[FEATURE] Allow configurable mode cycling - skip Accept Edits Mode in keyboard shortcuts

Status Closed — not planned
Maintainer reply None cached
Activity 8 comments · opened Sep 28, 2025 · closed Feb 28, 2026

Problem Statement

I primarily use only Plan Mode and Bypass Permissions Mode in my workflow. However, the current keyboard shortcut (Shift+Tab) cycles through all four modes with this sequence: Plan → Bypass → Normal → Accept Edits → Plan.

This creates an asymmetric experience:

  • Going from Plan to Bypass requires only 1 press of Shift+Tab
  • Going from Bypass back to Plan requires 3 presses of Shift+Tab (cycling through Normal and Accept Edits modes)

This asymmetry is inefficient and breaks my workflow rhythm, especially when frequently switching between these two modes.

Proposed Solution

Add a configuration option that allows users to customize which modes are included in the keyboard shortcut cycling. Specifically, I'd like to be able to exclude Normal Mode and Accept Edits Mode from the cycle, so the shortcut would only toggle between Plan Mode and Bypass Permissions Mode.

This could be implemented as:

  • A setting in Claude Code configuration to specify which modes to include in cycling
  • Or a checkbox/toggle option to "Skip unwanted modes in cycling"
  • Or predefined cycling presets (e.g., "All modes", "Plan + Bypass only", "Plan + Accept only", "Normal + Plan only")

Alternative Solutions

Currently, I work around this by:

  • Pressing Shift+Tab three times when going from Bypass to Plan
  • Sometimes using mouse clicks to change modes, but this slows down the keyboard-driven workflow
  • Creating custom keyboard shortcuts to simulate multiple presses

Other possible approaches could be:

  • Different keyboard shortcuts for each mode
  • A quick-access mode selector menu
  • Hotkeys to jump directly to specific modes
  • A "reverse cycle" shortcut (e.g., Ctrl+Shift+Tab to go backwards)

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

Example scenario:

  1. I'm working on a complex refactoring task that requires both planning and direct execution
  2. I start in Plan Mode to analyze the code structure
  3. Press Shift+Tab once to switch to Bypass Mode for rapid changes
  4. Need to return to Plan Mode to review the next steps
  5. Currently have to press Shift+Tab three times to get back to Plan Mode
  6. With this feature, I could press Shift+Tab once in both directions, creating a smooth toggle between the two modes I actually use

Additional Context

This enhancement would be particularly beneficial for power users who have established workflows with specific mode preferences. Many users may only use a subset of the available modes and would benefit from streamlined cycling options.

The current four-mode cycling (Plan → Bypass → Normal → Accept Edits → Plan) creates unnecessary friction for users who primarily work in just two modes, especially with the asymmetric number of key presses required.

---

Preflight Checklist:

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

View original on GitHub ↗

8 Comments

github-actions[bot] · 1 year ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/5343

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

wujekbogdan · 10 months ago

Use case example: I never use the "accept edits on" mode. I only turn it on by accident when cycling through modes (plan and regular mode). So for me it would be awesome if Claude simply allowed me to define available modes.

github-actions[bot] · 9 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

SixFive7 · 8 months ago

This issue is still relevant. An even better solution would be to have the hotkey configurable in Visual Studio as Shift-Tab is now conflicting with multiple other Keyboard shortcuts.

crespire · 8 months ago

I'd love also to be able to add custom modes.

github-actions[bot] · 7 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

pallani · 7 months ago

+1 — still want this. I'd love a modeCycle setting in settings.json to restrict Shift+Tab to a subset of modes, e.g.:

{
  "modeCycle": ["plan", "bypassPermissions"]
}

My workflow is almost exclusively plan → bypassPermissions. Cycling through acceptEdits and default adds friction since I never use them. A configurable cycle list would be a small, low-risk change that respects existing defaults while letting power users streamline their flow.

github-actions[bot] · 7 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.