{"version":"2.1.288","anchor":"mcp-elicitation-dialog-gets-userconfirmscompletion-wouldta","canonical_anchor":"mcp-elicitation-dialog-gets-userconfirmscompletion-wouldta","heading":"Dialogs where an MCP server asks you for input can ask you to confirm you are done","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/mcp-elicitation-dialog-gets-userconfirmscompletion-wouldta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Dialogs where an MCP server asks you for input can ask you to confirm you are done\n\nThe dialog an MCP server uses to ask you for input can now be told you will confirm when you are done, and can check whether an answer would be taken\n\n**Unclear.** It is not established whether this dialog is linked to the step-up sign-in setting for MCP servers whose default changed.\n\n**What**\n\nMCP (Model Context Protocol) servers connect Claude Code to outside tools and services. Such a server can ask you for information through an elicitation, a dialog that pauses and asks you to respond.\n\nThe elicitation dialog now receives two more pieces of information:\n\n- whether the server expects you to confirm that you have finished\n\n- a way to check whether an answer would be accepted\n\nPreviously it was given only the server's name, the request and a way to send your response.\n\n**Why**\n\nThis prepares the dialog for requests where you complete a step and then confirm it, rather than only typing an answer.\n\n- Flag `tengu_mcp_step_up_auth_dialog`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.288; this account: on, anonymous baseline: on, compiled default: on) 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: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}