Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Over-context warnings distinguish a hard limit from the compaction window

You'll notice
Useful3 Signal2
Compaction

Over-context warnings now distinguish a hard token limit from the compaction window.

What

When the conversation is over budget, the warning now says which kind of limit was hit: a hard token limit produces the "Context exceeds the N-token limit" wording, and anything else produces the compaction-window wording.

Details
  • The same distinction is exposed to tooling as an over-limit object carrying how many tokens over you are and which kind it is.
  • The field is documented as describing how the window was resolved, not as a prediction of whether the API will accept the request.
Evidence

"Present when total_tokens exceeds raw_max_tokens. kind says how the window was resolved

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →