Skip to main content

Saved Fleets

Name an armed set so you can recall it later: frozen snapshots, live rules that re-evaluate a predicate on every recall, the five built-in presets that use the same machinery, the Save fleet and Saved fleets dialogs, and Undo on delete.

Updated
Reviewed

What a Saved Fleet Is

A saved fleet is a named way of getting back to an armed set. Rebuilding the same selection by hand every morning is the thing this removes. Saved fleets are stored in project settings (fleetSavedScopes) as local, internal project data. They are scoped to this project on this installation and are not committed as shared team settings. They cover this window's own panes: agents armed from another host are not saved.

They come in two kinds, and the difference is whether the fleet remembers which panes or what kind of panes:

  • Snapshots store a frozen list of terminal IDs. They go stale as terminals come and go.
  • Live rules store a rule. They never go stale, because they are recomputed on every recall.

Saved fleets show up in three places:

  • The arming ribbon's … selection menu, under a Snapshots heading and a Live rules heading. Selecting a row recalls it.
  • The Saved fleets dialog, opened from Manage saved fleets… in that menu, where each fleet has Arm and Delete buttons.
  • The Fleet Picker, which offers each usable fleet as a one-click chip so you can recall one before anything is armed.

Each row shows the name and how many panes recalling it would arm right now. A snapshot that has lost some of its panes says so, as in 2 of 4. A live rule also says what it selects, as in Waiting · all worktrees.

Snapshots

A snapshot freezes the terminal IDs that were armed when you saved it. On recall, Daintree arms every stored ID that still exists and is still eligible, and drops the ones that are gone.

Terminals do not last forever, so snapshots decay. A snapshot whose stored IDs have all disappeared is stale: it moves into a separate sub-group below the usable ones, wears a trash glyph and the word Delete, and selecting it deletes it (with Undo) instead of recalling it. It stays visible rather than disappearing, because a stale fleet is something you want to notice and delete, not something that should quietly vanish.

The usable snapshots are ordered by frecency: recent use weighted against how often you use them, over a usage history capped at 20 entries. Ties break on last used, then created, then name. A freshly saved snapshot has no history yet and is seeded from its own creation so it does not sink below a fleet you recalled once a year ago. Stale snapshots are ordered by when you last used them.

Live Rules

A live rule stores a predicate instead of an ID list. The predicate has two fields:

FieldValuesMeans
scopecurrent, allThe active worktree at recall time, or every worktree in the project
stateFilterall, working, waiting, finishedWhich agent state to match (finished matches completed or exited agents), or every eligible terminal

On recall the predicate re-evaluates against the panels that exist right now and arms whatever matches. Live rules never auto-delete and never go stale, because the answer is recomputed every time. "Everything waiting for input, anywhere in this project" is a rule that stays true as the project changes; a snapshot of the same set stops being true within the hour. A rule that matches nothing at the moment stays listed but does nothing when selected.

The state filters match built-in agents, the same set the agent bulk actions address. all matches every fleet-eligible terminal, shells included.

The Built-In Presets

Five rules ship with Daintree and appear at the top of the selection menu under Select by state, each with a live count of how many panes it would arm:

PresetPredicate
All waiting, this worktreewaiting / current
All waiting, all worktreeswaiting / all
All working, this worktreeworking / current
All working, all worktreesworking / all
All in this worktreeall / current

They are the same predicate machinery a live rule uses. A live rule you save with the same predicate as one of them still appears under Live rules with your name on it, so it can be found, recalled by name and deleted like any other.

Tip
Hovering or keyboard-focusing a preset lights up the title bars of the panes it would arm, without arming anything. It is a dry run, so you can check a count of 7 is the 7 you meant before you commit to it.

Recalling a Saved Fleet

Recalling a fleet, from the menu, the Saved fleets dialog, or a Fleet Picker chip in Replace mode, replaces the armed set with the panes the fleet resolves to now, dropping any agents on other hosts. In the picker's Append mode the chips read Add a saved fleet and add only the panes not already armed. Each recall counts as a use for the frecency ordering.

Saving and Managing

Choose Save as fleet… at the bottom of the selection menu to open the Save fleet dialog:

  • Name: required. Enter saves.
  • Type: Snapshot or Live rule. The line under it says what you are about to save: The 3 panes armed now. Panes you close drop out of it. for a snapshot, or Whichever panes match when you recall it. 2 panes match now. for a rule.
  • For a live rule, Panes (Waiting, Working, Finished or All panes) and In (This worktree, meaning whichever is active, or All worktrees).

A snapshot needs something armed in this window: with nothing armed the footer reads Arm panes to save a snapshot and Save fleet stays disabled. A live rule does not depend on what is armed, because it describes a rule rather than a selection. The dialog stays open if the ribbon disappears underneath it, so a pane closing while you type a name does not take the name with it.

A live rule can be saved even when no panes match it yet.

Manage saved fleets… appears in the same menu once anything is saved, and the Fleet Picker has a Manage… button too. It opens the Saved fleets dialog: every fleet under Snapshots and Live rules, each with its count, an Arm button (disabled when it would arm nothing) and a Delete button.

Deleting is immediate and offers it back: a Fleet deleted notification carries an Undo button for five seconds, and Undo puts the fleet back where it was, with its usage history. In the selection menu, Delete or Backspace on a focused row deletes it the same way. Only the saved name and rule are deleted; the terminals it pointed to are untouched.