codeagent-memory

السجل الرسمي أدوات المطورين

Local code graph and solution memory for coding agents via CLI and MCP.

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

OCI package ghcr.io/hanochzhu/codeagent-memory:0.1.5
Claude Code
claude mcp add codeagent-memory -- docker run -i --rm ghcr.io/hanochzhu/codeagent-memory:0.1.5
إعداد JSON (Claude Desktop وCursor وVS Code)
{
    "mcpServers": {
        "codeagent-memory": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/hanochzhu/codeagent-memory:0.1.5"
            ]
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. cam
  2. Contents
  3. Why cam?
  4. Get Started
  5. Key Features
  6. How It Works
  7. Agent Workflow
  8. CLI Reference
  9. Memory Rules
  10. Configuration
  11. Benchmarks
  12. Supported Agents
  13. Supported Languages
  14. Supported Platforms
  15. License

cam

English · 中文 · 日本語 · 한국어 · العربية · 🌐 Website

A local multi-turn conversational memory system purpose-built for coding agents

Code graph + memory · surgical reads · 100% local · MCP + CLI

Kernel written in Rust

Contents

Guides: Interactive Showcase (Website) · Main Agent vs Subagent · MCP Configs by IDE · 中文说明


Why cam?

When an AI coding agent explores a repository, it usually rediscovers structure the slow way — running grep, glob, and full-file Read one file at a time — and forgets everything in the next session.

cam gives the agent two local retrieval planes in a single binary:

PlaneWhat it storesHow the agent uses it
Code GraphTree-sitter symbols (functions, types, methods) as a virtual filesystem + 1-hop callers/calleesls, find, read src/file.rs/symbol, `ref symbol --dir in\out` — surgical symbol reads instead of whole-file dumps
Memory TreeProject facts, architecture decisions, debugging write-ups, and user habitsrecall (Vector + BM25 fused with RRF) and add (with branching --parent and revision --supersedes)

One binary, two interfaces: The main agent calls cam over MCP (cam mcp); subagents (which rarely inherit MCP tools) call the exact same CLI (cam --json …). Both share .cam/cam.db on disk, 100% local, zero API cost.


Get Started

Paste this prompt directly into your coding agent (Cursor, Claude Code, Codex, Windsurf, GitHub Copilot, Cline, etc.) and let it install, index, and wire cam for you:

Install cam from https://github.com/HanochZhu/codeagent_memory: require a working Rust toolchain (rustup), run `cargo install --git https://github.com/HanochZhu/codeagent_memory --locked`, ensure ~/.cargo/bin (or %USERPROFILE%\.cargo\bin on Windows) is on PATH, then verify with `cam --help`. In this repo run `cam index`. For the main agent, register MCP stdio: command `cam`, args `["mcp"]` (Cursor: .cursor/mcp.json; Claude Code: .mcp.json). Subagents call `cam --json` in the shell. Do not add extra docs.

How each IDE / agent handles this prompt

EnvironmentWhat to do
Cursor / Windsurf / Claude Code / CodexPaste into Agent / Chat; the agent runs the terminal install, builds .cam/cam.db, and writes the MCP config
VS Code (Copilot / Continue / Cline)Paste into Agent / Chat mode with terminal access enabled
JetBrains (IntelliJ / RustRover / GoLand)Paste into AI Assistant, or run cargo install in the built-in terminal

Note: cargo install places cam in ~/.cargo/bin (Windows: %USERPROFILE%\.cargo\bin). Restart your terminal or IDE if cam is not immediately found on PATH.


Option 2: Manual Setup
1. Install the CLI

Requires a Rust toolchain:

cargo install --git https://github.com/HanochZhu/codeagent_memory --locked
cam --help

Alternative: Build from local clone or run via Docker

From a local clone:

git clone https://github.com/HanochZhu/codeagent_memory.git
cd codeagent_memory
cargo install --path . --locked

Docker (no Rust toolchain required):

docker pull ghcr.io/hanochzhu/codeagent-memory:0.1.5
docker run -i --rm -v "$PWD:/work" -w /work ghcr.io/hanochzhu/codeagent-memory:0.1.5

Or build locally: docker build -t cam https://github.com/HanochZhu/codeagent_memory.git

2. Index & query your project
cd your-project
cam index                                              # parse repo into .cam/cam.db

# Query the code graph
cam ls src/                                            # list files or symbols in a file
cam read src/main.rs/main                              # read a single symbol body
cam ref main --dir in                                  # 1-hop callers (in) or callees (out)

# Query & write to the memory tree
cam recall "how does hybrid recall fuse BM25 and vectors"
cam add --summary "..." < notes.md

cam auto-initializes .cam/ on first use. Run cam watch in the background if you want live incremental graph updates as files change.

3. Connect MCP for the main agent

Add cam mcp to your host's MCP configuration (e.g. .cursor/mcp.json or .mcp.json):

{
  "mcpServers": {
    "cam": {
      "command": "cam",
      "args": ["mcp"]
    }
  }
}

See docs/mcp.md for host-specific config paths and docs/agents.md for main-agent / subagent prompt rules.

The first recall or add downloads the default embedding model (potion-multilingual-128M to ~/.cam/models/) and falls back to a lexical hash embedder if offline.


Key Features

FeatureDetails
SQLite Code GraphTree-sitter parses functions, types, and call edges into .cam/cam.db for instant symbol-level navigation
Virtual Pathssrc/main.rs addresses a file outline; src/main.rs/main addresses the symbol body directly
Live Incremental Synccam sync hashes file contents; cam watch keeps the graph updated on save
Hybrid Recall (RRF)Combines local dense embeddings (model2vec) + identifier-aware BM25 via Reciprocal Rank Fusion ($k=60$)
Revision Chains & Tree--parent builds branching topic hierarchies; --supersedes links linear revisions and folds older entries automatically
Ebbinghaus RetentionRetention $R = e^{-t / S}$ gently weights ranking ($\le 10\%$) and flags stale / needs_update memories without deleting history
Dual Interface (MCP + CLI)Main agent uses cam_* MCP tools; subagents run cam --json … in the shell
100% Local & PrivateZero external API keys; runs entirely on local SQLite and on-disk embeddings
9 LanguagesRust, Python, TypeScript, JavaScript, Go, Java, C, C++, C#

How It Works

  1. Extract — tree-sitter walks the workspace and stores symbol definitions and call edges in .cam/cam.db.
  2. Surgical Read — Agents navigate via virtual paths (ls → find → read → ref). Reading a file returns its symbol outline; reading file/symbol returns only that symbol's source slice.
  3. Hybrid Recall — recall takes an English query, embeds it locally, runs identifier-aware BM25 (splitting snake_case, kebab-case, camelCase + English stemming), prunes low-confidence tails, and fuses both lists with RRF ($k=60$) scaled by $0.9 + 0.1 \times R$. Superseded revisions are automatically expanded to their newest replacement.
  4. Write-Back — When an agent solves a non-trivial task, it extracts atomic facts so each add stores only one fact (English summary; body supports non-Latin characters). Related facts are connected via --link / links into a knowledge graph (inspected via mem show; recall does not traverse graph links yet). --parent attaches a memory to a structural topic; --supersedes replaces an outdated memory while preserving lineage.

Architecture deep dive (Chinese): DESIGN.md.


Agent Workflow

Every coding task follows the same four-step loop:

  1. Recall first — Query cam_recall / cam recall in English before grepping. Reuse a hit if it is latest and not needs_update.
  2. Ensure indexed — If graph tools return not_indexed, run cam_index / cam index once for the project.
  3. Walk the graph — On a memory miss, locate symbols with find or ls, read symbol bodies with read <file>/<symbol>, and trace callers/callees with ref <symbol> --dir in|out.
  4. Write back — Persist newly discovered architecture facts or fixes with cam_add / cam add as atomic facts (one fact per memory, English summary; body supports non-Latin characters), linking related facts with links / --link.
RoleInterfaceTypical Usage
Main Agent (Chat / IDE session)MCP (cam mcp)Calls cam_recall, cam_find, cam_ls, cam_read, cam_ref, cam_add, cam_mem_tree, cam_mem_show directly
Subagent (Task / explore / CLI)CLI (cam --json)Runs cam --json --project <dir> <cmd> in the shell (subagents rarely inherit MCP tools)

Full agent rules & copy-paste system prompts: docs/agents.md.


CLI Reference

Code Graph Commands
CommandDescription
cam indexParse the project with tree-sitter into .cam/cam.db (creates .cam/ if needed)
cam syncIncrementally update the graph for modified files using content hashes
cam watch [--debounce-ms N]Watch source files and auto-sync (--json streams one JSON report per sync)
cam ls [virt_path]List directories, files, or symbols inside a file
cam read <virt_path> [--full]Read a file's symbol outline, a specific symbol body (path/symbol), or the --full file
cam find <query> [--kind K] [--file S] [--scope D] [--limit N]Case-insensitive substring search over symbol names (exact matches first, then prefixes)
`cam ref <symbol> --dir in\out [--file S] [--kind K] [--scope D]`1-hop callers (in / --callers) or callees (out / --callees). Returns ranked candidates on ambiguous names
Memory Commands
CommandDescription
cam recall "<query>" [--limit N] [--no-expand] [--include-superseded] [--snippets]Hybrid RRF recall (English query). --no-expand skips newest-revision expansion; --include-superseded keeps old revisions; --snippets clips long bodies below rank 1
`cam add --summary "..." [--parent ID] [--supersedes ID] [--link ID]... [--body TEXT \--file PATH]`Store one atomic fact as a memory (English summary required; body supports non-Latin characters; via --body, --file, or stdin). --link connects related facts in the knowledge graph; --parent for topic hierarchy; --supersedes to replace an older memory
cam mem treeRender the memory hierarchy and revision chains
cam mem show <id>Inspect a single memory entry in full
Server & Configuration Commands
CommandDescription
cam mcpStart the stdio MCP server for the main agent (see docs/mcp.md)
cam statusShow resolved project root, database path, node/edge/memory counts, and active config
cam config getPrint current ~/.cam/config.toml settings
cam config set stale_days <N>Set age threshold (in days) for marking memories stale
cam config set embedding_model <model>Set Hugging Face model2vec repo, local model directory, hash, or default

Global flags & conventions:

  • --project <dir> (or CAM_PROJECT env var) overrides automatic upward .cam / .git root detection.
  • --json emits compact JSON (--pretty for indented JSON). Errors on --json print {"error":{"code":…,"message":…}} to stdout and exit non-zero.
  • Ambiguous symbols: When read or ref matches multiple definitions, cam returns status: "ambiguous" with candidate node IDs (e.g. src/main.rs:function:main:12) that can be passed directly back to read or ref.
  • Ignore rules & multi-repo directories: Honors .gitignore and .camignore at any depth. Skips git submodules and linked worktrees; indexes nested standalone clones as kind: "project" (passable to --scope).

Memory Rules

  • Atomic facts & knowledge graph links: Store only one atomic fact per memory to avoid packing excessive information into a single entry. When multiple facts are related, link them with --link / links to form a knowledge graph (graph recall is not enabled yet).
  • English queries and summaries: Recall queries and memory summaries must be written in English. Memory bodies support non-Latin characters.
  • Retention & reinforcement: Ebbinghaus retention $R = e^{-t / S}$ adjusts recall score via $\text{relevance} \times (0.9 + 0.1 \times R)$. Entries with $R < 0.3$ are marked needs_update; entries older than stale_days (default 30) are marked stale. Every valid recall hit (needs_update = false) refreshes last-accessed time and multiplies stability $S$ by 1.7.
  • Non-destructive lineage: Memories are never deleted. --parent forms branching trees; --supersedes forms linear revision chains where only the tail is marked latest and older revisions are folded out of default recall results.

Configuration

Global settings live in ~/.cam/config.toml:

stale_days = 30
# embedding_model = "minishlab/potion-multilingual-128M" # default (cached under ~/.cam/models/)
# embedding_model = "minishlab/potion-base-8M"           # lighter Hugging Face model2vec repo
# embedding_model = "/path/to/local/model2vec"           # dir with tokenizer.json, config.json, model.safetensors
# embedding_model = "hash"                               # zero-download lexical hash embedder

Use CAM_EMBED_MODEL to override the model for a single process, or cam config set embedding_model default to reset. When the embedding model changes, the next recall automatically re-embeds existing memories before scoring.


Benchmarks

cam evaluates its code graph and memory planes separately against the closest open-source systems on identical corpora:

PlaneBaseline / AnalogueBenchmark CorpusHeadline Takeaway
Memoryagentmemory hybrid + tokenized grepcoding-agent-life-v11.000 R@5 / 0.240 P@5 (matches hybrid ceiling, 1.000 newest R@5 on revision chains)
Long-term MemoryBM25 / dense retrieversLongMemEval-S0.909 R@5 / 0.980 Hit@5 / 0.840 MRR with potion-multilingual-128M
Code Graphcodegraph v0.9.6LongMemCode (clap)0.769 vs 0.768 on supported 1-hop tasks, P95 ≈ 5.2 ms, $0
Workflow RetrievalLexical / BM25 file retrievalAgent Retrieval Bench V2 edit2ripple0.297 MRR (best first-hit rank, P95 7.3 ms)
Multi-turn TokensFull context dumpDeepSeek multi-turn57% fewer tokens on memory track, 98% fewer tokens on code track

General chat memory frameworks (Mem0, Zep, Letta) target conversational logs rather than these coding-agent corpora and are omitted from the tables below.

System Comparison
camagentmemorycodegraph
What it storesCode graph + memory treeSession / chat memoriesCode graph
Query primitivesrecall / ls / find / read / refsmart-search / rememberexplore / callers / callees
InterfaceMCP + CLIMCP + REST + hooksMCP + CLI
Ranking / FusionVector + BM25 + RRF + retentionBM25 + embed + rerankFTS5 + graph walk
Cost100% local ($0)Local serverLocal
1. Memory — coding-agent-life-v1

15 sessions, 15 queries, $k=5$ (same scoring as agentmemory score.ts; P@5 ceiling is 0.240).

SystemHit RateR@5P@5Source
grep (tokenized substring)15 / 150.9670.227this repo, 2026-09-23
cam min-max sum (legacy)15 / 150.9330.213historical, hash embed
cam RRF15 / 151.0000.240this repo, hash embed
agentmemory hybrid15 / 151.0000.240published v0.9.26

Revision chains (--lineage): Re-ingesting every turn as a --supersedes revision tests whether top-$k$ returns the newest node of each gold chain (newest R@k) and whether any superseded node falsely claims latest (stale latest).

kR@kP@knewest R@kstale latest
51.0000.2401.0000
101.0000.1201.0000
2. Long-Term Memory — LongMemEval-S

100 non-abstention questions sampled with seed 42 from cleaned LongMemEval-S. Retrieval fuses embeddings + BM25 with RRF at $k=10$ without an LLM reader.

EmbedderR@1R@5R@10Hit@1Hit@5Hit@10MRRRetrieval P50 / P95
hash (offline test)0.3820.8030.9220.5800.9100.9700.71824.1 / 35.5 ms
potion-multilingual-128M0.4740.9090.9520.7400.9800.9900.8401.12 / 1.34 s
3. Workflow Retrieval — Agent Retrieval Bench V2 (edit2ripple)

58 anchored-change queries across 44 frozen repository snapshots (no LLM; BCY = Budgeted Context Yield under the canonical 8K-token file-packing protocol).

SystemRecall@5Recall@10Recall@20MRRBCY@8k
cam graph0.3000.3350.3780.2970.300
Lexical0.4120.5360.5880.2430.447
BM250.2070.2870.4990.1540.243

cam graph achieves the highest first-hit rank (MRR 0.297, query P95 7.3 ms), while lexical search provides broader multi-file coverage — motivating graph + lexical rank fusion.

4. Code Graph — LongMemCode (clap)

clap v4.6.1, 536 scenarios against SCIP gold (no LLM, P95 ≈ 5.2 ms, $/1k = 0).

Slicencamcodegraph 0.9.6
Supported (1-hop)4780.7690.768
lookup / file_symbols293 / 550.808 / 0.9150.808 / 0.915
callers / callees67 / 180.397 / 0.8110.355 / 0.867
implementors400.1190.094
Raw / Weighted (all 536)5360.709 / 0.7040.704 / 0.700

5. Multi-Turn Token Savings — DeepSeek

Full context dump vs. per-turn cam retrieval (deepseek-flash, hash embedder, 2026-10-13):

TracknFull Acc.cam Acc.Full Tokenscam TokensToken Saving
Memory (coding-agent-life)151.000.8722,7969,90457% (1,471 → 616 / turn)
Code (this repo indexed)60.830.33379,0666,34298% (63,076 → 1,000 / turn)

Reproduce all benchmarks

Dataset paths are configured in eval/datasets.toml (coding-agent-life-v1 defaults to ../agentmemory or CAM_EVAL_CODING_LIFE).

python3 eval/coding_life/run.py --adapter grep
python3 eval/coding_life/run.py                                             # potion; errors if the model fails
python3 eval/coding_life/run.py --hash-embed                                # hash embedder
python3 eval/longmemeval/run.py --sample 100 --seed 42 --workers 8          # potion
python3 eval/longmemeval/run.py --sample 100 --seed 42 --workers 8 --hash-embed
python3 eval/locomo/run.py --workers 4                                      # potion, evidence recall

git clone --depth 1 https://github.com/eyuansu62/agent-retrieval-bench \
  eval/agent_retrieval/vendor/agent-retrieval-bench
python3 -m pip install -e eval/agent_retrieval/vendor/agent-retrieval-bench
arb download-benchmark --version v2_edit2ripple --local-dir eval/agent_retrieval/data --force
python3 eval/agent_retrieval/run.py --workers 8

python3 eval/llm_multiturn/run.py --track both   # potion; requires DEEPSEEK_API_KEY
python3 eval/longmemcode/run.py --corpus clap
python3 eval/charts/generate.py

Supported Agents

Register cam mcp (stdio) for the main agent; subagents use the cam --json CLI directly with zero extra setup.

HostMCP ConfigurationSubagent / Notes
Cursor.cursor/mcp.json, ~/.cursor/mcp.json, or .cursor-plugin/plugin.jsonTask / explore subagents use CLI
Claude Code.mcp.json, ~/.claude.json, or claude mcp add cam -- cam mcpLimited-tool subagents use CLI
Codex~/.codex/config.toml → [mcp_servers.cam]codex exec uses CLI
Windsurf~/.codeium/windsurf/mcp_config.jsonCascade uses MCP
GitHub Copilot.vscode/mcp.json or ~/.copilot/mcp-config.jsonChat uses MCP; CLI scripts use CLI
Continue / Cline~/.continue/config.yaml / ~/.cline/mcp.json
JetBrainsAI Assistant → MCP (cam / mcp)Use absolute path to cam if IDE PATH is empty
Gemini CLI / Antigravity / OpenCode / Zed / DroidSee docs/mcp.md

Copy-paste configs: docs/mcp.md · System prompts: docs/agents.md.


Supported Languages

LanguageExtensionsIndexed Nodes & Edges
Rust.rsfunctions, structs, enums, traits, calls
Python.pyfunctions, classes, calls
TypeScript.ts, .tsxfunctions, methods, classes, calls
JavaScript.js, .jsxfunctions, methods, classes, calls
Go.gofunctions, methods, structs, calls
Java.javafunctions, methods, classes, interfaces, calls
C.cfunctions, structs, calls
C++.cc, .cpp, .cxx, .h, .hppfunctions, methods, classes, structs, calls
C#.csfunctions, methods, classes, interfaces, calls

Supported Platforms

cam compiles natively on macOS, Linux, and Windows via cargo install --git https://github.com/HanochZhu/codeagent_memory --locked, or runs anywhere via Docker (ghcr.io/hanochzhu/codeagent-memory:0.1.5). See Get Started.


License

MIT


Made for AI coding agents — Claude Code, Cursor, Codex, Windsurf, Copilot, and JetBrains

Report Bug · Request Feature

الأسئلة الشائعة

ما هو codeagent-memory؟

Local code graph and solution memory for coding agents via CLI and MCP.

كيف أثبّت codeagent-memory؟

يعمل على جهازك. في Claude Code: claude mcp add codeagent-memory -- docker run -i --rm ghcr.io/hanochzhu/codeagent-memory:0.1.5. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج codeagent-memory إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل codeagent-memory مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون codeagent-memory؟

ينشره HanochZhu. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.