Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Allow user-level setting to default ExitPlanMode to acceptEdits (or hide auto mode) [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#50828•Fetched 2026-04-20 12:11:56
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
1
Author
AvimarzanAvimarzan
Participants
AvimarzanAvimarzangithub-actions[bot]github-actions[bot]
Timeline (top)
commented ×2labeled ×2subscribed ×1

Fix Action

Fix / Workaround

The only workarounds are to manually pick acceptEdits each time or Shift+Tab cycle after approval — both add friction to a per-plan flow.

RAW_BUFFERClick to expand / collapse

Request

Add a user-level setting in settings.json to control the ExitPlanMode picker — either:

(a) set the default/highlighted option to acceptEdits instead of auto, OR (b) hide the auto-mode option entirely when users don't want it.

Motivation

Before auto mode existed, exiting plan mode landed in acceptEdits. That was the expected flow for users who want: plan → review plan → apply edits automatically, while still being asked for non-edit actions (Bash, etc.).

With auto mode now the prominent option on the picker, users who prefer the old acceptEdits flow have no user-level way to restore it:

The only workarounds are to manually pick acceptEdits each time or Shift+Tab cycle after approval — both add friction to a per-plan flow.

Proposed

A permissions.planExitDefault setting (or similar) accepting "auto" | "acceptEdits" | "manual", user-settable in ~/.claude/settings.json.

Related

  • #49829 — analogous request for bypassPermissions users losing their mode on plan exit
  • #47637 — docs gap around plan-exit mode behavior

Version

2.1.113 (Claude Code)

extent analysis

TL;DR

To address the issue, consider adding a permissions.planExitDefault setting in settings.json to allow users to control the ExitPlanMode picker.

Guidance

  • Review the proposed permissions.planExitDefault setting and its potential values ("auto", "acceptEdits", "manual") to determine if it meets the requirements.
  • Investigate the feasibility of making this setting user-settable in ~/.claude/settings.json.
  • Examine the relationship between this proposed setting and existing settings like permissions.disableAutoMode to avoid conflicts.
  • Consider the potential impact on users who rely on the current auto mode behavior and how to mitigate any disruption.

Example

No code snippet is provided as the issue focuses on configuration and setting changes rather than code modifications.

Notes

The solution may require updates to the Claude Code documentation, particularly in relation to plan-exit mode behavior, as mentioned in the related issues (#47637).

Recommendation

Apply workaround: Add the proposed permissions.planExitDefault setting to provide users with control over the ExitPlanMode picker, as this directly addresses the requested functionality and user need.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#response parsing#generation error#database connection#vector store#embedding generation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING