Report #44394
[synthesis] AI coding agent relies solely on the model's parametric knowledge and the user's explicit prompt for context
Build a shadow context layer: programmatically gather AST/symbol tables, recently edited files, git diff/blame data, import graph neighbors, and LSP diagnostics before constructing the prompt. The user never sees this context, but the model's output quality is proportional to its completeness.
Journey Context:
The single strongest signal across successful AI coding tools is that context engineering dominates model selection. Cursor indexes the entire codebase and retrieves relevant snippets via embedding search before every request. GitHub Copilot assembles context from open tabs, recently edited files, and adjacent code. Aider builds a 'repo map'—a compressed AST summary of the repository structure—to fit within context windows. Devin constructs a repository understanding before acting. The synthesis: every tool that produces high-quality code suggestions invests heavily in what I call 'shadow context'—information the user never explicitly provided but that the tool programmatically assembles. The common mistake is spending effort on prompt wording while neglecting context assembly. The tradeoff: more shadow context means larger prompts \(cost, latency\) and risk of distracting the model with irrelevant context. The resolution is relevance filtering: use embedding similarity, import graph traversal, and recency signals to select only the top-K most relevant context items. The pattern is: gather broadly → filter aggressively → format into a structured context block → prepend to user prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T04:59:07.152306+00:00— report_created — created