search_contextLABSCO SUMMARY
A compact tool surface, and it tells you when its answer is stale.
The interesting design choice is honesty about freshness: every read carries the indexed commit and a dirty-file count, and points at refresh_context when the index has drifted. In Claude Code the hooks push context into each prompt automatically, so the tools are there for the gaps rather than the main path.
What it is
A local-first context and memory layer for coding agents. It indexes your repository with tree-sitter into SQLite and a local vector store, records call and import edges, and assembles a token-budgeted bundle of the code that answers a given question.
What you get
- search_context — assembled, token-budgeted context for a multi-file question, with compressed evidence you can expand later
- search_code — ranked raw hits, or action=read_chunk to pull one indexed chunk back at full source
- explain_flow — one tool covering call flow, callers, callees, a bidirectional stack tree, imports for a file, symbol lookup, and seed resolution
- memory — recall, explain, list, store and forget project memories; it keeps working even when no code is indexed
- refresh_context — the single reindex verb, for the whole project or named paths
- get_stats — index freshness, indexed commit versus HEAD, latency percentiles, and storage footprint
- Every read attaches a staleness object, so the agent can tell when the index is behind the working tree
Requirements
Node.js 22 or newer. On Windows the generated hooks call curl and cat, so Git Bash or WSL must be on PATH. No cloud account or API key for the default local provider — embeddings run locally; ollama and openai are opt-in alternatives. Install globally from npm as @proofofwork-agency/reporecall, then run init and index in the project root.
Setup effort
One command — npm install -g @proofofwork-agency/reporecall
USE CASES
Answering "how does this work?" on an unfamiliar repo
Ask in plain language and get the files and symbols that actually matter, packed under a token budget.
Tracing what a change will break
Find who calls a function, walk the call tree in both directions, and read the imports of the file you are about to edit.
Pulling one exact piece of source back
Expand a compressed piece of evidence into full source by chunk id, or by file path and line range.
Keeping a project rule from being relearned every session
Store the decision once, pinned, and recall it at the start of the next session.
Checking the index before trusting an answer
Read the indexed commit and chunk counts, and reindex the paths you just changed.
6 tools
Listed in project docs. Your client may show a different list.
search_codeexplain_flowmemoryrefresh_contextget_statsBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
npm on PATH
INSTALLATION
Connect your client
Server setup
npm install -g @proofofwork-agency/reporecallMCP Clients
Any MCP client — installed CLI
{
"mcpServers": {
"reporecall": {
"command": "reporecall",
"args": [
"mcp",
"--project",
"${PROJECT_ROOT}"
]
}
}
}Values written as ${…} are filled in only by clients that expand variables.
Claude Code
In your project root, run reporecall init — it writes the Claude Code hook settings and .mcp.json for this project.
Run reporecall serve to index the code and keep the index fresh, or reporecall index for a one-off index.