frigg-first-code-search

Frigg First Code Search

Frigg is the default for code discovery, file listing, navigation, exact code search, and bounded source reads.

Before using shell rg, grep, find, fd, cat, or sed for code exploration, use the matching Frigg MCP tool in attached or attachable code repositories.

Shell tools are fallback only for git state and diffs, non-code files, build/test output, generated or unindexed files, explicit live-disk verification, or when Frigg is unavailable.

Do not run parallel shell grep in the same turn as Frigg search on indexed source.

Follow the evidence, not just the shell replacement: use search_symbol for a known identifier and search_batch for independent hypotheses when callable. After selecting a hit, copy its target_ref into navigation when relationships matter, then use read_match for source proof. A known path still warrants direct read_file; do not add navigation merely to use more tools.

Harness boundary (Frigg is an evidence layer, not an agent OS):

• Host tool order, Grep-first defaults, and intermittent MCP registration/inheritance flukes are outside Frigg product code (FUT-003 harness boundary — not a Frigg CI gate or ranking bug).
• When the bridge is down or tools are unregistered, that is harness reliability, not ranking quality.
• Soft PreToolUse / adopt hooks are opt-in (not guaranteed Frigg-first). Soft only: Claude hook injects next-step context (search_text / search_batch / …) and never hard-denies Grep/shell (permissionDecision is not product).
• Hard block of Grep/rg on indexed roots is a host experiment, not Frigg core — do not invent FRIGG_HOOK_STRICT or product tool-order hacks.
• Do not invent product hacks (fake Grep, hide host tools, force MCP tool order, or a “subagent bridge health” Frigg tool — Frigg cannot see the host registry when it is not registered).
• Route indexed source through Frigg when the live tool list exposes Frigg tools; progressive disclosure on this top screen is intentional (30-second rule).

Probe-on-spawn (Task / subagent / new session):

1. Before claiming Frigg-first, verify Frigg is on the *live* host tool surface for THIS spawn:
   live tools/list (or a successful Frigg CallMcpTool). Do NOT trust on-disk mcps/…/tools
   descriptors or a parent session's tool list as proof this spawn has Frigg.
2. If Frigg is absent from live tools/list for this spawn (empty Frigg server, or
   Tool not found when calling a known Frigg tool like search_text while the parent still has Frigg):
   - Shell/Grep/Read fallback is correct for this spawn
   - Note the gap once (harness MCP inheritance / registration) — do NOT file as Frigg search/ranking failure
   - Do NOT invent workspace_reindex / bridge_health / fake tools to "fix" registration
   - (Invented names / extended-only tools missing while other Frigg tools work → surface honesty,
     not inheritance — see tool-surface rules)
3. If the initial Frigg workspace is the wrong repository, attach the task repository with
   workspace(path=...) before falling back to local tools.
4. Parent session success does NOT imply child Task success — re-probe every delegation.
5. Prefer loopback HTTP + frigg serve when multiple clients/subagents should share one Frigg
   *after* each spawn actually has Frigg registered; HTTP shares state when registration works —
   it does not create child registration by itself.

Partial surface (some Frigg tools work, recommended ones are missing):

• Compare the host-callable tools, the installed skill's mcp.json includeTools (or inline mcpServers), and workspace.runtime.tools_exposed / live tools/list when available. A stale skill filter can hide symbol, batch, and navigation tools even when the server supports them.
• Report the reduced surface once. Do not call host-unavailable tools just because the skill or server lists them. Use parallel scoped searches when batch is unavailable; use bounded exact identifier/import/call-site searches when navigation is unavailable, then read the witnesses.
• See runtime recovery before refreshing an install. Preserve its endpoint/credentials; an expired HTTP session is not evidence of a smaller server tool surface.