Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

SDK/print-mode turn telemetry reworked

The turn-tracking and shutdown telemetry for SDK/print mode runs was rewritten, adding a tool-call breakdown and consolidating shutdown reporting

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal0worth watching, 1 to 5
AreaSDKwhat it touches
KindInternal Changesin v2.1.269,
Group of 2 Under the hood

The turn-tracking and shutdown telemetry for SDK/print mode runs was rewritten, adding a tool-call breakdown and consolidating shutdown reporting

What

  • Turn execution in SDK/non-interactive (print) mode now uses two new internal classes: one that tracks whether a turn is in flight and emits tengu_sdk_result (or tengu_sdk_session_crash) on shutdown or crash, and another that runs each turn and emits tengu_sdk_result with a new breakdown of tool call counts into MCP tool calls, tool-search calls, and built-in tool calls.
  • A companion class manages adopting a model override at the end of a turn and logs tengu_print_model_override_adopted with the previous and new model.
  • The telemetry sent when a run is shut down mid-way (status terminated) now goes through one shared method (reportTerminatedOnShutdown) instead of being built inline, so aborted/runPhase/exitCode reporting is consistent.

Why This gives clearer visibility into how SDK-driven and print-mode sessions end and what kinds of tool calls they made, and makes the shutdown telemetry more consistent and easier to maintain.

See this entry in the whole of v2.1.269 →

Feedback