FastContext × Claude Code — interleaved outer/inner transcript on the git codebase (local 4B-RL explorer via Ollama, hard functional queries) FastContext, a local 4B-RL explorer running via Ollama, was tested as an MCP tool for Claude Code on four hard git queries against the git codebase. The tool returned thin or drifting results on a recursive merge query, requiring four calls and 154 seconds, while a single call sufficed for an interactive-rebase query in 44 seconds. The developer noted that Claude Code had to split queries or re-query when FastContext returned empty results. Each of the 4 hard git queries run through Claude Code , which was allowed only the mcp fastcontext explore tool built-in search denied; grove removed from the test bench . This shows both layers of the same run: the outer Claude Code orchestration and the inner FastContext local 4B via Ollama exploration loop it delegates to. |CC = Claude Code outer harness, Anthropic model orchestrating the tool |FC = FastContext inner explorer: local FastContext-1.0-4B-RL Q4, Ollama - explore ... Claude Code calls the MCP tool |FC Turn n: LLM .. one turn of the inner explorer loop LLM latency + tokens |FC - Grep/Read a read-only tool call inside the explorer its own latency <- tool result what the explorer returned to Claude Code All timings are measured wall-clock; inner turns come from the MCP server's per-call timing sidecars, outer flow from Claude Code's stream-json. | Query | FC calls | End-to-end | Outcome | |---|---|---|---| Q1 recursive/ort merge + rename detection | 4 | 154s | FC returned thin/under-cited results across 4 calls drifted to unrelated files ; Claude relayed them with a caveat that they looked unreliable | Q2 interactive-rebase sequencer | 1 | 44s | Single FC call found ; Claude relayed citations sequencer.c / sequencer.h | Q3 index read/write + cache-tree | 3 | 75s | First combined FC call empty → Claude split into 2 focused queries → got citations | Q4 packfile delta create/apply | 2 | 128s | First FC call empty → Claude re-queried → second call hit the delta machinery | User → Claude Code: Use the fastcontext explore tool to find where the recursive/ort three-way merge is implemented and where rename detection during a merge is handled. Report the file:line citations it returns. Ground truth: merge-ort.c; diffcore-rename.c End-to-end wall clock: 154s · FastContext calls Claude made: 4 php |CC ToolSearch - load mcp fastcontext explore schema deferred tool |CC <- tool result: empty |CC - explore query='where is the recursive/ort three-way merge implemented and where is rename detection during a merge handled' |FC Turn 1: LLM 5311ms p=6039 c=102 |FC - Grep pattern=merge-ort|recursive merge|three way merge path=/git mode=files with matches 8ms ok |FC obs: git/apply.c / git/merge-ort.c / git/merge-ort-wrappers.c / src/g ... |FC - Grep pattern=rename|renamed|detect. rename|rename. detect path=/git mode=files with matches 9ms ok |FC obs: git/diffcore.h / git/setup.c / git/transport-helper.c / git/ ... |FC Turn 2: LLM 1467ms p=7378 c=47 |FC - Read /git/merge-ort.c 1ms ok |FC obs: git/merge-ort.c:1-2000 / 1|/ / 2| "Ostensibly Recursive's Twin" merge strategy, or "ort" for short. ... |FC - Read /git/diffcore-rename.c 1ms ok |FC obs: git/diffcore-rename.c:1-1724 / 1|/ / 2| / 3| Copyright C 2005 Junio C Hamano / 4| / / 5| / 6| ... |FC Turn 3: LLM 43752ms p=27631 c=878 - emits