Claude Agent SDK 0.3.230 started attaching a structured twin of the /context report — model, token totals, over-limit detail, and per-category/MCP-tool/memory-file/agent breakdowns — to the synthetic assistant message that delivers the markdown table. The Claude normalizer now carries that context_usage object verbatim as providerMetadata on the message’s first block (or a message.metadata event when the frame has no blocks), joining the existing wrapper-sibling carries. Clients can render a context-usage card straight from the fold instead of parsing markdown.

OpenAI Agents 0.16 supported

@openai/agents 0.16.0 landed four days after 0.15.0, again outside our declared peer range. The study came back as clean as it gets: both consumed wire files are byte-identical to 0.15.0 (run-item event names, protocol items, and the full literal inventory all zero-delta) — the minor is internal to agent/handoff/runner plumbing. The range widens to >=0.2.0 <0.17 and the npm peer warning disappears.

Verification refresh

• Claude Agent SDK 0.3.233 — SDKMessage union unchanged (39 members); the only stream-wire addition is the context_usage sibling carried above.
• genai 2.17.1 (under ADK 1.6.0) — the Part surface is byte-identical.
• Vercel AI 7.0.66 with the aligned @ai-sdk/mcp 2.0.32 / @ai-sdk/openai 4.0.42 trio — provider-utils pin unchanged at 5.0.27, both patches crossed the nightly’s family-forced leg silently.

The compatibility tables on each npm page carry the dated evidence.