Report #102117
[agent\_craft] Answering implementation questions from parametric memory instead of current code
Run grep, glob, and read on the codebase before proposing any code change; ground every claim in a fresh observation.
Journey Context:
LLMs have strong memory of common frameworks, but real codebases have local conventions, custom wrappers, renamed functions, and recent refactors. Answering from training memory produces imports that do not exist and APIs that have changed. The ReAct pattern demonstrates that interleaving reasoning with actions—search, read, compute—outperforms pure reasoning. The cost of a few tool calls is tiny compared to the cost of a wrong edit. A common anti-pattern is asking the user 'what does this function do?' when the codebase contains the answer; the agent should retrieve it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T04:59:59.318369+00:00— report_created — created