Kanban Board
See agent names, status, recent updates, and live diff stats on a board. Preview conversations and terminals without leaving the board, and drag cards between labels.
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:
- An Unlabeled column holds everything unassigned.
- One column per worktree label you've created, in your chosen color.
Drag anywhere on a card to move it into another label. The destination column highlights as you drag; you can drop on its header, between cards, or in its empty space. Drop into Unlabeled to clear the card's labels. Hold the card near the board's left or right edge to scroll to other labels, or near a column's top or bottom edge to scroll its cards. Moving a card changes labels within its repository.
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. Columns adapt to the available width, with horizontal scrolling when they no longer fit.
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 |
|---|---|
| Agent name | The agent's display name, with its branch underneath |
| Status and update | Current activity and the latest agent notification |
Current | The worktree this window is looking at |
+124 / −38 | Live diff stats against the base |
#1924 | The worktree's pull request |
| Issue badge | A linked Linear or Sentry issue |
| Mode badge | Container or remote, rather than local |
| Relationship icons | Linked agents or blocking dependencies |
| Chat and terminal buttons | Preview the worktree's conversations and terminal sessions |
Preview an agent without leaving the board#
Hover a card for a quick look at its primary conversation or terminal. Click a card, or its chat or terminal button, to keep the preview open. The selected card gets an accent outline; the separate Current badge continues to identify your active worktree.
The detail pane opens beside the board in wide windows and below it in smaller windows. The board stays in place, and you can drag the divider to resize the preview. Card zoom leaves chat and terminal text at their normal sizes.
- Chat uses the same message bubbles, Markdown, code blocks, attachments, and tool activity as the normal conversation view. The preview is read-only; choose Open to reply or respond to a request.
- Terminal shows selectable output at the upper-left corner, using your terminal font and colors. Choose Use Terminal to move the live terminal into the pane and interact with it.
- If an agent has multiple conversations or terminals, choose a session from the detail pane's picker.
Double-click a card or choose Open to open its workspace. Use the close button or Escape to dismiss a passive preview. Once a terminal is active, Escape continues to work inside terminal applications.
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