MCP 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.
MCP elicitation handling reworked into a stateful class with 'waiting' UI and URL-mode flows
MCP elicitation gets a distinct waiting dialog with a Skip confirmation action and can be completed by the server.
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.257,
What probably matters to youSection of the release