Product boundary
Frigg’s category is local code context for coding agents. It gives agents repository-aware search, navigation, and bounded reads through MCP so their claims can be checked against local source.
What Frigg owns
Section titled “What Frigg owns”Frigg owns the local evidence layer:
- repository-aware file listing and exact text search
- ranked discovery, known-symbol lookup, and multi-probe search
- bounded source reads, citations, outlines, and structural queries
- read-only definitions, references, implementations, and call navigation
- target-first impact analysis with explicit trust and completeness
- runtime status for adopted repositories
- optional semantic recall, SCIP ingestion, and watch refreshes
What Frigg does not own
Section titled “What Frigg does not own”Frigg is not an AI pair programmer, IDE replacement, hosted code-intelligence platform, Copilot alternative, generic semantic-search product, framework runtime, or agent operating system.
It also does not control a host’s tool ordering, authorization, MCP registration, or subagent inheritance. If a child session lacks Frigg while its parent has it, repair the host integration or use that child’s allowed fallback; it is not evidence of a search-ranking failure.
Safety and side effects
Section titled “Safety and side effects”Normal indexing reads source inside configured workspace roots and writes only Frigg-owned state such as .frigg/storage.sqlite3. It does not edit project source files.
Some optional or explicit operations have wider effects:
frigg adoptwrites managed instructions, MCP configuration, optional hooks, and optional copied skills in the project or host skill locations.- Semantic providers can send source-derived embedding inputs to the configured OpenAI, Google, or OpenAI-compatible service. The local provider stays local.
- Precise generators can execute repository-local or PATH tools and write
.frigg/scip/artifacts. - The CLI owns explicit maintenance such as
frigg initandfrigg index. The public MCP product surface has no reindex or source-write tool.
Why the boundary matters
Section titled “Why the boundary matters”The customer value is not a particular implementation detail. Frigg helps agents find the right files, narrow source windows, follow identities, and leave a traceable path to evidence. Hosts and agents still decide what to change and whether the evidence supports a conclusion.
Related
Section titled “Related”Source Anchors
Section titled “Source Anchors”../frigg/README.md../frigg/crates/cli/src/mcp/types.rs../frigg/crates/cli/src/mcp/guidance.rs../frigg/crates/cli/src/workspace_ignores.rs../frigg/skills/frigg-first-code-search/SKILL.md