{"version":"2.1.284","anchor":"new-telemetry-when-an-elicitation-result-hook-changes-the-us","canonical_anchor":"new-telemetry-when-an-elicitation-result-hook-changes-the-us","heading":"Claude Code now records when a hook changes your answer to an MCP question","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/new-telemetry-when-an-elicitation-result-hook-changes-the-us","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Claude Code now records when a hook changes your answer to an MCP question\n\nClaude Code now logs when an ElicitationResult hook changes the answer you gave an MCP server, or when a hook answered for you\n\n**What**\n\nMCP servers are outside tools that can ask you a question during a session. An `ElicitationResult` hook is a script you set up that runs after you answer. Claude Code now records usage data when such a hook changes the choice you made, and marks a response as answered by a hook when one answered instead of you. Nothing you see changes.\n\n**Why**\n\nThis is usage data only. It is a reminder that your hooks can change or supply answers to MCP questions.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}