claude-code - 💡(How to fix) Fix Auto mode still triggers permission prompts for PowerShell registry writes on Windows [1 participants]

Environment

• OS: Windows 11 Home 10.0.26200
• Shell: PowerShell (Windows PowerShell 5.1)
• Claude Code model: Opus 4.7 (claude-opus-4-7[1m])
• Mode: Auto mode (explicitly enabled)

Problem

In auto mode — documented as "continuous, autonomous execution" with instruction to "execute immediately" and "minimize interruptions" — the sandbox still prompts for permission on every individual PowerShell command that writes to the registry (Set-ItemProperty, Remove-ItemProperty, Stop-Process).

Repeatable example: a single PowerShell tool call that:

1. Kills processes with Stop-Process
2. Deletes HKCU Run entries with Remove-ItemProperty
3. Writes UWP startup task state with Set-ItemProperty

...triggers multiple approval dialogs mid-execution despite auto mode being active and the operation being explicitly user-requested.

Expected

Auto mode should let the agent execute low-risk, user-requested local operations (registry writes scoped to HKCU, killing user-space processes) without mid-task permission prompts. The per-command prompting interrupts the "autonomous" contract and defeats the purpose of the mode.

Actual

Every Stop-Process / Remove-ItemProperty / Set-ItemProperty call is individually gated by the sandbox, producing a permission prompt per command even when bundled into one tool invocation.

Suggested fix

Either (a) treat HKCU-scoped registry writes and user-owned process kills as auto-mode-allowed by default, or (b) expose a clearer auto-mode allowlist override so users can pre-approve these classes of operations once per session instead of per-command.

Additional notes

Reported by user "Thanos" (Europe/London). User's quote: "you are in auto mode and you keep asking permissions".