The /context report now includes structured totals plus per-tool, per-memory, per-agent and per-skill breakdowns.
What's wrong with this entry?
The context report now carries a structured payload as well as the usual markdown table: model, total tokens, the model's raw maximum, percentage used, and breakdowns by category, MCP tool, memory file, agent and skill.
- When you are over the window there is an extra section giving how many tokens over you are and which kind of limit was hit: the model's own believed limit, or the smaller window Claude Code compacts against.
- A matching schema with full descriptions was added to the stream-JSON type definitions. The schema shape existed before; the code that fills it in is new.
Structured twin of the /context report, over_limit
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.
-
v2.1.229
Session context is built lazily and cached per project root
Both mention context
-
v2.1.248
/context can hide the memory-files section
Both mention context
-
v2.1.248
/context remote failures can hide the raw error
Both mention context