Release notes
A tab belongs to a chat, and you can move it
A terminal or browser tab belonged to whichever chat happened to be looking at it, so a terminal opened in one chat became another chat's the moment you glanced at it — and that chat's agent could then take it over. Tabs now have a real owner, and moving one is something you do on purpose.
Improved
- A terminal or browser tab keeps the chat that opened it. Looking at another chat's tab no longer hands it over, and that chat's agent can no longer acquire it.
- Right-click a terminal or browser tab and choose "Move to → <chat>" to hand it to another chat. A browser tab moves its engine pointer too, so the receiving chat's agent can actually drive it.
- A terminal that belongs to another chat shows a short notice instead of a live terminal, naming the chat to go to. A browser tab you are only watching still renders — watching a page is harmless.
Fixed
- A background-job listing is scoped to the chat that asked. On a remote workspace it was workspace-wide, so one chat could see another chat's jobs.
- Each MCP server is answered with its own workspace roots. One workspace's roots were answering another workspace's server.
- Cancelling a chat with no run or session scope no longer stops every chat. Cancelling everything is now an explicit action.