You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SDKArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release
Unclear What this changes in which requests the prompt tool or a hook ends up answering is not clear.
What
--permission-prompt-tool names an MCP tool that answers permission prompts in non-interactive mode. Some applications that embed Claude Code supply their own wording for these prompts.
When deciding how to handle a request, Claude Code now checks whether it carries wording from the host application, instead of whether it is marked for local display only. It also tells the prompt tool whether the wording came from the host, and passes the permission result on to the hook check that runs at the same time. Separately, "ask" decisions (where Claude Code should ask before acting) that carry host wording are now kept as asks.
Why
This affects applications that supply their own wording for permission prompts.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat this changes in which requests the prompt tool or a hook ends up answering is not clear.
