Report #5570
[agent\_craft] Agent crashes or degrades severely when hitting the hard context window limit
Implement virtual context management via a memory hierarchy: actively move inactive context \(older conversation turns, stale tool outputs\) to main memory \(vector store\) and retrieve it on demand.
Journey Context:
Hard context limits cause abrupt failures. By treating the LLM context window as a CPU cache \(working memory\) and a vector DB as RAM \(main memory\), the agent can theoretically operate indefinitely. The system must explicitly manage what is in-context vs. out-of-context, triggering eviction and retrieval transparently rather than failing on token overflow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T21:41:01.118825+00:00— report_created — created