A session finished by another CLI run (official CLI, or one that has
exited) kept a background shell "running" forever: the sidebar spun, the
header said the session was active, and Stop failed with "CLI session is
not running".
The CLI records a task's end in several shapes depending on when the
notification was delivered, and history restore only read the user-turn
one:
- notifications drained mid-turn are queued_command attachments;
- notifications queued but never delivered survive only as a
queue-operation;
- TaskStop/KillShell leave no notification, only their own tool result.
Read all of them, and when no CLI process exists, converge a Stop of a
history-only task to stopped instead of failing.
程序员阿江(Relakkes)
b8871ca0e8