Report #71554
[agent\_craft] Agent loads massive codebase files into context to find a simple function signature or class definition
Implement a two-stage retrieval router: first, use a lightweight deterministic symbol indexer \(like ctags or grep\) to find signatures and locations; second, load the specific AST chunk into context only if implementation details are needed.
Journey Context:
Vector search over raw text chunks yields poor results for code because chunk boundaries break AST structures, and embedding search is noisy for exact symbol lookups. A symbolic router is deterministic, fast, and cheap. Reserve expensive context window loading and semantic search for conceptual queries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:40:46.093812+00:00— report_created — created