{"version":"2.1.268","anchor":"new-claude-code-resume-reason-env-var-for-interrupted-turns","canonical_anchor":"new-claude-code-resume-reason-env-var-for-interrupted-turns","heading":"New CLAUDE_CODE_RESUME_REASON env var for interrupted turns","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-claude-code-resume-reason-env-var-for-interrupted-turns","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New CLAUDE_CODE_RESUME_REASON env var for interrupted turns\n\nNew CLAUDE_CODE_RESUME_REASON env var labels why an interrupted turn was resumed\n\n**What**\n\nA new environment variable, `CLAUDE_CODE_RESUME_REASON`, can now be set to a short lowercase tag (letters and underscores only, up to 64 characters) that becomes the recorded reason for resuming a turn that was interrupted. If the value doesn't match that pattern, Claude Code falls back to the default reason, `interrupted_turn`. A new `interruptedTurnUserMessageUuid` field also now records which prior user message an interruption corresponds to.\n\n**Why**\n\nThis gives tooling built around Claude Code a way to tag and later trace why a particular turn was resumed after an interruption, and to tie that resumption back to the specific user message it interrupted.\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_RESUME_REASON`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}