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

Structured context_usage alongside the /context table

Use it now
Useful3 Signal3
SDK Notable not in their notes

The streaming schema carries an optional context_usage field so tools skip parsing the markdown table.

context_usage
What

The streaming message schema adds an optional context_usage field carrying a machine-readable twin of the /context breakdown, so tools consuming the stream no longer have to parse the markdown table.

Details
  • It sits at the wrapper level, as a sibling of message.content on the synthetic assistant message that delivers the table.
  • Deliberately not replayed back to the model.
  • The markdown table remains canonical for clients that do not receive the field.
Evidence

Structured twin of the /context report, carried on the synthetic assistant message that delivers the markdown table.

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 →