[Compat] Claude Code v2.1.236: SIGTERM in print/SDK mode no longer writes interrupted-turn/synthetic-denial entries

[delexw]

Claude Code Version

v2.1.236 (August 19, 2026)

Change Description

SIGTERM in print/SDK mode no longer records an interrupted turn or synthetic tool denials before exiting; running commands are still terminated and the process still exits with code 143

Previously, when a print-mode (-p) or SDK-driven session received SIGTERM, Claude Code would write an "interrupted turn" record and synthetic tool-denial entries into the transcript before exiting. That no longer happens — the process now just terminates running commands and exits.

Impact on claude-code-trace

This changes what shows up in the JSONL for a SIGTERM'd print/SDK session going forward: previously a tool_use block killed mid-flight would likely be followed by a synthetic denial tool_result and an "interrupted" marker; now the transcript can simply end mid-turn with a dangling tool_use that has no matching tool_result, and no explicit "interrupted" entry at all.

If claude-code-trace's UI assumes every tool_use id eventually gets a matching tool_result, or relies on an "interrupted turn" marker to render a distinct "cancelled" state, sessions ended this way (2.1.236+, print/SDK mode) will instead just look like the conversation silently stopped mid tool call.

Severity: Moderate

Affected Parser Code

• src-tauri/src/parser/entry.rs - Entry struct / tool_use ↔ tool_result matching logic
• Any UI state that renders "interrupted" sessions based on a specific synthetic entry rather than "last entry is an unmatched tool_use"

Suggested Fix

• Ensure the UI already handles (or add handling for) a tool_use block with no corresponding tool_result in the same session — render it as pending/unknown rather than erroring — since this is now an expected end state for killed print/SDK sessions.

Source

Claude Code v2.1.236 release notes, August 19, 2026.