{"version":"2.1.315","anchor":"elicitation-control-requests-now-send-a-cancel-on-answer-be","canonical_anchor":"elicitation-control-requests-now-send-a-cancel-on-answer-be","heading":"Answering an input request can also cancel it, behind a remote switch","tier":"soon","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/elicitation-control-requests-now-send-a-cancel-on-answer-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Answering an input request can also cancel it, behind a remote switch\n\nWhen an answer settles a request for user input, Claude Code can now also send a cancel for that request, a change that falls back to off\n\n**What**\n\nAn elicitation is a request for input from you, for example a question an MCP server asks during a task. When Claude Code runs under another program, such as an app built with the SDK or a remote host, that program can answer such a request.\n\nWhen an answer settles an elicitation, Claude Code can now also send a cancel for the same request. This is controlled by a setting Anthropic can change from its servers, and it falls back to off when the servers send nothing.\n\n**Why**\n\nThis changes how Claude Code and a host program finish off an input request once it has been answered.\n\n- Flag `tengu_humming_waterfall`: Not enough to say (read for one account on one subscription tier against v2.1.315; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}