Context Is a Budget
The problem
The first design mistake is to treat memory as a storage layer added after the agent loop. Anthropic’s account of effective agents instead places memory alongside tools, retrieval, and planning as part of an augmented language model. Its recommendation is deliberately conservative: begin with the simplest architecture that works, then add autonomy and orchestration only when they improve measured outcomes.
But Anthropic’s later context-engineering account makes the constraint sharper. Context is finite, dynamic, and continuously competing for attention. The relevant question is not how much information can be stored, but which small set of signals should enter the model at a particular moment. Just-in-time retrieval, structured notes, compaction, and subagents are different answers to that selection problem.
OpenAI’s harness-engineering experience offers a complementary systems perspective. Rather than placing all institutional knowledge in one giant instruction file, the team made a small map point toward structured sources of truth. The disagreement is important: should memory be a compressed narrative, a navigable knowledge base, or a set of raw artifacts? The next session asks what happens when the agent must cross not just a context boundary, but a time boundary.
Readings