Stop compaction drift

Repo memory without pushing code to a cloud vector database.

CodeFathom is a local-first semantic indexing service that gives your CLI code agents (Claude Code, Codex CLI) persistent codebase memory via MCP tools. Keep conversations focused on intent and decisions, not pasted files.

Local-first privacyMCP-nativeCode-aware retrieval

The problem

Compaction drift kills long sessions

CLI code agents have finite context windows. As you paste files and discuss architecture, the window fills. When compaction kicks in, your original intent, discovered constraints, and key decisions get summarized away. That's compaction drift.

1

Context window fills

You paste files, discuss architecture, explore options. The agent's context fills with raw code and conversation history.

2

Compaction kicks in

The agent auto-summarizes older context to stay under its limit. Details get compressed into high-level summaries.

3

Drift happens

Your original intent, discovered constraints, and key decisions get lost. The agent starts making suggestions that contradict earlier conclusions.

The solution

Local semantic index with MCP retrieval

CodeFathom builds a semantic index of your repo locally. When your agent needs code context, it retrieves minimal, relevant slices via MCP tools instead of you pasting entire files.

1

Index locally

CodeFathom vectorizes your codebase and builds a symbol graph. Everything stays on your machine.

2

Query via MCP

Your agent calls MCP tools to search semantically, find references, or get architecture summaries.

3

Stay focused

Conversations stay about intent and decisions. No more pasting files or losing context to compaction.

MCP tools

Agent-facing retrieval surface

CodeFathom exposes five MCP tools that your CLI agent can call to retrieve exactly what it needs from your codebase.

search_semantic

Semantic search

Find code by meaning, not just keywords. Ask for "authentication logic" and get relevant functions.

"Find where we validate JWT tokens"

search_exact

Exact search

Precise text and symbol search when you know exactly what you're looking for.

"Find all uses of UserService"

find_references

Find references

Trace all call sites and usages of a function, class, or variable across the codebase.

"Where is handlePayment called?"

get_related

Get related

Find code entities related to a given symbol via imports, calls, or type relationships.

"What depends on OrderModel?"

describe_arch

Describe architecture

Get a structured summary of a module, directory, or the entire codebase architecture.

"Summarize the src/services/ folder"

Why CodeFathom

vs. cloud vector databases

Cloud vector DBs like Zilliz, Weaviate, and Pinecone are built for app backends. CodeFathom is built for agent workflows.

Local-first privacy

CodeFathom

Your repo stays on your machine. Embeddings and indexes are local.

Cloud Vector DB

Code must be uploaded to cloud storage for indexing.

No pipeline overhead

CodeFathom

Point at your repo and index. No ingestion pipelines to configure.

Cloud Vector DB

Requires data pipelines, chunking strategies, and sync jobs.

Code-aware retrieval

CodeFathom

Understands symbols, references, AST. Not just text similarity.

Cloud Vector DB

Generic vector similarity without code structure understanding.

MCP-native interface

CodeFathom

Tools designed for agent calls. Your agent queries directly.

Cloud Vector DB

App database APIs require integration code.

Minutes to value

CodeFathom

Install, index, connect your agent. Under 5 minutes.

Cloud Vector DB

Account setup, API keys, schema design, deployment.

Lower TCO

CodeFathom

No cloud storage fees. Pay only for context bandwidth delivered.

Cloud Vector DB

Storage costs, compute costs, egress fees add up.

Built for

Engineers who think in long sessions

CodeFathom is built for developers whose work requires sustained context across hours, not minutes.

CLI agent power users

Developers who use Claude Code, Codex CLI, or similar tools for serious coding sessions.

"My agent forgets what we decided two hours ago."

Ideation-heavy engineers

Developers who use agents for architecture exploration, refactoring planning, and design discussions.

"By the time I'm ready to implement, the context is gone."

Security-conscious teams

Teams that can't or won't push proprietary code to third-party cloud services.

"We need code search but can't use cloud vector DBs."

How it works

From repo to retrieval in minutes

Four steps to give your agent persistent codebase memory.

1

Install CodeFathom

Download and run the local service. No cloud account required for indexing.

2

Index your repo

Point at your codebase. CodeFathom builds embeddings and a symbol graph locally.

3

Connect your agent

Add CodeFathom's MCP server to your agent's config. One line in your settings.

4

Query and build

Your agent now retrieves code context via MCP tools. Stay in flow without pasting files.

Ready to try

Keep the plan alive.

Start your 14-day trial. Full access to all MCP tools. No code leaves your machine during indexing.