[FEATURE] Change Default Plan Mode Exit Option

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/18576
2. https://github.com/anthropics/claude-code/issues/18523
3. https://github.com/anthropics/claude-code/issues/2988

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

I wouldn't call this a duplicate because it provides more context on why the "clear context" setting is problematic and proposes various solutions.

The new "clear context" option can definitely be useful, but I agree it would be nice to make this default configurable. @jasonevines gave a good rundown of reason why clearing context isn't always desired.

The new "clear context" option can definitely be useful, but I agree it would be nice to make this default configurable. @jasonevines gave a good rundown of reason why clearing context isn't always desired.

I would go further to say that clearing context is almost never desired for tasks involving more than a small amount of intricacy.

Boris Cherny is touting this default context clearing on X, claiming, "We found this helps keep Claude on track longer, and significantly improves plan adherence."

I question how that was determined. It's flatly wrong for anything more than simple work without complex strategy or discovery.

I would go further to say that clearing context is almost never desired for tasks involving more than a small amount of intricacy.

This is true probably for how most people use it, but i don't think it's inherently true. That being said, I don't think it's a good default given to how most people work currently.

But back to that point, when I'm working on a large task I often intentionally start a new conversation when I'm ready to implement, so that the agent has more context space to work with. The key is to make sure your written plan has everything needed to understand and complete the implementation.

I do this by telling Claude something like "I'm going to hand this off to another Claude agent to implement, make sure our plan has all the information the next agent will need to understand and implement this successfully." Then I start a new chat and point it to the plan file we generated in the previous chat.

@timdmackey To address the context issues during complex development, I've built a phased skill workflow (inspired by and extended from feature-dev) wherein an orchestration agent (the conversation agent) coordinates custom-tailored subagents (sometimes multiple at a time depending on Claude's judgment of task needs) through discovery, planning, implementation, code review, and strategy review. The orchestrator starts plan mode and a to-do list at the very start of the workflow and then exits plan mode before implementation.

With a workflow like this, the orchestrator can maintain context on the problem and the strategy through the whole process much of the time. And if I do need to compact, triggering the workflow again is usually enough to get Claude back on track without missing a step.

I almost had a conniption fit running the workflow after the default context clearing mechanic for exiting plan mode dropped, when I didn't realize yet what had happened.

See related issue #18878

This could yield such awesome setups, 10x than ralph-loop.

Alternative Solution

Add a setting (e.g., "questionSafetyOption": true) that inserts a neutral, no-op first option at the top of every AskUserQuestion prompt. This option would do nothing when selected, effectively acting as a guard against accidental Enter presses.

For example, the no-op option could be labeled something like:

• "(No selection — ask me again)"
• "(Skip — re-ask this question)"

When selected, Claude would simply re-ask the same question or treat it as if no answer was given.

After living with this feature for the last month, I'd say it's definitely useful but I'd still rather it not be in the default position. I use the "clear context" option 50% of the time but there have been a couple times were I accidentally triggered it and didn't want to.

The context-clearing default hurts because compaction is inherently lossy — no AI summary perfectly preserves the intent and strategy a human put into a plan. Plan documents are the real answer: human-curated artifacts you can re-read verbatim after any reset. But right now plans have no lifecycle — an approved plan gets silently overwritten the next time you enter plan mode, so there's nothing to reload. If plans had identity and status tracking, clearing context would be safe because the approved plan persists and Claude can pick it back up. See #29445 for the broader proposal.

The default "clear context and auto-accept" option on plan mode exit is indeed surprising when you want to keep your planning context.
Workaround 1 — Use Shift+Tab to switch modes instead of ExitPlanMode:
Pressing Shift+Tab cycles between permission modes (plan → auto-accept → bypass → plan) without clearing context. This avoids the ExitPlanMode prompt entirely.
Workaround 2 — Save critical context in CLAUDE.md before exiting:
Before exiting plan mode, tell Claude:

Save the plan we just created as a comment in CLAUDE.md

This persists the planning context in a file that survives context clears.
Workaround 3 — Use mission.md or a task file:

<!-- CLAUDE.md -->
Before exiting plan mode, always write the agreed plan to tasks/current-plan.md.
Read tasks/current-plan.md at the start of every session.

This ensures the plan persists regardless of how plan mode is exited.
Workaround 4 — Select "No" and manually switch:
When the ExitPlanMode dialog appears, select the option that doesn't clear context (if available). Then manually adjust your permission mode with Shift+Tab.