Unclear Whether the error is caught, and whether you would see it, is not clear.
What
The Elicitation and ElicitationResult hooks run when an MCP server asks you for input and after you answer. They now receive the actual session (one conversation with Claude Code) and raise an error when that session is not tied to a project. Before, they built a stand-in session from the current directory.
Why
Hooks on these events could behave differently in sessions that have no project, since they now fail there instead of using the current directory.
Names in the bundleElicitationElicitationResult
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up ElicitationResult, on Claude Code changelog.
* Fixed `{"decision":"block"}` returned by Elicitation and ElicitationResult hooks being ignored; it now declines the MCP elicitation, as exit code 2 doeschangelog see the edit
Confirmed since
Anthropic's documentation has since written up Elicitation, on Claude Code changelog.
* Fixed `{"decision":"block"}` returned by Elicitation and ElicitationResult hooks being ignored; it now declines the MCP elicitation, as exit code 2 doeschangelog see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether the error is caught, and whether you would see it, is not clear.
Anthropic's documentation agrees
Anthropic's documentation has since written up Elicitation, on Claude Code changelog.