A /stop command can end a background session while keeping its transcript and worktree.
/stop exists behind an availability check not decided in the command definition.
What's wrong with this entry?
A new /stop command ends a background session immediately while keeping its transcript and worktree. It is behind an availability check, and what turns that check on is not decided in the command definition itself.
Stop this background session; transcript and worktree are kept
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
claude rmtells you which session is holding a directoryBoth mention stop
-
v2.1.238
stop_taskcontrol request stops a single taskBoth mention stop
-
v2.1.223
Background job state and roster writes can route through the v5 storage backend
Both mention background