Unclear It is not clear which requests carry a client-supplied tool-use id, so when the default handler takes over.
What
--permission-prompt-tool names an MCP tool that answers permission prompts when Claude Code runs without you watching. Some requests now skip it and go to Claude Code's default permission handling instead. This happens when both of these are true:
- the request carries a tool-use id supplied by the client
- the MCP tool has no input schema, the description of what input it accepts
The check for whether the prompt tool's server has gone away now has three outcomes instead of two.
Why
This changes how permission prompts are routed for programs that drive Claude Code through the SDK.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear which requests carry a client-supplied tool-use id, so when the default handler takes over.