You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Stop button shows only while the Command's process is alive.
A confirm step says the issue will be labelled needs-triage, and offers "requeue instead", which is thirdshift stop --requeue.
The action calls the same Stop as thirdshift stop, with "from the Console" and the signed-in account's email as who asked. The Activity log reads <subject> stopped from the Console by <email>.
The page shows "still ending", with the stopping bar, until the outcome arrives, then shows the outcome and anything left on origin.
The page shows thirdshift stop <command> beside the button.
Acceptance criteria
Stop shows only for live Commands, and needs the confirm step and a CSRF token.
Stop and requeue label the issue as thirdshift stop and thirdshift stop --requeue do, against the fake GitHub.
The Activity log line names the Console and the account.
The page goes from "still ending" to the outcome through the push stream.
The Stop route is paired with stop in the parity test.
Tested over HTTP against a real Command with a waiting fake Harness, and with Playwright for the confirm step.
Activity
JacobStephens2 commentedon Oct 20, 2026
Closed by #869, merged into issue-776 by a thirdshift Merge run.