Release notes
One status per chat
The sidebar reads one status for each chat, written by the app itself. A worker cannot finish the parent chat, and a run that disappears marks the chat failed. A fleet task that was running when Vortex quit is marked interrupted and keeps its lane.
Fixed
- The sidebar, the Running filter, and the mind map share one status for a chat: running, waiting for your answer, plan ready, finished, failed, or idle. Opening the chat clears a finished, failed, or plan-ready mark. Stopping a run yourself returns the chat to idle. A plan that is ready for review stays marked until you open it.
- A sub-agent's finish leaves the parent chat running. A newer run stays running when the previous one ends. A run that disappears without a finish marks the chat failed, with reason interrupted.
- An approval or a question keeps the waiting dot until the last wait ends, including when a worker is the one asking. Cancel wakes the wait immediately.
- Starting a chat or resuming a run uses an id the app minted, and a second start with the same id is refused. Every event for that run carries the chat, workspace, and parent, so a late event lands on the row it belongs to.
- A fleet task that was running when Vortex quit is marked failed with reason interrupted and keeps its branch. Queued tasks start again. A task waits until the ones it depends on have landed or been kept. The stored task does not keep your API key.