Feature Request: Allow configuring or disabling 'clear context' default when accepting plans

Feature Request

Request: Add the ability to re-order or disable the "clear context" default option when accepting Claude's plan.

Problem

When Claude generates a plan, the default option presented is to execute the plan and clear context. This creates a user flow where valuable conversation information not captured in the plan is lost.

Example Scenario

1. Have a conversation with Claude about two problems you want to fix
2. Ask Claude to come up with a plan to fix one problem
3. Result: Claude generates the plan, and the default option is "work on the plan and clear context"
4. Impact: Pressing Enter (accepting the default) forgets valuable information from the conversation that wasn't included in the plan

Current Workaround

Don't hit Enter to accept the default—manually select a different option.

Why the Workaround is Inadequate

1. Muscle memory: Accepting the first option is the natural, easy flow
2. User expectations: If Claude offers to clear context, users may reasonably expect that clearing is safe
3. No recovery awareness: Users could theoretically resume the session before context was cleared, but Claude won't be aware that a "fork" happened

Observations

The "talk about task → generate plan → clear context → execute" flow works well for focused, single-task workflows. I use it frequently and find it valuable.

However, Claude is a versatile tool. There are legitimate reasons for users to:

• Discuss multiple problems before planning
• Plan and work on only a component of the overall work
• Maintain context about related issues while executing a plan

The "clear and execute" option is potentially destructive. Users should be able to configure this behavior.

Proposed Solutions

Option A - User Configuration: Allow users to configure Claude to:

1. Disable the "clear context" behavior entirely, or
2. Adjust the order of options presented (making "execute without clearing" the default)

Option B - Smarter Context Awareness: Claude could make a context-aware decision:

• If the plan covers all remaining work → present "clear and execute" as default
• If there's unaddressed context → present "execute without clearing" as default

(Option B may have inference overhead considerations)

Summary

I recognize the value of the current "clear and execute" pattern for focused workflows. However, since context clearing is destructive and irreversible, I believe users should have control over this default behavior.