Claude Code No Longer Carries Out an Unapproved Plan When a Session Resumes in Another Permission Mode
Claude CodeClaude Code 2.1.319 stops an interrupted plan-mode turn from being re-run or carried out when the session comes back in a different permission mode. This covers the CLAUDE_CODE_RESUME_INTERRUPTED_TURN setting and a window reload in the VS Code extension, where Claude could act on a plan the user had never approved. In VS Code the step now stops with a notice.
Key Takeaways
- Plan-mode steps are no longer re-run when a session resumes in a different permission mode with
CLAUDE_CODE_RESUME_INTERRUPTED_TURN. - In VS Code, a window reload could previously bring Claude back to carry out an unapproved plan.
- The interrupted step now stops with a notice instead of proceeding.
- Both fixes preserve the approve-before-run guarantee of plan mode.
- The change shipped in 2.1.319.
What changed
Plan mode exists so Claude can propose work that the user reviews before anything runs. Claude Code 2.1.319 closes two paths that could skip that review. Both involve an interrupted plan-mode turn coming back in a different permission mode.
Resumed turns no longer re-run a plan-mode step
With CLAUDE_CODE_RESUME_INTERRUPTED_TURN set, Claude Code can re-run a turn that was interrupted. Before this release, a turn interrupted in plan mode could be re-run when the session resumed in another permission mode. The release note lists this as a fix, so the turn is no longer re-run in that case.
VS Code window reloads no longer carry out an unapproved plan
In the VS Code extension, a window reload could bring a session back in a different permission mode, and Claude could then carry out a plan that was never approved. A step that was interrupted in plan mode now stops with a notice when the session comes back in another permission mode.
Why it matters
Both fixes preserve the rule that a plan is approved before it runs. The agent could otherwise act on something the user had only been asked to review.