Repository navigation
(sessions): stop all sessions of a project folder #843
Description
Stopping is per row (public/stop-session-ui.js planSessionStop / confirmAndStopSession; session-state.md "The two lifecycle verbs"). Add a "Stop all" verb on a project folder header: run the existing planner over every row of the folder (nested worktrees included), one danger confirmation that lists the sessions and marks mid-turn ones, and the existing failure notice with Retry. Background jobs and remote hosts follow the existing refusal rules; do not port upstream's swallowed errors. Idea from upstream ee65652 confirmStopWork (credit Ali Basiri). Found by the #831 study.
Activity
devsuitup commentedon Oct 30, 2026
Decided by Jean-Baptiste in person on 2026-10-30 (row = one conversation, #564): when a conversation under the folder has background jobs, "Stop all" refuses by default and says why, and offers a way to force it; forcing also stops those jobs. His words: « tu peux bloquer (en disant pourquoi) mais permettre de forcer ».
(sessions): stop all conversations of a project folder (#843)
(sessions): stop all conversations of a project folder (#843)
(sessions): Stop all derives background from targets, shares host fai…
(sessions): Stop all names unchecked idle parts, offers force only fo…
(sessions): stop all conversations of a project folder (#843) (#927)