naps62/maestro
Archived
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

surface a session's blocked work before the kill is attempted #83

New Issue
Closed
opened 2026-08-24 09:38:48 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-24 09:38:48 +01:00
Collaborator
Copy Link
Copy Source

With #79 in place a kill can be refused, and without any prior signal that refusal is a surprise every time — the operator presses kill, gets told no, and has to go find out why.

Session gains an indicator of blocked work, refreshed by the same watcher that maintains activity: whether the worktree currently holds anything that would block a kill, and a short summary of it. Clients render it on the session row and warn on the kill action, so "this will be refused" is visible before the attempt rather than after.

Recomputing it costs git probes per session per tick, so it needs the same treatment as the rest of the watcher: cheap checks, and no probe at all for a session with no worktree.

This issue is the one to cut if the milestone needs to be smaller — everything else works without it, just less kindly.

Depends on: #79

With #79 in place a kill can be refused, and without any prior signal that refusal is a surprise every time — the operator presses kill, gets told no, and has to go find out why. `Session` gains an indicator of blocked work, refreshed by the same watcher that maintains `activity`: whether the worktree currently holds anything that would block a kill, and a short summary of it. Clients render it on the session row and warn on the kill action, so "this will be refused" is visible before the attempt rather than after. Recomputing it costs git probes per session per tick, so it needs the same treatment as the rest of the watcher: cheap checks, and no probe at all for a session with no worktree. This issue is the one to cut if the milestone needs to be smaller — everything else works without it, just less kindly. Depends on: #79
naps62-yolo added this to the Worktree lifecycle milestone 2026-08-24 09:38:48 +01:00
naps62-yolo added the area/daemonarea/webarea/tuidifficulty/mediumtype/feat labels 2026-08-24 09:38:48 +01:00
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/android
area/cli
area/config
area/daemon
area/protocol
area/tui
area/web
code-review
difficulty/easy
difficulty/hard
difficulty/medium
epic
Tracks a multi-issue epic / parent work item
 tui
type/docs
type/feat
type/fix
type/refactor
type/test
No labels area/daemon area/tui area/web difficulty/medium type/feat
Milestone
No items
No Milestone Worktree lifecycle
Projects
Clear projects
No projects
Assignees
Clear assignees
hermes (Hermes (agent)) naps62-yolo (naps62-yolo (agent)) resende (Resende) naps62 (Miguel Palhas)
No Assignees
1 Participants
Due Date
No due date set.
Depends on
#79 daemon: refuse a kill when the session's worktree holds unsaved work
naps62/maestro
Reference: naps62/maestro#83