{"version":"2.1.288","anchor":"plan-exit-approval-switches-to-default-mode-on-success-imme","canonical_anchor":"plan-exit-approval-switches-to-default-mode-on-success-imme","heading":"Approving a plan now switches Claude Code back to default mode","tier":"notice","area":"Plan Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/plan-exit-approval-switches-to-default-mode-on-success-imme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Approving a plan now switches Claude Code back to default mode\n\nApproving Claude's plan to leave plan mode now switches the session to default permission mode, and the mode indicator shows an \"on\" hint\n\n**Unclear.** It is not clear what the busy state for slash commands changes for you in practice.\n\n**What**\n\nPlan mode is a mode where Claude works out a plan before it is allowed to change anything. When you approve a plan and leave plan mode, Claude Code now switches the session to the default permission mode, unless the approval step itself was cancelled. Before, approving a plan had no follow-up mode change.\n\nTwo smaller changes come with it:\n\n- Slash commands that run straight away are now marked as busy while they run, and that state is released when they finish.\n\n- When the mode changes, a short `[... on]` hint appears if the new mode matches the one shown.\n\n**Why**\n\nThese are small fixes to how the interface behaves. After approving a plan, you end up in default mode rather than in whatever state the session was left in.\n\n- Area: Plan Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}