Worktree Cards
The anatomy of a worktree card in the sidebar: the lifecycle status mark, row status signals, alarm salience, the quick state filter, collapsed states, filters, and per-card recovery.
Worktree Cards
Each worktree shows as a card in the sidebar. This page covers how a card is built: the lifecycle status mark, row status signals, alarm salience, the quick state filter, collapsed states, filters, and per-card recovery. For creating, switching and deleting worktrees see Worktrees; for what a deleted worktree's card does, see Deleted worktrees.
A card carries:
- Title row: a branch-type icon (a sparkle for feature, a bug for bugfix, a wrench for chore and so on) and the branch name with its type prefix stripped; the tooltip gives the full name. When an issue is linked, or the worktree was created from a pull request, its title becomes the headline and the branch moves to the line below. The same row holds the small status signals described below, and the card's toolbar: a collapse chevron (Collapse card / Expand card) and the ⋯ menu.
- Secondary row: the branch (under a headline), the pull request badge with its CI state, the upstream sync line, and a View agent plan file link when an agent has written one.
- Details: a disclosure whose summary line names the most useful fact about the worktree right now (Conflicts need review, the changed-file count and diff stat, a running lifecycle step, the last commit subject, or No recent activity), with the activity chip at its end. Opened, it shows any errors, the agent's note or the last commit, the Changed files list with Open changes, the path row, and when the worktree was last active.
- Path row: the worktree's folder, written relative to your home directory. Clicking it opens the built-in File Browser as a grid panel rooted there, selecting the card first if it isn't already active; Copy full path beside it copies the absolute path.
- Sessions: every panel in this worktree with its kind and state, under an Active sessions (N) disclosure. Clicking a session row arms it for fleet actions and shows its arm order; drag across several rows to arm them together, drag a row by its grip to move the terminal, and right-click a row for that session's own menu. A card with no sessions offers Start a session.
The main worktree's card is built differently; see Primary worktree card.
Local git state on cards (commits, branch switches, file changes) comes from file-system event watching rather than polling, so an agent writing files in a background worktree shows up live instead of staying invisible until it commits. A polling fallback covers the case where the OS-level watcher isn't available, which on Linux usually means the inotify watch limit is exhausted.
On Linux, sidebar updates that lag badly usually mean the inotify watch limit is exhausted. Daintree raises a File watching degraded notice with a Copy fix command action when it detects this; the log (Settings > Troubleshooting > Application logs > Open log file) carries the watcher warning too, then raise the limit with sudo sysctl -w fs.inotify.max_user_watches=524288. To persist it, add fs.inotify.max_user_watches=524288 to /etc/sysctl.d/99-inotify.conf and run sudo sysctl --system.
Double-click anywhere on the card that isn't a control to collapse it, or use the collapse chevron or Organize > Collapse card. A collapsed card takes less vertical space while still showing status, and stays collapsed across restarts. Double-click again to expand.
Changed files on a card
Open a card's Details to inspect local edits without leaving the sidebar. Files are grouped under folder headers, with root-level files grouped as (root); each row shows the filename, status and change counts. Selecting a row opens its diff. The row menu offers the shared file actions, including Insert file reference, the Copy submenu and plugin Extensions. For a complete staging workflow, open Review Hub.
Lifecycle Status Mark
A small mark at a card's top-left names the next action that worktree needs. It only appears when there is something to act on. The waiting mark can show at once; cleanup and complete wait until git data has resolved.
Since v0.34 the mark is a segmented vertical tick in the grip gutter rather than a corner wedge: a 4px bar in a fixed 16px slot, cut into a different number of pieces per state. On a sidebar card it sits on the leading edge, 4px down from the top. A collapsed card carries a smaller 6×6 version in the same place, cut into the same 1, 2 or 3 pieces, so it stays legible under forced colors.
| Mark | Tooltip | Meaning |
|---|---|---|
| One unbroken amber bar | Agent waiting for input | An agent in this worktree is blocked on you. |
| Two purple segments | Ready for cleanup | The PR is merged. The worktree has served its purpose and can be deleted. |
| Three blue segments | Complete: in review | A linked issue, an open PR, no uncommitted changes, and no active agent. It is ready for review. |
The cut count, not the color, is what separates cleanup from complete. Under Windows High Contrast every state repaints to one system color, so geometry is the only channel left; and the previous three corner wedges differed only in how much of a 12×12 box they filled, which does not read at that size. Length would have been the obvious knob and is the wrong one: a short bar is only short beside a longer one, and a card read on its own has no neighbor to compare with. A count of segments is absolute. The ink descends with urgency too, so the solid bar is the state that is blocking on you and the most broken-up one is the state that wants nothing.
Blue, not green, for complete. Across the app green means working and blue means in review or finished; a green "done" mark would compete with the one signal that means work is happening right now.
When several conditions apply the mark shows the highest-priority state: cleanup, then complete, then waiting. A merged PR outranks the rest because deleting the worktree is the most definitive thing left to do, but neither cleanup nor complete shows while an agent in the worktree is still working.
Only cleanup is gated to secondary worktrees. Waiting and complete render on the main card too: the main worktree can have an agent waiting on it like any other.
The cleanup mark also adds a Delete worktree trash button to the card's toolbar, next to the three-dot menu, so Delete is one click rather than a menu dive. The icon is neutral at rest and turns red on hover or focus. Once a worktree reaches complete, open the Review Hub from its menu to stage, review and push.
Row Status Signals
A card's signals sit in three places: small marks at the end of the title row, the secondary row under the title, and the activity chip at the end of the Details line. Each is independent and degrades on its own, so a remote that can't be reached never hides a fresh activity chip beside it.
| Signal | Where | What it shows |
|---|---|---|
| Git state indicator | Title row | An inline label for an in-progress git operation: rebasing, merging, cherry-picking, reverting or detached, amber; conflicted, red. It is a passive label, not a control. |
| Pin | Title row | A pin icon on a worktree you pinned to the top from the card menu. |
| External | Title row | A folder-out icon on a worktree git reports from outside the project directory, with the full path in its tooltip. See Worktrees outside the project. |
| Muted | Title row | A bell-off icon when notifications are muted for this project. |
| Environment | Title row | The resource-environment popover, when the worktree runs on non-local compute or has a resource status to show. See Remote Compute. |
| Dev server | Title row | A globe and the port while a dev server is running for this worktree, a spinner while it starts, a red mark on error. See Dev Preview. |
| Pull request badge | Secondary row | The linked pull request (or GitLab merge request) as #N, colored by state, with its CI result. See PR and issue badges. |
| Upstream sync line | Secondary row | ↑N / ↓N against the upstream branch, then the base branch: ≡ develop when the branch is level with it, Δ develop ↑N ↓N when it has drifted (shown once when base and upstream are the same branch). local means no upstream is configured. An amber key means fetching failed to authenticate; a cloud-off icon means the remote couldn't be reached. The tooltip spells it out, ending with when the remote was last fetched. |
| Activity chip | Details line | An activity light and how long ago the worktree last changed, falling back to the last commit. The light holds the working color for five minutes, then fades to a hollow ring by ten. Hover the commit for its subject and body, author, co-authors, exact time and SHA. |
On an authentication failure, when Daintree knows which forge the remote belongs to, the sync line becomes a button ending in Reconnect: it retries the fetch and opens Settings > Code forge so you can fix the token.
The author avatar is deliberately left off the row: a column of identical "you" avatars adds noise and no information. The commit hover card surfaces the author when you need it.
Where mid-rebase recovery lives
The git state indicator names a rebase, merge, cherry-pick, or revert in progress. Open the Review Hub to inspect and resolve conflicted files. The card menu also offers Git > Continue rebase and Git > Abort rebase… (or merge, cherry-pick or revert) for the current operation. Continue routes unresolved conflicts to the review surface; Abort opens a confirmation describing what is restored.
Status still resolving, and the review button
Before git has answered for a worktree, its Details line reads Checking status… rather than "No recent activity", an all-clear the data can't yet support.
While Details is closed, an icon button at the end of that line opens the Review Hub, and its tooltip tracks what the worktree actually needs:
- Review & commit when the tree has changes.
- Review & push when the tree is clean but commits are unpushed. The next step is still in the Review Hub, so the button stays; only the label shifts.
- Nothing, when the tree is clean and everything is pushed.
Alarm Salience and the Collapsed Pill
A row can carry a failing CI run, an upstream auth failure, a behind-upstream count and more at once. Salience tiers keep it from becoming a wall of badges: when the upstream line's alarm outranks the pull request's, the upstream line moves above it, and a collapsed card shows only the single highest tier.
| Tier | Signal | Tone |
|---|---|---|
| 3 (highest) | CI failed | Red |
| 2 | Auth failed (couldn't fetch from upstream) | Amber |
| 1 | Behind upstream, or behind the base branch | Amber |
| 0 | No alarm | None |
Only a failure CI state climbs above tier 0. Pending and neutral states stay quiet, so a long push session doesn't flicker the row between tiers as checks queue and finish. Detached HEAD is deliberately not an alarm either: the git state indicator already labels it in the title row, and a colored pill would double-label the same fact.
What makes CI "failed"
On GitHub, the CI signal is derived from the PR's required checks, not the raw status rollup, the same derivation the PR dropdown in Code Forge uses, so the two never disagree. On GitLab it comes from the merge request's head pipeline. The badge's hover card reads like CI failing · 2 of 5 failed or CI pending · 1 of 4 running.
The derivation refuses to invent a green. If the checks page is truncated, if a context arrives in a shape it can't classify, or if no required checks are configured at all, it falls back to the raw rollup state and shows no summary rather than reporting a pass over checks it never saw. A stale required run counts as failing, because it has not resolved to a passing state.
Collapsed, the signals reduce to a single icon in the header for the highest active tier: a red circled X for CI failed, an amber key for auth failed, an amber down arrow for behind. Its tooltip carries the label and the detail, such as 2 of 5 checks failing or what to do about it; focusing the card from the keyboard shows the tooltip too. Expand the card to get the individual signals back.
Quick State Filter
The filter bar above the worktree list filters by agent state. Four segments: All, Working, Attention, Finished. "All" keeps its text label; in the sidebar the other three are an icon plus a count, with the name in a tooltip, which is what keeps the bar legible in a narrow sidebar. The Worktrees Overview shows the same bar with its labels written out.
- Working: a green spinner. When the count is above zero it turns slowly, gated by
prefers-reduced-motion. It is a glance signal, not a change in polling cadence. - Attention: an amber hollow circle, for worktrees with an agent waiting on you.
- Finished: a blue check circle.
The bar is a radio group: arrow keys, Home and End move between segments and select as they go. The active segment carries a subtle inset bottom rule in neutral text color, not the accent. Accent stays scarce. A segment whose count is zero dims its glyph. Clicking the active segment resets to All. Each segment's accessible name carries noun and count together ("Working, 3 worktrees"), so dropping the visible text label costs screen-reader users nothing.
"Finished" is not "Completed." Finished is a worktree-level label covering complete and cleanup worktrees. Completed is a session-level state, one agent that finished a turn, and appears as an option in the filter popover's Sessions section; the collapsed card's indicators call it done. The filter bar counts worktrees, the collapsed card indicators count sessions.
In the sidebar, counts ignore your search and other filters. Each segment counts every non-main worktree in that state, whatever the search box and the filter popover are hiding, so a count never changes because of something you typed. The line under the search field says so while a search is active: N of M worktrees · state tabs ignore search. The overview's copy of the bar counts within its search and filters instead.
The trailing arm button
A small lightning-bolt button sits at the trailing edge of the bar, past a divider. One click arms every unarmed agent in the currently filtered set, ready for an Accept, Interrupt or broadcast; the Fleet Arming Ribbon appears once two or more terminals are armed.
It addresses agents only. Plain shells are excluded (they stay armable individually, from a card's session rows, and through Select terminals to arm in the sidebar header), which is a different unit from the state filters beside it: those are derived from agent state but count matching worktrees, while the arm button counts the agents it would arm. The tooltip and accessible name track the state:
| State | Label |
|---|---|
| No filter, nothing armed | Arm all N agents |
| Filter active, nothing armed | Arm N matching agents |
| Some already armed | Arm N more agents / Arm N more matching agents |
| Nothing eligible | No agents to arm / No agents match the filter |
| Everything already armed | All agents are armed / All matching agents are armed |
The button never disappears (it dims and disables), so its place in the bar stays predictable.
PR and Issue Badges
The pull request badge shows the linked pull request, or GitLab merge request, as #N, colored by its state, with its CI result beside it. On a card it shows open and merged states; a closed PR drops the badge. The merge-conflict icon introduced for GitHub and GitLab appears in the Code Forge lists, not on the card. Clicking a badge opens the PR or issue only on the active card; on any other card, select the card first.
PR and issue badges come from cached provider responses that refresh on a short poll, so their age alone is not something to act on and the badge does not show it. It changes only when the data really can't be trusted: a cloud-off glyph appears when the forge has rate-limited Daintree (on both badges) or when PR detection is paused after repeated failures (on the PR badge). The last known value stays on screen, and the hover card says why: Rate limited, retrying at {time}, or PR detection paused, so details may be out of date.
With no forge token configured, the badge's text turns neutral, and its hover card reads Add a forge access token to see pull request details; clicking it opens Settings > Code forge.
Collapsed Cards
Collapsing a card hides the secondary row and the body (Details and the session list). The title row stays, with the small status tick, the git state label, the alarm icon, the pin, external, muted, environment and dev-server marks and the toolbar, and gains a row of compact session indicators. Each indicator is an icon plus a count.
| State | Icon | Tone | Animated |
|---|---|---|---|
| Working | Spinner circle | Green | Yes |
| Directing | Interacting circle | Blue | No |
| Waiting | Hollow circle | Amber | No |
| Done | Check circle | Slate | No |
| Exited | Exited circle | Dim | No |
Hovering the group shows the full summary, such as "3 sessions: 2 working, 1 waiting". Idle sessions are never shown: when every session is idle, or there are none, the collapsed card shows no session indicators. For what each session state means, see Agent States.
Focused Sub-Line
A collapsed card reveals a thin line of context below the branch name while it is the selected worktree or has keyboard focus. Hovering does not open it, and the main worktree's card never shows it. It expands with a short height transition and a brief fade, and collapses again when the card loses selection and focus. The animation respects prefers-reduced-motion.
Up to three dot-separated segments, in order: the changed file count when the tree is dirty ("3 files"), the last activity time as a live relative timestamp, and a status label: the running or failed lifecycle step (Running setup, Setup failed) or the resource status. It gives a collapsed card enough for a triage call without expanding it.
Primary Worktree Card
The main worktree's card uses a two-row header that doubles as a project-level overview.
The top row shows the project name rather than the branch, a sprout icon, a collapse button and the actions menu. The second row, visible when expanded, shows the branch label, upstream sync, and an aggregate summary of the secondary worktrees.
- Upstream sync:
↑Nin green for commits ahead,↓Nin amber for commits behind, with the full sentence on hover. - Aggregate summary: a folder icon with the total worktree count, then colored counts for working and waiting. The finished count only appears once nothing is working or waiting, so finished work never drowns out work that still needs you.
Expanded, the body adds a health row with CI status, open PR count and open issue count, which needs a configured forge token.
The Worktree Sidebar
The sidebar is where you navigate worktrees. It is virtualized and keyboard-first: only the rows in view plus a small overscan buffer render to the DOM, so scroll performance holds on projects with hundreds of worktrees.
The main worktree renders outside the virtual surface and stays at the top. Below it, pinned worktrees, then everything else by the active sort, then external worktrees. Deleted-worktree rows sit at the position they were deleted from.
When rows sit fully offscreen, small pills appear at the top and bottom edges with a chevron and the count of hidden worktrees, ringed in amber when any of them needs attention. The tooltip says what is there and what a click will do (12 more worktrees below, 2 need attention. Click to show the nearest): a click jumps to the nearest worktree that needs you, or otherwise moves one page.
The sidebar header holds four buttons. Create new worktree is always shown; Open worktrees overview, Select terminals to arm and Refresh sidebar appear when you hover or focus the header. Right-clicking empty sidebar space offers New worktree… and Refresh sidebar.
Filter changes and result counts are announced. See Search and Filters for what the controls do. When a quick state filter leaves nothing to show, the list says so (for example No working worktrees) and offers Show all worktrees and Open overview.
Refreshing
The refresh button in the sidebar header is a true full refresh, not a nudge. It discards cached forge data and re-resolves worktree state, issue and PR titles, and CI badges, re-reading from disk and from the provider. That costs provider round trips against your rate limit, so it is an escape hatch for when something changed outside the app, not a habit to build on top of routine polling.
The pass is watchdogged and each phase is isolated: a slow PR fetch can't sink the worktree refresh, topology re-discovery failing doesn't stop the status pass, and the button always resolves. If the host doesn't respond at all, a Refresh failed toast says so rather than the button quietly doing nothing.
Keyboard navigation
The sidebar has two focus modes. List mode is the default, with focus on a row. Toolbar mode moves focus into the focused row's inline action buttons. The grid holds a single tab stop and tracks the active row through aria-activedescendant.
List mode
| Key | Action |
|---|---|
| ↑ / ↓ (or j / k) | Move row focus |
| PgUp / PgDn | Move one viewport page |
| Home / End | First / last worktree |
| Enter or → | Enter the focused row's toolbar |
| Space | Select / switch to the focused worktree |
| Alt+↑ / Alt+↓ | Reorder the row in the custom sort |
Toolbar mode
| Key | Action |
|---|---|
| ← / → | Move between toolbar buttons (wraps) |
| Home / End | First / last toolbar button |
| Ctrl+Home / Ctrl+End | Return to list mode, jump to first / last row |
| ↑ / ↓ | Return to list mode and move row focus by one |
| Esc | Return to list mode, keeping the active row |
Leaving the window drops back to list mode, so re-entering the app never lands inside a toolbar. The grid has no bindings of its own on Cmd; Ctrl matters only for Ctrl+Home and Ctrl+End.
Reordering
Alt+↑ and Alt+↓ move the focused worktree in the list, as do dragging a card by its grip and Organize > Move up / Move down in the card menu. Reordering under any other sort switches Sort by to Custom order, which is per-project and survives restarts. Pinned worktrees have no grip and no move items: their place is set by pinning.
Reordering is off while the list is grouped by type or a search query is active, and the line under the search field says why (Drag to reorder is off while searching). With either on, the Alt+Arrow keys and drag-to-reorder do nothing and the move items are hidden. The order itself is kept; you just cannot edit it until you clear the search or the grouping.
Focus follows the card as it moves, and the screen-reader announcement reports the new position once the key release settles, so holding the key does not fire an announcement per step.
With the mouse, drag a card and a thin directional line shows where it will land. Escape mid-drag cancels, and the card snaps back with an assertive "drag cancelled" announcement.
Placeholder cards during creation
While a worktree from the New Worktree dialog is being created, a compact row for it sits directly under the main worktree's card: the branch name and Creating…, which becomes Still creating… if Git takes a while, and is announced to screen readers. When the checkout exists the row gives way to the real card. A failure turns the row into Couldn't create {branch} with the error message, and Retry and Dismiss buttons. Retry reopens the dialog with the branch, recipe, agent and prompt filled back in. See Create a Worktree.
Reconnecting and load errors
When the renderer loses contact with the worktree host (rare, and usually after a sleep/wake cycle or a host crash) the sidebar header shows a spinner and Reconnecting…. Past ten seconds it turns to a warning tone, and its tooltip says when the list was last updated, so you can tell fresh data from a stale snapshot. A failed initial load shows a top banner titled Couldn't load worktrees with the error and a Retry button.
Search and Filters
The search field at the top of the sidebar (Search…) filters as you type. It matches the worktree's name and branch, its linked issue's title and its pull request's title; a bare number, with or without #, matches a linked issue or PR number. Escape clears the query, and pressing it again on an empty field leaves it; ↓ moves into the list. The X (Clear search) clears the query only, leaving filters alone. The search field and the quick state filter only appear once the project has a worktree besides main.
Under the field, a line reports what you are looking at while anything narrows the list: 4 of 12 worktrees, the active filters by name (Status: Dirty · Branch type: Feature), and a Clear all button when two or more filter axes are active. A single-axis search or quick state filter has its own clear control.
The filter button beside the field (Filter and sort worktrees) opens the advanced popover. While filters are active it carries a neutral fill and the count of active filters.
| Category | Options |
|---|---|
| Has an agent | A single toggle pinned above the other sections, with its own count: keeps only worktrees with at least one agent session, in any state, including idle agents and ones that haven't reported a state yet. Plain shells don't count. |
| Sort by | Date created, Recently updated, Alphabetical, Custom order; plus a Group by type checkbox that groups worktrees by branch-type prefix, with an "Outside the project" section when external worktrees exist |
| Status | Active, Dirty, Stale, Idle |
| Branch type | Feature, Bugfix, Refactor, Chore, Docs, Test, Release, CI, Deps, Perf, Style, WIP, Main, Detached, Other |
| Issues & PRs | Has issue, Has PR, PR open, PR merged, PR closed |
| Sessions | Has terminals, Working, Waiting, Completed, Exited |
| Activity | 15m, 1h, 24h, 7d |
| Dev server | Has server, Running, Starting, Error |
Has an agent is its own filter rather than a Sessions option, because Sessions options combine with OR: Has an agent plus Waiting would otherwise widen back to every worktree with an agent. Like the other sections it combines with the rest by AND.
Sort by starts collapsed, with the current order in its header. Status and Branch type start open; the other sections open only when one of their options is active. Each section has its own Clear, and a long Branch type list folds behind N more. The "Issues & PRs" section is provider-neutral: it filters on whatever forge the project is connected to, not on GitHub specifically. "Custom order" is hidden while "Group by type" is on. A Clear all filters button appears at the bottom of the popover whenever anything is active.
Chip counts inside each category use disjunctive logic: the number you see is the number you get if you click. A chip with nothing to match is dimmed but stays clickable.
Activity recency is unified across worktrees, so "Recently updated" and the activity windows mean the same thing everywhere rather than each worktree tracking its own notion of recent.
Visual Hierarchy
With many worktrees open, Daintree dims idle and stale cards so active work stays prominent. A card is muted when it is idle or stale, has no waiting agent, and isn't the selected or focused worktree or a target for a panel being dragged. Hovering doesn't lift the muting. Muted cards use a dimmer text color for the branch name and labels.
One exception matters: a card with a waiting agent is never muted, however idle the worktree otherwise looks. Waiting is the state that needs you.
Lifecycle Failure Recovery
A setup lifecycle script can fail on a missing dependency, a wrong path or a network blip, and other lifecycle commands can fail or time out the same way. The failure surfaces on the card, under the Details line, rather than in a toast you can miss after a context switch, and the worktree holds that state until you act on it.
The footer reads Setup didn't finish. Re-run when you're ready. with two controls:
- Retry setup: re-runs the failed phase. The button shows a spinner while it runs, then the footer clears on success. The retry is pinned to the card's own worktree, not whichever one is focused, so you can trigger it from anywhere.
- Show details: expands the captured error and output in a scrollable monospaced block. Daintree keeps the last 8192 bytes.
The footer is shown while the card is expanded and its Details are closed; the open Details panel lists the same error. The state lasts until you retry or the app restarts.
Repository commands that need approval
Lifecycle commands that come from the repository, rather than from your own user-level config, don't run until you approve them. A card whose worktree would run unapproved commands says so in the same place: Repository commands need your approval to run, or Setup is waiting for you to approve its commands when setup stopped for it. Review commands opens Approve repository commands?, which lists every command by file; Approve commands (or Approve and run setup) approves those exact lines, and any later change to them asks again. If the commands were approved elsewhere after setup was skipped, the card reads Setup was skipped, and its commands are approved now and offers Run setup. See Setup and submodules.
Restarting a Session
Restart session, on a panel's three-dot menu, applies at once when the terminal is idle. When an agent in it is still working, it asks first: Restart "{title}"?, noting that the agent is working and will be interrupted, with a Restart terminal button. The earlier two-click countdown is gone.
The Card Menu
The card's ⋯ button and its right-click menu render the same items, so a command can never be wired into one and missed in the other. As of v0.34 that menu is no longer one flat list of around 25 commands: it is eleven named submenus and a single destructive row, in a fixed order, split into four bands by a separator.
| Group | What it holds |
|---|---|
| Launch | Your pinned agents under an Agents heading, then Terminal, Browser and Dev preview, then More agents and panels…, which opens the panel palette. An agent that isn't installed stays on the list, disabled and marked Not installed, rather than disappearing or quietly launching a plain terminal instead. |
| Open | Browse files, Open in editor, and Show in Finder / Show in Explorer / Show in file manager (on a window connected to a remote host, Copy host path instead). |
| Review | Review worktree (the Review Hub), View uncommitted changes with its changed-file count, and Compare with another worktree…. |
| Git | Pull and rebase, Push, Fetch, Fetch and prune, then Rebase onto {base}… or Merge {base} in…. Each previews the commits it will actually move before it runs, and a row that can't run says why beside it instead of disappearing: No upstream, Nothing to push, No remote, No base branch, No branch checked out, Checking status…, Commit or stash first, Up to date. The rebase row shows how far behind the base the branch is. During a repository operation, Continue rebase and Abort rebase… (or merge, cherry-pick, revert) replace the base-integration commands. After a push is rejected, the Push failed notice offers Force push…, and the menu adds Force push with lease…. See Integrating the base branch. |
| Sessions | Everything that acts on every session in the worktree at once. Three labeled sections and a destructive tail; see below. |
| Recipes | Each applicable recipe under a Run heading, then Save current layout as recipe…. Saving needs a live session to snapshot, and the whole group is absent when there is neither a recipe nor a layout to save. |
| Runtime | Two labeled sections. Dev server: Start when a stopped server can be restored, Restart and Stop while one is live. Environment: Switch environment, Check status, Connect, Provision, Resume or Pause, and Tear down environment… last. While the worktree is on local compute the section is only the switcher: the six remote commands aren't temporarily unavailable, they don't apply. See Dev Preview and Remote Compute. |
| Linked work | View plan, Open issue #N and Open PR #N, then, below a rule, Attach issue… (or Change linked issue…) and Unlink issue #N. |
| Copy | Full context and Modified files only, then Path and Branch name. See below. |
| Organize | Pin to top / Unpin, Collapse card / Expand card, then Move up and Move down. A move that would run off the end of the list is disabled rather than hidden; the move items are absent on a pinned worktree and while the list is searched or grouped. |
| Extensions | Everything plugins contribute to a worktree. See below. |
| Delete worktree… | The one item that is a row rather than a submenu, alone in the last band. Withheld on the main worktree. |
A group with nothing in it is dropped, not shown empty or dimmed: a worktree with no dev server and no configured environment has no Runtime, one with neither a recipe nor a live layout worth saving has no Recipes, and one no plugin contributes to has no Extensions. Linked work is the exception that looks like one. It survives a worktree with no plan, issue or PR, because Attach issue… is still something to offer: the group is dropped only when there is nothing to open and nothing to attach. So a fresh secondary worktree opens on Launch, Open, Review, Git, Sessions, Linked work, Copy, Organize and Delete alone. The separators are computed after that decision rather than owned by each optional group, so the menu can never open on a leading rule, end on a trailing one, or show two in a row.
The order ends on the destructive row deliberately. Destruction ends a menu, so nothing renders past it.
A workspace with no repository uses the same menu on its single row, cut down to what acts on a plain folder: Launch, Open, Recipes, and Copy with Full context and Path. See Worktrees need a repository.
Plugin items under Extensions
Plugin contributions used to trail the root menu after Delete worktree…. Nesting them under Extensions keeps the root the same shape however many plugins are installed, and makes it impossible for a third party to render past deletion.
A single contributing plugin gets no group heading: the submenu's own title is enough. Once two or more contribute, each plugin's items sit under its display name (falling back to its plugin id), separated by a rule, so you can tell whose command you are about to run.
Filtering happens before the menu sees the list. An item whose when clause doesn't hold is never passed in, and an empty list produces no Extensions trigger at all.
Copy path and Copy branch name
Copy gathers every clipboard route in one place. Full context and Modified files only hand the worktree to CopyTree; below a rule, Path copies the worktree's absolute path and Branch name, new in v0.34, copies the branch it is checked out on.
A successful copy confirms with a brief Copied toast; a failed one says Couldn't copy path (or branch) and offers Retry.
Branch name sits directly under Path so the two copy targets read together. It is hidden, not disabled, when there is no branch name to give: a worktree on a detached HEAD has none, even while the card still shows the branch it was on before detaching, and copying that string would hand you a branch you are not on.
Sessions Submenu
The menu's Sessions submenu fans one action across every session in the worktree. Most items carry their eligible count and disable at zero, and the count is part of the accessible name ("Dock all panels, 2") rather than only a muted number at the end of the row.
| Section | Item | What it does |
|---|---|---|
| Layout | Dock all panels | Move every grid-resident session into the dock. |
| Layout | Move all to grid | Restore every docked session to the grid. |
| Fleet selection | Select all terminals | Arm every live terminal here, plain shells included. The Fleet Arming Ribbon appears once two or more are armed. |
| Fleet selection | Select waiting agents | Arm only the sessions currently waiting. |
| Fleet selection | Select working agents | Arm only the sessions currently working. |
| Maintenance | Redraw all terminals | Force-reload the terminal renderer for every session here, useful after a GPU driver hiccup or a font-loading glitch. |
| Below the rule | Clear session history… | Drop this worktree's resumable session journal. Bookmarked sessions and sessions still open are kept. |
| Below the rule | Trash all sessions… | Close every active session. Trashed processes keep running in Recently closed for 20 seconds, so a mistaken trash can be restored. |
| Below the rule | End all sessions… | End every active session outright. Ended sessions can't be restored; the confirmation reads End N sessions in {worktree}? |
Layout, Fleet selection and Maintenance each disappear when their subject does: no live panels, no Layout or Maintenance section; nothing armable, no Fleet selection. Clear session history… stays whatever else is on screen, and carries no count: availability isn't cached, and opening a menu must not go and read the journal to find out. It sits with the destructive pair rather than beside renderer maintenance because it is deletion, not repair: the journal records are gone permanently.
The items below the rule confirm before they act. End all sessions… and Clear session history… aren't offered in the action palette, and an agent calling an exposed destructive action over MCP goes through MCP approval instead of a second dialog. Tool availability still depends on its tool set.
WSL Git Banner
On Windows, when a worktree lives inside a WSL distribution, Daintree probes whether git can be routed through the interop layer and shows a banner on the card describing what it found.
The WSL git banner does not appear on macOS. Daintree always runs git natively.
The banner has four states.
Eligible: git is installed in the distribution and reachable. The title reads Speed up git for this worktree:
Git runs from Windows. Run it in {distro} for 5–10× faster status checks.
Two buttons: Enable WSL git switches this worktree to WSL-native git; No thanks dismisses.
Ineligible: the distribution isn't your default WSL distro, so git can't be routed through it. The title reads Git runs from Windows:
{distro} isn't your default WSL distro, so git can't run inside it.
Two buttons here too: Re-check, which shows a spinner while it runs and then reports what it found (Checked. Still not the default distro., Couldn't re-check. or WSL didn't answer.), and Got it.
Unreadable: the default distro couldn't be read at all, so routing is undetermined. The title reads Couldn't read your default WSL distro, with Git runs from Windows for now, which may be slower. The buttons are Retry and Got it. You are never stranded on a spinner.
Probing: a short skeleton while the probe resolves. It appears only if the probe is slow enough to be worth acknowledging.
The WSL git banner does not appear on Linux. Daintree always runs git natively.
Worktrees Outside the Project
Git will happily report worktrees that live outside the project directory. Daintree identifies those and sorts them apart: they sink below everything the project owns, ahead of the pin check, so a stale pin can't lift one back to the top. In grouped mode they get their own Outside the project section.
On the card, a FolderOutput icon carries the tooltip "Outside the project directory" and the full path. External worktrees can't be pinned, and the pin entry is ignored if one exists.
Containment is only asserted on an explicit answer from the workspace host. When the host can't resolve the boundary, the worktree is treated as internal: a transient path-resolution failure shouldn't demote every worktree in the project at once.
Pinning is the counterpart: Pin to top / Unpin on any non-main, non-external card's menu. Pinned worktrees sit directly under main and every sort honors that.