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

daemon: persist a retained-worktree store in state_dir #78

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

Once a kill can be refused and a force-kill retains, worktrees outlive their sessions on purpose. Something has to remember them, or a refusal just produces invisible garbage on disk — the failure mode the Spawn v2 reviews kept finding.

A state_dir-backed store of worktrees the daemon created that no longer have a session, holding for each one:

  • the worktree path and its base repository
  • the branch it holds
  • why it was retained (force-killed, exited-with-unsaved-work, and room for more)
  • when it entered the store

It must survive a daemon restart — this is the recovery path for everything else in the milestone, so a store that is lost on restart is worse than none. Write it the way sidecar.rs writes session records: atomic replace, tolerant of a missing or malformed file.

Entries leave the store when the worktree is reclaimed, and when the daemon notices the directory is gone (someone removed it by hand) — a stale entry must not accumulate.

Non-goals: this is not an ownership record and must not be used to decide whether a path may be adopted; #E1 settles that nothing is ever adopted.

Once a kill can be refused and a force-kill retains, worktrees outlive their sessions on purpose. Something has to remember them, or a refusal just produces invisible garbage on disk — the failure mode the Spawn v2 reviews kept finding. A `state_dir`-backed store of worktrees the daemon created that no longer have a session, holding for each one: - the worktree path and its base repository - the branch it holds - why it was retained (`force-killed`, `exited-with-unsaved-work`, and room for more) - when it entered the store It must survive a daemon restart — this is the recovery path for everything else in the milestone, so a store that is lost on restart is worse than none. Write it the way `sidecar.rs` writes session records: atomic replace, tolerant of a missing or malformed file. Entries leave the store when the worktree is reclaimed, and when the daemon notices the directory is gone (someone removed it by hand) — a stale entry must not accumulate. Non-goals: this is not an ownership record and must not be used to decide whether a path may be adopted; #E1 settles that nothing is ever adopted.
naps62-yolo added this to the Worktree lifecycle milestone 2026-08-24 09:38:40 +01:00
naps62-yolo added the area/daemondifficulty/mediumtype/feat labels 2026-08-24 09:38:40 +01:00
naps62-yolo added a new dependency 2026-08-24 09:39:00 +01:00
#80 daemon: GET /api/worktrees plus a reclaim endpoint
naps62-yolo added a new dependency 2026-08-24 09:39:00 +01:00
#81 kill --force ends the session and retains the worktree
naps62-yolo added a new dependency 2026-08-24 09:39:01 +01:00
#89 write the worktree lifecycle contract into the design doc
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 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.
Blocks
#80 daemon: GET /api/worktrees plus a reclaim endpoint
naps62/maestro
#81 kill --force ends the session and retains the worktree
naps62/maestro
#82 daemon: apply the same worktree rule when a session exits on its own
naps62/maestro
Reference: naps62/maestro#78