Principle

Treat context as a budget, not a transcript

A bigger context window is not permission to turn the whole project into one prompt.

About 1 min read

Before you use it

Use when
  • A long AI task keeps accumulating chat history, tool output and reference material.

Keep this limit in mind

  • Do not optimize tokens by deleting safety constraints, unresolved assumptions or evidence the next decision actually requires.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Decide which information must be present now, which can be retrieved later and which should live only in durable project state. Keep the active context focused on current goals, constraints, recent decisions and the evidence needed for the next move. Store bulky logs, old tool output and reference material outside the working window with discoverable pointers.

An example

For a SAP incident, keep the current failure, tested hypotheses and next diagnostic step in context; leave old log dumps in files the agent can reopen.

Check your result

You can explain why every large context item is present now rather than merely available somewhere.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingTreat context as a budget, not a transcript

Evidence and sources
Supports

Anthropic recommends treating context as a finite resource and aiming for the smallest set of high-signal tokens that supports the desired behavior.

More context can still be necessary for some tasks; the goal is relevance, not arbitrary brevity.

Effective context engineering for AI agents · Finite context and anatomy of effective context

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details