Workboard

Palette: Workboard: Open, Workboard: Next Waiting Agent · Menu: View → Workboard

Needs: the Orchestrator plugin, which provides the workspaces it shows.

The Workboard puts every Orchestrator workspace and its coding agent on one full-screen board, together with the agent sessions running outside the editor and the ones found in your agents' history, so you can see at a glance which agents are waiting on you, which have finished, and which are still working. Press Enter on a card to open that workspace.

┌ Workboard ─────────────────────────────────────────────────────────────────[×]┐
│[ 1 Inbox ][ 2 Projects ][ 3 Folders ][ 4 Board ]                ● 2   ✓ 1   * 2  │
│────────────────────────────────────────────────────────────────────────────────│
│       Workspace      Status                         Project  Branch        For │
│▼ NEEDS YOU  2                                                                  │
│    ●  rate-limit     Should I use Postgres or Redis? api      rate-limit    4m │
│    ●  login-fix      Allow running cargo test? (y/n) web      login-fix     1m │
│▼ READY TO REVIEW  1                                                            │
│    ✓  tab-names      finished, not looked at         web      tab-names · 3 changed │
│▼ WORKING  2                                                                    │
│    *  billing-ui                                     api      billing-ui    2m │
│Enter open  n next waiting  Tab/1-4 lens  Esc close                             │
└────────────────────────────────────────────────────────────────────────────────┘

The state symbols are the Orchestrator dock's own: ● waiting on you, ✓ finished work you haven't looked at, * working, · idle. The time on each card is how long it has been in that state, counted from when the Workboard first saw it.

The list lenses are tables: a heading per group (← / → or a click fold it), then a row per workspace with its status, project, branch, working-tree changes and how long it has been in its state. The status is a waiting agent's question, "finished, not looked at", or a failed create's reason.

Lenses

Tab / Shift+Tab cycle through four ways of arranging the same workspaces, and 1–4 pick one directly. The workspace under the cursor stays under it when you switch, scrolled into view. The board reopens on the lens you used last.

Lens	What it shows
Inbox	Sorted by what needs you: Needs you (agent asked a question), Ready to review (finished, unseen), Working, Parked, then Detected (sessions found in history, newest first). In the first two, the one that has waited longest is on top. A waiting agent's question is its status; a workspace whose create failed waits here too, with the reason.
Projects	One group per project, resolved the way Import sessions resolves one: by the repository's git remote (origin, else the first remote), so every worktree of a repo and every clone of it, wherever it sits on disk, lands in the same group, and the ssh and https forms of one URL match. A repository with no remote is grouped by its root, anything else by its directory. A cloud session joins the group of the GitHub repository it works on.
Folders	The Orchestrator dock's folders, in the dock's order, so an arrangement you made by hand is one key away. Drag a workspace onto a folder (or onto a workspace in it) to file it there; drop it on Not in a folder to unfile it. Sessions outside the editor are listed under Outside the editor.
Board	A kanban board that fills itself, one column of cards each: Backlog, Needs me, Working, Review, Shipped.

How the Board places cards

Each card goes to a column from its agent's state:

State	Column
Waiting on you	Needs me
Working, or still being created	Working
A create that failed (retry or dismiss it from the dock)	Needs me
Finished, not yet looked at	Review
Idle, with uncommitted or unpushed work	Review
Idle and clean	Backlog
Found in history	Backlog

Nothing on a workspace says it was merged, so Shipped is reached only by hand. Press Shift+← / Shift+→ (or < / >) to pin a card one column left or right. A pinned card shows ⊙ and stays where you put it while its agent's state changes. Press p to unpin it. Moving a card back onto its automatic column removes the pin. Pins are saved and survive restarts.

Sessions outside the editor

Besides the Orchestrator's workspaces, the board lists:

• Agents running outside the editor: the Claude Code and Codex sessions the Orchestrator dock lists under its external sessions (in a terminal, in Claude Desktop or an editor extension, in the cloud), except those a workspace already stands for. They are placed by their state like workspaces: a waiting one is in Needs you with its question. Enter opens one as the dock's Open does.
• Detected sessions: what the Orchestrator's Import sessions finds on every reachable machine (Claude Code and Codex transcripts, tmux and other multiplexer panes, other orchestrators' worktrees) and was active in the last 14 days. A session whose directory is already on the board, as a workspace or a running session, is left out: that card is the one for the work. Enter opens the New Workspace form filled in to resume it, as Import sessions does.

Both are refreshed when the board opens and periodically while it is open. The status-bar beacon and Next Waiting Agent count only the editor's own workspaces, since there is nowhere in the editor to jump to for the others.

Keys

The cards are ordinary lists and trees, so they answer the keys and the mouse the way every list in Fresh does: ↑ ↓ move, a click selects, the wheel scrolls, Enter opens. On the Board, ← → move to the card beside, in the next column that has cards: empty columns are skipped.

Key	Action
Enter	Open the workspace and close the board
n	Move to the next card that needs you (waiting first, then finished)
Tab / Shift+Tab, 1–4	Change lens (or click a lens button)
Shift+← Shift+→, < >	Board: move (pin) the card one column left or right
p	Board: unpin the card
Esc / q	Close

Status-bar beacon

While any agent is waiting on you or has finished unseen work, the status bar shows a count such as ● 2 waiting ✓ 1 done. When nothing needs you it is empty and takes no room. Click it, or run Workboard: Next Waiting Agent, to jump to the agent that has waited longest (or, if none is waiting, the oldest finished work). The jump never picks the workspace you are already in.

The beacon adds itself to the right of the status bar for the current run, without editing config.json. To place it yourself, put {workboard:attention} in editor.status_bar.left or editor.status_bar.right. To turn it off, set Plugins → workboard → statusBarBeacon to off in the Settings UI.

From a script

The plugin exports a small API for init.ts or scripts:

const board = editor.getPluginApi("workboard");
board?.setLens("board"); // "inbox" | "projects" | "folders" | "board"
board?.open();

A plugin can add its own sessions to the board — another agent's, a CI queue's — with registerSource. The board asks list() on every refresh, so it answers from what it has; refresh() is where to fetch, and it is called when the board opens and every refreshMs while it stays open:

const board = editor.getPluginApi("workboard");
const unregister = board?.registerSource({
  id: "my-agents",
  label: "My agents",
  kind: "running", // or "history": listed under Detected, parked on the Board
  list: () => mySessions.map((s) => ({
    id: s.id,
    title: s.name,
    state: s.waiting ? "blocked" : "working", // "done" | "idle" | "unknown"
    cwd: s.dir,               // grouped into its project by the board
    question: s.prompt,       // shown while it waits
  })),
  refresh: () => fetchMySessions(),
  refreshMs: 60_000,
  open: (id) => attach(id),   // return a string to show why it could not open
});

The types (WorkboardSource, WorkboardItem, WorkboardApi) are in plugins/lib/workboard_model.ts.

Bind a key to Workboard: Open in the keybinding editor to bring the board up from anywhere, including from inside an agent's terminal.