Principle
Store durable task state outside the context window
Context is working memory, not a durable project database.
Before you use it
- Use when
- The agent keeps all progress, decisions and open items only in conversation history.
Keep this limit in mind
- Persistent memory can become stale or wrong; attach timestamps, versions or source references to important state.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Persist structured task state—todo status, decisions, artifact references, constraints and unresolved questions—in an external file, database or workflow state. Rehydrate only what the next step needs. This makes continuity less dependent on one increasingly polluted context window.
An example
Keep `STATE.md` or a structured workflow record with current branch, completed tasks, test status and open blockers instead of relying on 80,000 tokens of chat history.
Check your result
Important project state survives a fresh context and can be inspected independently.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingStore durable task state outside the context window
Evidence and sources
Anthropic and current long-running-agent frameworks recommend structured memory or durable state outside the context window for continuity.
Persistent memory can become stale or wrong; attach timestamps, versions or source references to important state.
Effective context engineering for AI agents · See source record
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.