[DOCS] Shift+Tab keyboard shortcut collision in Plan Mode

Documentation Type

Unclear/confusing documentation

Documentation Location

• https://code.claude.com/docs/en/interactive-mode#general-controls - https://code.claude.com/docs/en/common-workflows#how-to-use-plan-mode

Section/Topic

The "General controls" keyboard shortcut table and the "How to use Plan Mode" instructional section.

Current Documentation

The "General controls" table on the Interactive Mode page lists:

Shift+Tab or Alt+M: Toggle permission modes (Auto-Accept, Plan, Normal).

The "How to use Plan Mode" section on the Common Workflows page states:

"You can switch into Plan Mode during a session using Shift+Tab to cycle through permission modes."

What's Wrong or Missing?

There is a functional collision for the Shift+Tab shortcut that is not addressed in the main documentation. While the docs state it is used for cycling permission modes, the version 2.1.2 updates introduced a context-specific behavior: "Added Shift+Tab keyboard shortcut in plan mode to quickly select 'auto-accept edits' option."

This creates ambiguity: if a user is already in Plan Mode, does Shift+Tab move them back to Normal Mode, or does it trigger the "auto-accept edits" UI selection? The documentation does not explain how this collision is resolved or if users should prioritize Alt+M for mode cycling once Plan Mode is active.

Suggested Improvement

Update the "General controls" table and Plan Mode instructions to clarify the dual-purpose of the key.

Suggested text for the shortcuts table:

Shift+Tab: Toggle permission modes. Note: When Plan Mode is active, this shortcut is used to select the 'auto-accept edits' option; use Alt+M to cycle out of Plan Mode.

Impact

High - Prevents users from using a feature

Additional Context

• This logic was introduced in the 2.1.2 release.
• Related documentation for context: https://code.claude.com/docs/en/interactive-mode
• Providing clarity here prevents user frustration when they attempt to exit Plan Mode but inadvertently trigger a UI selection instead.