Report #100246
[architecture] I treated the context window as the agent's memory and now long tasks degrade or crash.
Externalize durable memory from the start. Give the agent explicit read/write memory tools and keep only the working set in the prompt, just as you would use RAM as a cache and disk as storage.
Journey Context:
Anthropic's 'augmented LLM' pattern treats retrieval, tools, and memory as first-class augmentations, not afterthoughts. Teams that stuff everything into the prompt hit context rot, high latency, and lost state. The alternative—growing context windows—is expensive and still finite. Memory-first design means the agent decides what to retain via tools, not the developer hoping the prompt is big enough.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-01T04:54:10.236274+00:00— report_created — created