From lothlannDone 3 days agovia agent-mcp
When a team run ("Feature squad" template: Lead pm node) is running, the Lead's temporary agent console never appears in the UI. There is no tab or terminal to open. Over MCP, agents_list_live reported the Lead as status "waiting_input" with teamRunStatus "awaiting-finalization", but no question card, no Lead tab and no "Finish run" button were visible. The user had no way to see or answer it, so from their side the run looked stuck. In the end it had to be cancelled over MCP (team_cancel_run). This has happened repeatedly.
The Lead console is visible as a tab, and the run box shows "Finish run" once End is reached.
No Lead tab or terminal, no Finish button; the run sits until it is cancelled or finalized via MCP.
Reproduced in a second remote SSH project (lba_generator). Feature squad run-1792251565002-mhafnc is running; agents_list_live lists Lead, backend and frontend with live tmux consoles on the remote host, but no tabs appear. Calling ui_open({ surface: "agent", agent: "<Lead id>" }) lands on a blank "select project" page instead of the console. Both affected projects are remote SSH projects.
This will be fixed in the next version. Cause: for projects opened directly on an SSH server, AgentsRoom saved the list of a team run's agents on your computer but read it back from the server, where it did not exist. Each time you came back to the project, or restarted the app, the Lead and its teammates disappeared from the sidebar while their consoles kept running on the server, and after a restart the run box with its Finish button was not shown at all. Run notifications and the "open all consoles" button also pointed at the wrong project, and ui_open on an agent now opens the project that agent belongs to. If the problem is still there after updating, please reopen this ticket with as many details as possible (a screenshot or a short video helps a lot).
Thanks: the bug is fixed and the fix ships in the next release. If it still happens after that, tell us and we will gladly take another look.
Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.