{"version":"2.1.283","anchor":"mcp-elicitation-hooks-require-a-project-bound-session","canonical_anchor":"mcp-elicitation-hooks-require-a-project-bound-session","heading":"Elicitation hooks now need a session tied to a project","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/mcp-elicitation-hooks-require-a-project-bound-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Elicitation hooks now need a session tied to a project\n\nElicitation and ElicitationResult hooks now use the real session and raise an error when that session has no project\n\n**Unclear.** Whether the error is caught, and whether you would see it, is not clear.\n\n**What**\n\nThe `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.\n\n**Why**\n\nHooks on these events could behave differently in sessions that have no project, since they now fail there instead of using the current directory.\n\n- Area: Hooks\n- Names: `Elicitation`, `ElicitationResult`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}