[FEATURE] Reset mode after running /clear

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When the /clear command is run, the current mode remains unchanged.

This can be unintuitive, especially when the mode has been changed temporarily. Users may expect /clear to return the application to a known default state, including the default mode defined in settings.json. Currently, there is no way to configure this behavior.

Proposed Solution

Introduce an optional configuration setting in settings.json that controls whether the active mode is reset when /clear is executed.

For example:

• The default mode would continue to be defined in settings.json
• A new setting (e.g. "resetModeOnClear": true) would instruct Claude to reset the mode back to the configured default whenever /clear is run.
• If the setting is disabled or omitted, existing behavior would remain unchanged.

This approach preserves backward compatibility while giving users explicit control over mode-reset behavior.

Alternative Solutions

CLI or interactive settings option

Expose a configuration toggle via a CLI settings menu or command instead of (or in addition to) settings.json.

Create a new command adjacent to /clear (not preferred)

Create a new command along the lines of /reset that resets the mode in addition to what /clear does. This adds more complexity and can confuse users with two very similar commands.

Always reset mode on /clear (not preferred)

Make /clear unconditionally reset the mode to the default. This simplifies behavior but removes flexibility for users who prefer the current behavior.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

My work flow

• The default mode in settings.json is set to plan.
• I begin a task using Claude in plan mode to work through requirements and structure a solution.
• Once the plan is finalized, I switch to accept edits mode so that changes are automatically accepted and applied.
• After completing that task, I run the /clear command to start a new task.

At this point, I expect the application to return to its default state, including the plan mode defined in settings.json. However, the application remains in accept edits mode.

As a result, when I issue my next command:

• The command is immediately accepted and executed
• I lose the opportunity to plan or review changes
• This behavior is unexpected and can lead to unintended modifications

Resetting the mode to the configured default on /clear would prevent this issue and better align with user expectations of a “clean slate.”

Additional Context

_No response_