{"version":"2.1.309","anchor":"resume-can-show-tool-calls-that-were-cut-off-claude-code-re","canonical_anchor":"resume-can-show-tool-calls-that-were-cut-off-claude-code-re","heading":"Resumed sessions can keep tool calls that were cut off","tier":"soon","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/resume-can-show-tool-calls-that-were-cut-off-claude-code-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Resumed sessions can keep tool calls that were cut off\n\nA new CLAUDE_CODE_RESUME_SHOWS_CUT_OFF_CALLS setting lets a resumed session show tool calls that were interrupted mid-turn\n\n**Unclear.** Two further conditions it checks were not identified, so it is unclear whether setting the variable alone turns this on for a local user.\n\n**What**\n\nWhen you resume a session whose last prompt was interrupted, Claude Code can now treat that turn as one that can be picked up again, even if some tool calls (actions Claude had started, such as running a command or editing a file) were cut off before they got an answer. With this switched on, those cut-off calls stay visible in the resumed conversation.\n\nThis is controlled by the `CLAUDE_CODE_RESUME_SHOWS_CUT_OFF_CALLS` environment variable, which is a named value you set in your shell before starting Claude Code. It does nothing unless it is set to true. It also has to pass a server-side safety switch, which stays out of the way unless the server sends otherwise, and two further internal conditions.\n\n- Local use: you get this only by setting `CLAUDE_CODE_RESUME_SHOWS_CUT_OFF_CALLS` yourself.\n\n- Hosted remote sessions: when Claude Code restarts the same session on a new worker, it sets the variable to `1` for you and uses a different resume prompt.\n\nThe note Claude receives about calls that were lost has been reworded, and a new version of it tells Claude that such calls are no longer shown above.\n\n**Why**\n\nAfter an interruption, Claude can see which actions it had started and not finished, instead of resuming without them. For remote sessions that get restarted, this happens without any setting.\n\n- Flag `tengu_mutable_phoenix_killswitch`: Not enough to say (read for one account on one subscription tier against v2.1.309; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Flag `tengu_vast_journal`: Not enough to say (read for one account on one subscription tier against v2.1.309; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}