**Feature request** Two pain points, one fix — an ordered `modeCycle` array in settings.json: 1. **Order (non-monotonic):** cycle is default → acceptEdits → plan → auto. Escalating semi-auto (acceptEdits) → full-auto with one Shift+Tab instead drops into plan — more restrictive — and can halt a task already permitted. 2. **Subset:** users who only use 2 of 3 modes hit a 2-tap guessing game and overshoot. Proposed: "permissions": { "modeCycle": ["plan", "default", "acceptEdits", "auto"] }

[Feature] Configurable Shift+Tab permission-mode cycle (order + subset)

Status Closed — not planned

Reported on v2.1.195

Maintainer reply None cached

Activity 1 comment · opened Jun 29, 2026 · closed Aug 16, 2026

Feature request

Two pain points, one fix — an ordered modeCycle array in settings.json:

Order (non-monotonic): cycle is default → acceptEdits → plan → auto. Escalating semi-auto (acceptEdits) → full-auto with one Shift+Tab instead drops into plan — more restrictive — and can halt a task already permitted.
Subset: users who only use 2 of 3 modes hit a 2-tap guessing game and overshoot.

Proposed:

"permissions": { "modeCycle": ["plan", "default", "acceptEdits", "auto"] }

Shift+Tab rotates only the listed modes, in the listed order. defaultMode already picks the start; this completes the story.

Prior art: #52332 (same ask, auto-closed as stale).

Environment