You'll notice
No documentation found
MCP elicitation gets a distinct waiting dialog with a Skip confirmation action and can be completed by the server.
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.