Release notes
Plan mode can call MCP, and a queued message that actually sends
Plan mode can call the MCP tools you already connected, so a plan can look something up before you Build. A queued follow-up sends when the run finishes, and it does not fire after a failure or a plan that is still waiting on you. The SSH chip is the host again: right-click it to disconnect.
Fixed
- Plan mode told the model it could not call MCP tools, and the executor refused them. A plan could not look up an issue, a doc, or a database until Build.
- A queued message could sit forever after a successful run, because the trace still said
runningat the instant the run ended. A message queued while the agent was already idle had the same problem. - A queued follow-up could also fire after a failed, cancelled, or Plan-ready run, and bury that outcome.
- Starting a new chat left the previous run's context ring on the composer.
- The live checklist pinned to the top of the transcript even when you had not scrolled past it, so it floated over the turn. It now stays in place until its row would leave the top, then holds there.
- The SSH chip grew an Open button and an agent count. Disconnect is a right-click on the chip. The chip still stays visible when you switch to a local workspace.
New
- Registered MCP tools are callable in Plan mode, the same set Agent mode has, including tools that are not marked read-only. Adding or configuring a server still waits until Build. An unknown
mcp_*name is still refused. Ask mode still calls nothing. Docs: MCP integrations.