Stop, restart, pause, archive, or message many sessions at once (part 2)
How the Bulk session manager window is actually wired: the one list and its action bar, the selectors that decide which sessions each action may touch, the filter counts and not-loaded sessions read in the main process, which store call each button loops over, the single terminate-many request Stop sends, the delivery channel a broadcast reuses, and the contracts that lock the whole rule set.
On this page
What it is
This is part 2 of the Stop, restart, pause, archive, or message many sessions at once page. It carries the implementation behind those buttons, moved here because a single page is capped at 40,000 characters.
Where to find it
Nothing on this page is a surface — part 1 has the buttons and where they live. What follows is the code behind them, so it is for a reader with the repository open.
How it behaves
Each bulk action loops an existing single-session call rather than adding a parallel path, which is what makes the per-session busy-guard, the undo chokepoint and the routing for non-Claude engines apply here unchanged. Stop is the one exception and sends a single batched request. Below is how each of those is wired, the selectors that choose the rows, how the window assembles its list, filter counts and not-loaded sessions, and the contracts that lock the rules.
Related
- Stop, restart, pause, archive, or message many sessions at once — part 1 of this page, with the surfaces and the user-facing behaviour.
Last verified 2026-10-10