Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Plan execution dialog shows inconsistent options across parallel sessions [1 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#47824•Fetched 2026-04-15 06:41:16
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
selfmademayooselfmademayoo
Participants
github-actions[bot]github-actions[bot]selfmademayooselfmademayoo
Timeline (top)
labeled ×5closed ×1commented ×1

Error Message

Option 1 differs: "auto mode" vs. "auto-accept edits". Selecting "auto mode" results in an error on the MAX plan, while "auto-accept edits" works correctly. Selecting "auto mode" on a MAX plan causes an error every time, making it a confusing and frustrating option to encounter. Since both sessions share the same configuration, the inconsistency suggests a race condition or state management issue in the plan execution dialog.

Code Example

1. Yes, and use auto mode
2. Yes, manually approve edits
3. No, refine with Ultraplan on Claude Code on the web
4. Tell Claude what to change

---

1. Yes, auto-accept edits
2. Yes, manually approve edits
3. No, refine with Ultraplan on Claude Code on the web
4. Tell Claude what to change

---

{
    "permissions": {
      "defaultMode": "acceptEdits"
    }
  }
RAW_BUFFERClick to expand / collapse

Bug Description

When running two Claude Code sessions in parallel with the same global settings, the plan execution dialog ("Claude has written up a plan and is ready to execute") shows different options in each session:

Session A (incorrect):

1. Yes, and use auto mode
2. Yes, manually approve edits
3. No, refine with Ultraplan on Claude Code on the web
4. Tell Claude what to change

Session B (correct):

1. Yes, auto-accept edits
2. Yes, manually approve edits
3. No, refine with Ultraplan on Claude Code on the web
4. Tell Claude what to change

Option 1 differs: "auto mode" vs. "auto-accept edits". Selecting "auto mode" results in an error on the MAX plan, while "auto-accept edits" works correctly.

Expected Behavior

Both sessions should show "auto-accept edits" as option 1, matching the configured defaultMode: "acceptEdits". The "auto mode" option should either not appear on plans that don't support it, or it should work correctly.

Environment

  • Plan: Claude MAX (individual, not Team/Enterprise)
  • Global settings (~/.claude/settings.json): 
    {
  "permissions": {
    "defaultMode": "acceptEdits"
  }
}
  • Project-level settings: None (no project-specific .claude/settings.json exists)
  • Platform: macOS (Darwin 25.3.0)

Steps to Reproduce

  1. Configure defaultMode: "acceptEdits" in global settings
  2. Open two parallel Claude Code sessions
  3. Trigger plan mode in both sessions
  4. Observe that one session shows "auto mode" while the other shows "auto-accept edits"

Impact

Selecting "auto mode" on a MAX plan causes an error every time, making it a confusing and frustrating option to encounter. Since both sessions share the same configuration, the inconsistency suggests a race condition or state management issue in the plan execution dialog.

extent analysis

TL;DR

The most likely fix is to ensure consistent state management in the plan execution dialog to prevent the display of incorrect options.

Guidance

  • Verify that the defaultMode setting is being applied correctly in both sessions by checking the settings file and the application's behavior.
  • Investigate potential race conditions or state management issues in the plan execution dialog that could cause the inconsistency.
  • Check if the plan execution dialog is correctly handling the defaultMode setting for the MAX plan, and if it's correctly disabling or hiding the "auto mode" option when necessary.
  • Consider adding logging or debugging statements to track the state of the plan execution dialog and the defaultMode setting in both sessions.

Example

No code snippet is provided as it's not clearly supported by the issue, but an example of how to log the defaultMode setting in the plan execution dialog could be useful for debugging.

Notes

The issue may be specific to the MAX plan or the macOS platform, and further investigation is needed to determine the root cause. The defaultMode setting and its application in the plan execution dialog should be reviewed to ensure consistency.

Recommendation

Apply a workaround to ensure consistent state management in the plan execution dialog, such as adding a check to disable or hide the "auto mode" option when the defaultMode is set to "acceptEdits". This will prevent the error caused by selecting "auto mode" on a MAX plan.

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…
#logging issue#authentication issue#prompt issue#agent setup#task chaining

Still need to ship something?

×6

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

Back to top recommendations

TRENDING