{"version":"2.1.257","anchor":"mcp-elicitation-handling-reworked-into-a-stateful-class-with","canonical_anchor":"mcp-elicitation-handling-reworked-into-a-stateful-class-with","heading":"MCP elicitation handling reworked into a stateful class with 'waiting' UI and URL-mode flows","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/mcp-elicitation-handling-reworked-into-a-stateful-class-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### MCP elicitation handling reworked into a stateful class with 'waiting' UI and URL-mode flows\n\nMCP elicitation gets a distinct waiting dialog with a Skip confirmation action and can be completed by the server.\n\nMCP elicitation handling moved from a single async function into a stateful class that tracks per-URL elicitation flows. It adds a distinct `mcp_elicitation_waiting` dialog state, shown after accepting a URL-mode elicitation, with a \"Skip confirmation\" action, and the flow can now be explicitly completed or abandoned via server completion notifications.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}