Observed: Session cards change color to reflect status (e.g. active → completed) for Claude Code sessions, but Cursor sessions don't get the same color update — the card stays in its initial state even after the work has completed.
Expected: Card color/status indicator updates on completion regardless of the agent kind running the session.
Suspected cause: The completion-detection path (whatever signals "session is done" — process exit, output marker, agent-specific RPC, etc.) is likely wired only for the Claude Code agent. Cursor sessions don't emit the same signal, so the status never transitions and the card color never updates.
Acceptance:
- A Cursor session that finishes its work transitions to the same "completed" visual state as a Claude Code session.
- The completion signal works whether the agent exited cleanly, was stopped, or marked itself done.
- No regression to Claude Code completion behavior.
Related: #424 (Cursor agent launches terminal but does nothing) — completion can't be observed if the agent never starts. Fix order: #424 first, then verify this.
🐦⬛ Created with Crow via Claude Code
Observed: Session cards change color to reflect status (e.g. active → completed) for Claude Code sessions, but Cursor sessions don't get the same color update — the card stays in its initial state even after the work has completed.
Expected: Card color/status indicator updates on completion regardless of the agent kind running the session.
Suspected cause: The completion-detection path (whatever signals "session is done" — process exit, output marker, agent-specific RPC, etc.) is likely wired only for the Claude Code agent. Cursor sessions don't emit the same signal, so the status never transitions and the card color never updates.
Acceptance:
Related: #424 (Cursor agent launches terminal but does nothing) — completion can't be observed if the agent never starts. Fix order: #424 first, then verify this.
🐦⬛ Created with Crow via Claude Code