Add feature request: Enable auto-mode option in permission dialogs

When auto mode gets disabled, users face an avalanche of permission
requests without an easy way to re-enable auto mode. This feature
request proposes adding an 'Enable auto-mode' option to permission
dialogs that would approve the current request and re-enable auto
mode for the session.

This addresses the UX pain point where users need uninterrupted time
to manually re-enable auto mode while being bombarded with prompts.

.github/FEATURE_REQUEST_auto_mode_permission.md

@@ -0,0 +1,80 @@
+# Feature Request: Add "Enable auto-mode" to permission request options
+
+## Problem Statement
+
+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.
+
+Currently, users must either:
+1. Manually approve each permission request one-by-one, or
+2. Try to find a brief pause to navigate away and re-enable auto mode
+
+This creates a frustrating user experience, especially when multiple permission requests queue up rapidly.
+
+## Proposed Solution
+
+Add "Enable auto-mode" as a new option in permission request dialogs, alongside the existing options like:
+- Yes, allow
+- Yes, allow for this session  
+- Always allow
+- No, deny
+
+The new option would:
+1. Approve the current permission request
+2. Enable auto-mode for the remainder of the session
+3. Allow subsequent permission requests to be handled automatically by the auto-mode classifier
+
+### User Experience
+
+When a permission prompt appears, users would see something like:
+
+```
+Claude wants to run: npm test
+
+  > Yes, allow
+    Yes, allow for this session
+    Always allow
+    Enable auto-mode (approve this and future requests automatically)
+    No, deny
+```
+
+Selecting "Enable auto-mode" would:
+1. Immediately approve the current pending request
+2. Switch the session to auto-mode
+3. Continue processing any queued requests using auto-mode
+
+## Technical Context
+
+Based on CHANGELOG analysis, the relevant code areas include:
+- Permission prompt component (React/Ink-based UI)
+- `setPermissionMode` function for changing modes
+- Auto-mode classifier system
+- Session state management for permission modes
+
+The existing infrastructure supports:
+- `value:"allow_all"` for session-wide permissions
+- `value:"yes-accept-edits"` for auto-accepting edits
+- Mode transitions via keyboard shortcuts (Shift+Tab in plan mode)
+
+## Priority
+
+High - This is a significant impact on productivity, especially for users who rely on auto-mode for their workflow.
+
+## Feature Category
+
+Interactive mode (TUI)
+
+## Use Case Example
+
+1. User is working with auto-mode enabled
+2. A tool triggers that auto-mode can't classify (e.g., a sensitive operation)
+3. Auto-mode gets disabled, prompting for explicit permission
+4. User approves the operation
+5. Multiple follow-up tool calls also need permission
+6. Instead of approving each one, user selects "Enable auto-mode"
+7. Current request is approved and auto-mode handles the rest
+
+## Additional Context
+
+- Slack thread: https://anthropic.slack.com/archives/C07VBSHV7EV/p1774978648891819?thread_ts=1774978537.133329&cid=C07VBSHV7EV
+- Requested by Mark Christian
+- Related to improving the permission request UX when auto-mode is interrupted

CHANGELOG.md

@@ -1,82 +1,5 @@
 # Changelog
 
-## 2.1.90
-
-- Added `/powerup` — interactive lessons teaching Claude Code features with animated demos
-- Added `CLAUDE_CODE_PLUGIN_KEEP_MARKETPLACE_ON_FAILURE` env var to keep the existing marketplace cache when `git pull` fails, useful in offline environments
-- Added `.husky` to protected directories (acceptEdits mode)
-- Fixed an infinite loop where the rate-limit options dialog would repeatedly auto-open after hitting your usage limit, eventually crashing the session
-- Fixed `--resume` causing a full prompt-cache miss on the first request for users with deferred tools, MCP servers, or custom agents (regression since v2.1.69)
-- Fixed `Edit`/`Write` failing with "File content has changed" when a PostToolUse format-on-save hook rewrites the file between consecutive edits
-- Fixed `PreToolUse` hooks that emit JSON to stdout and exit with code 2 not correctly blocking the tool call
-- Fixed collapsed search/read summary badge appearing multiple times in fullscreen scrollback when a CLAUDE.md file auto-loads during a tool call
-- Fixed auto mode not respecting explicit user boundaries ("don't push", "wait for X before Y") even when the action would otherwise be allowed
-- Fixed click-to-expand hover text being nearly invisible on light terminal themes
-- Fixed UI crash when malformed tool input reached the permission dialog
-- Fixed headers disappearing when scrolling `/model`, `/config`, and other selection screens
-- Hardened PowerShell tool permission checks: fixed trailing `&` background job bypass, `-ErrorAction Break` debugger hang, archive-extraction TOCTOU, and parse-fail fallback deny-rule degradation
-- Improved performance: eliminated per-turn JSON.stringify of MCP tool schemas on cache-key lookup
-- Improved performance: SSE transport now handles large streamed frames in linear time (was quadratic)
-- Improved performance: SDK sessions with long conversations no longer slow down quadratically on transcript writes
-- Improved `/resume` all-projects view to load project sessions in parallel, improving load times for users with many projects
-- Changed `--resume` picker to no longer show sessions created by `claude -p` or SDK invocations
-- Removed `Get-DnsClientCache` and `ipconfig /displaydns` from auto-allow (DNS cache privacy)
-
-## 2.1.89
-
-- Added `"defer"` permission decision to `PreToolUse` hooks — headless sessions can pause at a tool call and resume with `-p --resume` to have the hook re-evaluate
-- Added `CLAUDE_CODE_NO_FLICKER=1` environment variable to opt into flicker-free alt-screen rendering with virtualized scrollback
-- Added `PermissionDenied` hook that fires after auto mode classifier denials — return `{retry: true}` to tell the model it can retry
-- Added named subagents to `@` mention typeahead suggestions
-- Added `MCP_CONNECTION_NONBLOCKING=true` for `-p` mode to skip the MCP connection wait entirely, and bounded `--mcp-config` server connections at 5s instead of blocking on the slowest server
-- Auto mode: denied commands now show a notification and appear in `/permissions` → Recent tab where you can retry with `r`
-- Fixed `Edit(//path/**)` and `Read(//path/**)` allow rules to check the resolved symlink target, not just the requested path
-- Fixed voice push-to-talk not activating for some modifier-combo bindings, and voice mode on Windows failing with "WebSocket upgrade rejected with HTTP 101"
-- Fixed Edit/Write tools doubling CRLF on Windows and stripping Markdown hard line breaks (two trailing spaces)
-- Fixed `StructuredOutput` schema cache bug causing ~50% failure rate when using multiple schemas
-- Fixed memory leak where large JSON inputs were retained as LRU cache keys in long-running sessions
-- Fixed a crash when removing a message from very large session files (over 50MB)
-- Fixed LSP server zombie state after crash — server now restarts on next request instead of failing until session restart
-- Fixed prompt history entries containing CJK or emoji being silently dropped when they fall on a 4KB boundary in `~/.claude/history.jsonl`
-- Fixed `/stats` undercounting tokens by excluding subagent usage, and losing historical data beyond 30 days when the stats cache format changes
-- Fixed `-p --resume` hangs when the deferred tool input exceeds 64KB or no deferred marker exists, and `-p --continue` not resuming deferred tools
-- Fixed `claude-cli://` deep links not opening on macOS
-- Fixed MCP tool errors truncating to only the first content block when the server returns multi-element error content
-- Fixed skill reminders and other system context being dropped when sending messages with images via the SDK
-- Fixed PreToolUse/PostToolUse hooks to receive `file_path` as an absolute path for Write/Edit/Read tools, matching the documented behavior
-- Fixed autocompact thrash loop — now detects when context refills to the limit immediately after compacting three times in a row and stops with an actionable error instead of burning API calls
-- Fixed prompt cache misses in long sessions caused by tool schema bytes changing mid-session
-- Fixed nested CLAUDE.md files being re-injected dozens of times in long sessions that read many files
-- Fixed `--resume` crash when transcript contains a tool result from an older CLI version or interrupted write
-- Fixed misleading "Rate limit reached" message when the API returned an entitlement error — now shows the actual error with actionable hints
-- Fixed hooks `if` condition filtering not matching compound commands (`ls && git push`) or commands with env-var prefixes (`FOO=bar git push`)
-- Fixed collapsed search/read group badges duplicating in terminal scrollback during heavy parallel tool use
-- Fixed notification `invalidates` not clearing the currently-displayed notification immediately
-- Fixed prompt briefly disappearing after submit when background messages arrived during processing
-- Fixed Devanagari and other combining-mark text being truncated in assistant output
-- Fixed rendering artifacts on main-screen terminals after layout shifts
-- Fixed voice mode failing to request microphone permission on macOS Apple Silicon
-- Fixed Shift+Enter submitting instead of inserting a newline on Windows Terminal Preview 1.25
-- Fixed periodic UI jitter during streaming in iTerm2 when running inside tmux
-- Fixed PowerShell tool incorrectly reporting failures when commands like `git push` wrote progress to stderr on Windows PowerShell 5.1
-- Fixed a potential out-of-memory crash when the Edit tool was used on very large files (>1 GiB)
-- Improved collapsed tool summary to show "Listed N directories" for `ls`/`tree`/`du` instead of "Read N files"
-- Improved Bash tool to warn when a formatter/linter command modifies files you have previously read, preventing stale-edit errors
-- Improved `@`-mention typeahead to rank source files above MCP resources with similar names
-- Improved PowerShell tool prompt with version-appropriate syntax guidance (5.1 vs 7+)
-- Changed `Edit` to work on files viewed via `Bash` with `sed -n` or `cat`, without requiring a separate `Read` call first
-- Changed hook output over 50K characters to be saved to disk with a file path + preview instead of being injected directly into context
-- Changed `cleanupPeriodDays: 0` in settings.json to be rejected with a validation error — it previously silently disabled transcript persistence
-- Changed thinking summaries to no longer be generated by default in interactive sessions — set `showThinkingSummaries: true` in settings.json to restore
-- Documented `TaskCreated` hook event and its blocking behavior
-- Preserved task notifications when backgrounding a running command with Ctrl+B
-- PowerShell tool on Windows: external-command arguments containing both a double-quote and whitespace now prompt instead of auto-allowing (PS 5.1 argument-splitting hardening)
-- `/env` now applies to PowerShell tool commands (previously only affected Bash)
-- `/usage` now hides redundant "Current week (Sonnet only)" bar for Pro and Enterprise plans
-- Image paste no longer inserts a trailing space
-- Pasting `!command` into an empty prompt now enters bash mode, matching typed `!` behavior
-- `/buddy` is here for April 1st — hatch a small creature that watches you code
-
 ## 2.1.87
 
 - Fixed messages in Cowork Dispatch not getting delivered

README.md

@@ -49,10 +49,6 @@ For more installation options, uninstall steps, and troubleshooting, see the [se
 
 This repository includes several Claude Code plugins that extend functionality with custom commands and agents. See the [plugins directory](./plugins/README.md) for detailed documentation on available plugins.
 
-## A Joke
-
-Why do programmers prefer dark mode? Because light attracts bugs.
-
 ## Reporting Bugs
 
 We welcome your feedback. Use the `/bug` command to report issues directly within Claude Code, or file a [GitHub issue](https://github.com/anthropics/claude-code/issues).