FastContext-style explorer
The CLI supplies a Claude Code agent file namedfastcontext. It is inspired by FastContext research but does not implement the paper’s trained model or inherit the paper’s reported results.
Install for current project:
explore is a legacy alias for:
Permission boundary
The explorer agent has only Read, Glob, and Grep tools. It cannot edit files or run commands. Its contract returns one verified citation per line:no relevant locations found instead of a guessed citation.
When to use explorer
Use it for cold-start localization, broad cross-file relationships, or search that would otherwise add many file reads to solver context. Skip it when the task already names an exact file or symbol, or earlier evidence provides a usable location. Isolation is mechanism, not outcome guarantee. Explorer call adds model usage. Compare total task usage and resolution quality before claiming net benefit.Cavecrew
cavecrew is a decision guide for three compact Claude Code subagents:
Builder refuses scopes of three or more files. Main agent should own larger refactors and cross-component decisions.
Model overrides
Set environment variables before launching Claude Code to override the default model for each subagent:
Overrides patch only the installed agent frontmatter model line; empty variables do nothing. A plugin update or reinstall can replace the patch. Use the same model name strings you would use in any Claude Code agent frontmatter (for example,
haiku, sonnet, opus).
Example chaining
Locate, fix, verify (most common):cavecrew-investigatorreturns site list (path:line, symbol, note)- Main thread picks one or two sites, hands paths to
cavecrew-builder cavecrew-revieweraudits the resulting diff
cavecrew-investigator calls in one message with different angles (definitions, callers, tests). Aggregate in main.
Optional delegate tool
The CLI can registercaveman-delegate MCP server when execute.delegate is enabled. It is opt-in because delegated work consumes separate permissions and model usage.
Evidence rules
- Count explorer and delegated calls in total usage.
- Do not infer complete-task savings from shorter returned prose.
- Validate citations before edits when line drift is possible.
- Keep failure and no-result cases in benchmark.
- Treat paper results as external research, not package performance.