You'll notice
Useful3 Signal3
Some permission prompts now open on No, with digit shortcuts hidden so you cannot approve accidentally.
What's wrong with this entry?
Anonymous. No account, no email.
What
A permission request can now be marked so its dialog opens focused on No, with the decline option listed first and the digit shortcuts hidden, so an ask "must not be approvable by a single stray keystroke". It is set per request by whatever raises the prompt rather than by any setting, and a couple of internal permission results, including some Artifact-related asks, already use it in this build.
Details
- The field is named
default_to_noand carries guidance that a host "should not pre-select approve when set". - No flag, setting or environment variable gates it, and there is no way to turn it on for all prompts.
- The flag travels over the control protocol Claude Code uses to talk to a host UI, added to the set of boolean permission fields carried across that boundary.
- Editors and other hosts that draw their own permission prompts have to honour it themselves; nothing forces the behaviour on them, and a host that ignores it falls back to its usual prompt with approve selectable as normal.
Evidence
a terminal-style prompt opens on its decline option and takes no digit shortcut, default_to_no
Strings lifted out of the shipped bundle, so the claim above can be checked against them.