{"version":"2.1.317","anchor":"plan-approval-dialog-drops-some-options-when-the-model-needs","canonical_anchor":"plan-approval-dialog-drops-some-options-when-the-model-needs","heading":"Plan approval stops offering modes some models cannot use","tier":"notice","area":"Plan Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/plan-approval-dialog-drops-some-options-when-the-model-needs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Plan approval stops offering modes some models cannot use\n\nWhen a model needs auto or plan mode, the plan approval choices drop the bypass-permissions option and the default-mode option, and offer auto mode\n\n**Unclear.** Which models need auto or plan mode, and so get the shorter list of choices, is not stated.\n\n**What**\n\nWhen Claude finishes a plan in plan mode (where it plans without changing anything), it asks you to approve the plan and pick how to continue. For models that need to run in auto mode or plan mode, and where auto mode is available, those choices are now different:\n\n- the bypass permissions option, which lets Claude act without asking, is not offered\n\n- the option to keep the current context and continue in the default mode is left out\n\n- the auto mode option is offered instead\n\nPreviously the bypass option appeared whenever that mode was available, and the keep-context default-mode option was always shown.\n\n**Why**\n\nSome models can only run in auto mode or plan mode, so the approval dialog no longer offers modes those models cannot use.\n\n- Area: Plan Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}