surshar / claude-code
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
Built by Anthropic · github.com/anthropics
| 1 | # Feature Request: Add "Enable auto-mode" to permission request options |
| 2 | |
| 3 | ## Problem Statement |
| 4 | |
| 5 | When auto mode gets turned off (for various reasons like encountering a tool that requires explicit permission), users face an avalanche of back-to-back permission requests. This makes it very difficult to get the 2 seconds of uninterrupted time needed to navigate to settings and re-enable auto mode. |
| 6 | |
| 7 | Currently, users must either: |
| 8 | 1. Manually approve each permission request one-by-one, or |
| 9 | 2. Try to find a brief pause to navigate away and re-enable auto mode |
| 10 | |
| 11 | This creates a frustrating user experience, especially when multiple permission requests queue up rapidly. |
| 12 | |
| 13 | ## Proposed Solution |
| 14 | |
| 15 | Add "Enable auto-mode" as a new option in permission request dialogs, alongside the existing options like: |
| 16 | - Yes, allow |
| 17 | - Yes, allow for this session |
| 18 | - Always allow |
| 19 | - No, deny |
| 20 | |
| 21 | The new option would: |
| 22 | 1. Approve the current permission request |
| 23 | 2. Enable auto-mode for the remainder of the session |
| 24 | 3. Allow subsequent permission requests to be handled automatically by the auto-mode classifier |
| 25 | |
| 26 | ### User Experience |
| 27 | |
| 28 | When a permission prompt appears, users would see something like: |
| 29 | |
| 30 | ``` |
| 31 | Claude wants to run: npm test |
| 32 | |
| 33 | > Yes, allow |
| 34 | Yes, allow for this session |
| 35 | Always allow |
| 36 | Enable auto-mode (approve this and future requests automatically) |
| 37 | No, deny |
| 38 | ``` |
| 39 | |
| 40 | Selecting "Enable auto-mode" would: |
| 41 | 1. Immediately approve the current pending request |
| 42 | 2. Switch the session to auto-mode |
| 43 | 3. Continue processing any queued requests using auto-mode |
| 44 | |
| 45 | ## Technical Context |
| 46 | |
| 47 | Based on CHANGELOG analysis, the relevant code areas include: |
| 48 | - Permission prompt component (React/Ink-based UI) |
| 49 | - `setPermissionMode` function for changing modes |
| 50 | - Auto-mode classifier system |
| 51 | - Session state management for permission modes |
| 52 | |
| 53 | The existing infrastructure supports: |
| 54 | - `value:"allow_all"` for session-wide permissions |
| 55 | - `value:"yes-accept-edits"` for auto-accepting edits |
| 56 | - Mode transitions via keyboard shortcuts (Shift+Tab in plan mode) |
| 57 | |
| 58 | ## Priority |
| 59 | |
| 60 | High - This is a significant impact on productivity, especially for users who rely on auto-mode for their workflow. |
| 61 | |
| 62 | ## Feature Category |
| 63 | |
| 64 | Interactive mode (TUI) |
| 65 | |
| 66 | ## Use Case Example |
| 67 | |
| 68 | 1. User is working with auto-mode enabled |
| 69 | 2. A tool triggers that auto-mode can't classify (e.g., a sensitive operation) |
| 70 | 3. Auto-mode gets disabled, prompting for explicit permission |
| 71 | 4. User approves the operation |
| 72 | 5. Multiple follow-up tool calls also need permission |
| 73 | 6. Instead of approving each one, user selects "Enable auto-mode" |
| 74 | 7. Current request is approved and auto-mode handles the rest |
| 75 | |
| 76 | ## Additional Context |
| 77 | |
| 78 | - Slack thread: https://anthropic.slack.com/archives/C07VBSHV7EV/p1774978648891819?thread_ts=1774978537.133329&cid=C07VBSHV7EV |
| 79 | - Requested by Mark Christian |
| 80 | - Related to improving the permission request UX when auto-mode is interrupted |