Done

Open space keeps cards for closed trigger agents, shown by raw id, with no console and no way to remove them

From lothlannDone 5 days agovia agent-mcp

A project trigger started several throwaway "Update Readme" agents within a minute or so of each other. After they finished and the trigger was deleted, agents_list_live for the project no longer lists them, but Open space still shows 5 cards labelled with raw ids (e.g. agent-1792229702049-99vxmo) and counts them as "5 agents online". Open console does nothing and the cards can't be closed. Mark as seen only moves them from To review to Available, where they stay. The project is offloaded to an SSH host.

AgentsRoom diagnostics

App version: 1.219.0
OS: linux 6.19.8-arch1-3-surface (x64)
Agent CLI: claude
App language: system

Expected behavior

A closed trigger agent's card leaves Open space, or at least can be dismissed.

Actual behavior

5 stale cards labelled by raw id stay in Available, counted as online; Open console does nothing and they cannot be closed.

Steps to reproduce

Project trigger starts several agents -> they finish and their consoles close (trigger deleted) -> open Open space.

Replies

Someone5 days ago

I seem to have reproduced this now.

Title: Agents disappear from the sidebar and their console can't be opened as soon as they wait for input

What happens When an agent stops to ask the user a question (its status becomes waiting_input), its tab disappears from the sidebar and its console can't be opened. The agent is still alive: agents_list_live lists it as waiting_input with a current heartbeat. Because its question can't be seen, the agent stays blocked.

Expected The agent stays in the sidebar, its console opens, and its question is shown so the user can answer it.

Steps

Start a backlog ticket in a project, which spawns a temporary frontend agent. Alternatively, start a "Feature squad" team run. Let the agent work until it asks the user a question. The agent disappears from the sidebar, and opening it with ui_open (surface agent) shows nothing. Evidence (17 Oct 2026, UTC)

15:49:49.70: two agents in two different projects switched to waiting_input within the same second, and both disappeared: grey-tide: temporary frontend agent agent-1792252142155-0bxrmu lba_generator: Feature squad Lead agent-1792252165772-7cyn8z. The run (run-1792252165756-ina85b) shows awaiting-finalization but holds only the Lead; no other squad members were ever visible. Restarting the grey-tide agent created agent-1792252529308-3obrg9, which worked normally while busy. At 16:03:48.70 it switched to waiting_input and disappeared the same way. Workaround Restarting the agent brings it back, but only until it next asks a question.

Impact: high. This keeps happening, and any agent that asks a question gets stuck because the question can't be answered.

The team5 days ago

Thanks for the report, this will be fixed in the next version. When a trigger started several agents in a row, the oldest ones were removed while their console was still connecting over SSH, so the console appeared afterwards with no agent behind it; those leftover consoles are now closed automatically and no longer show up in Open space (the cards you already have go away on the next restart). If the bug is still there after this update, please reopen the ticket with as many details as possible (a screenshot or a video helps a lot).

Sent automatically with your message

Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.

Browser: Linux