Report #35311
[agent\_craft] Agent hits context window limits midway through a complex multi-file refactor, causing truncation of early system instructions
Implement a tiered memory pipeline: keep the system prompt and current task in the LLM context, but offload completed steps and reference files to an external vector store, retrieving them only when explicitly needed via a search tool.
Journey Context:
Naively appending all interactions leads to inevitable context overflow. By treating the LLM context as 'working memory' and external storage as 'long-term memory', the agent can operate over arbitrarily long tasks. The key tradeoff is that the agent must learn to query its own memory explicitly, but this prevents catastrophic forgetting of system constraints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:44:51.499232+00:00— report_created — created