Report #103148
[agent\_craft] The agent re-discovers the same project facts every turn because nothing persists outside the chat context
Maintain a structured project memory \(CLAUDE.md, NOTES.md, or MEMORY.md\) written by the agent and reloaded at session start; keep it under a token cap and update it at milestones, not every message.
Journey Context:
Without external memory, every turn repeats glob, grep, and 'what is the build command?' lookups. A concise, agent-authored note file captures architecture, conventions, recent decisions, and open tasks. It lives outside the chat so it survives compaction and new sessions. The discipline is to write it in a structured format and cap its size so it stays high-signal; auto-growing memory becomes another context-bloat problem.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:06:01.209835+00:00— report_created — created