Kanban Board
See every worktree in every repository as a card on a board — with live diff stats, PR status, linked issues, and a peek at each agent's running terminal. Drag a card to change its label.
When you're running ten agents at once, a list stops helping. The Kanban board turns your worktrees into cards, grouped into columns by label, so "what's in flight, what's waiting on review, what's stuck" is one glance instead of ten clicks.
Open it with Cmd+Opt+K, from View → Show Kanban Board, or with the board button in the toolbar. It opens as an editor tab, so it can sit in a split beside your work.
Columns are labels#
Each repository is its own collapsible section with its own set of columns:
- A No label column holds everything unassigned.
- One column per worktree label you've created, in your chosen color.
Drag a card into a column to assign that label. Drag a column header to reorder columns; the order is remembered per repository across restarts. A count in each header tells you how loaded that stage is.
What a card tells you#
Every worktree card carries the state you'd otherwise have to open the worktree to learn:
| On the card | Meaning |
|---|---|
| Branch name | The worktree's branch, or its folder name |
current | The worktree this window is looking at |
main | The repository's main checkout |
+124 / −38 | Live diff stats against the base |
PR#1924 | An open pull request, with its status |
| Issue badge | A linked Linear or Sentry issue |
| Mode badge | Container or remote, rather than local |
| Relationship badges | 3 linked, 2 blocked, merge→1, merge←2 |
| Terminal buttons | One per live agent session in that worktree |
Peek at a running agent#
The small terminal buttons on a card aren't decoration — each is a live session. Hover one to preview that terminal right on the board; click to expand it in place. You can see what an agent is doing without switching worktrees, losing your place, or waiting for a window to reload.
Cards show up to four sessions with a +N for the rest.
Labels#
Labels are per repository and carry a color. They drive three surfaces at once: the board's columns, the grouping in the worktree navigator, and the Label you can pick when launching from Agent Home — so a run can land in the right column the moment it starts.
From the CLI, dev agent create --label <name> does the same thing, which is how a script or a scheduled task files its work correctly without you sorting it afterwards.
Worktree relationships#
Parallel agent work isn't a flat list — one branch builds on another, one reviews another, two collide. Agentastic lets you record that.
Some edges are drawn automatically: creating a worktree from another records Forked From (or Based On Worktree when the source was the main checkout), and agents launched together as a batch are linked as a named group.
You can add the rest by hand from a worktree's context menu:
Depends On · Blocks · Reviews · Validates · Supersedes · Merged Into · Cherry-Picks From · Conflicts With · Shares Context With · Spawned By · Forked From · Based On Worktree
Directional edges (Blocks, Depends On, Reviews, …) point one way; symmetric ones (Conflicts With, Shares Context With) apply both ways. The resulting counts show up as badges on the board and in the navigator, so a branch that's blocking three others is visible before you wonder why nothing is merging. Clear All Relationships resets a worktree.
Related#
- Agents & Isolation — the worktree model behind the cards
- Git Worktrees — creating, basing, and removing worktrees
- Multi-Agent Programming — splitting work across parallel agents
- Scheduled Agents — runs that file themselves into a label