Project board

The project board is a Beads-backed Kanban view for each main repository. Switch to Kanban from the titlebar, create tickets with prompts, drag cards across lanes, and launch agent sessions with Create & Start or Start work.

WorkflowBeadsKanban

Opening the board

OptionWhat it does
Option+4Switch to Kanban view (rebindable in Settings → Hotkeys)
Kanban titlebar tabWorkarea view alongside Agents, Source, GitHub

Quick sessions do not have a Kanban project view — the titlebar tab is disabled with tooltip: Quick sessions do not have a Kanban project view.

The board loads in a bundled WKWebView (tasks-placeholder.html) with a native Beads bridge.

Board UI

OptionWhat it does
BoardActive view tab
Automations / Runs / TriageDisabled — Coming soon!
+ TicketCreate new ticket (board tab)
Refresh projectManual board refresh icon
Search ticketsFilter field in ticket filters bar
Filter by priorityAll, Urgent, High, Medium, Low
Filter by estimateAll, None, XS, S, M, L, XL

Auto-refresh runs every 8 s; labels refresh every 60 s. All bd commands run through bundled gxserver Beads — not a shell bd on PATH.

Kanban lanes

OptionWhat it does
BacklogBeads status: backlog
TodoBeads status: open
In ProgressBeads status: in_progress
TestBeads status: test
ReviewBeads status: review
DoneBeads status: closed

Lane headers show ticket count and a + button (aria: Add ticket to {lane}). Cards display IDs like ZMX-12 from beadsDisplayKey, plus priority, labels, estimate, and conversation link when present.

New Ticket dialog

OptionWhat it does
PriorityTicket priority metadata
T-shirtEstimate (XS–XL)
Labels / Blocking / Blocked byBeads relationship fields
TitleOptional — auto-generated from prompt when empty
PromptRequired — becomes agent work context
Start workFooter section — agent + location selectors
CreateCreate bead only, refresh board
Create & StartCreate bead, close dialog, launch agent immediately

Cmd+Enter submits in ticket dialogs. Escape clears the search field.

Create & Start workflow

  • Fill Prompt (required) and optional metadata.
  • Start work section — pick Agent (aria: Agent for Create and Start) and Location.
  • Location: Current project or New worktree.
  • Create & Start closes the dialog immediately, creates the bead, then launches agent with buildAgentWorkPrompt().
  • Session focus matches sidebar session-card behavior after terminal is ready.
  • Title generation and label assignment are secondary — prompt drives the session.

Edit ticket & Start work

  • Edit ticket dialog — same metadata plus Conversation section and Add comment.
  • Footer: Delete (two-click confirm), Start work / Go to Session, Save.
  • Right-click card context menu — Start work / Go to Session, Delete.
  • Go to Session when a conversation link already exists; Start work launches a new agent run.

Beads setup notices

OptionWhat it does
Initialize Beads for this projectShows copyable bd init command when .beads is missing
Beads CLI unavailableBroken bundled Beads binary
Project board unavailableOther gxserver or bridge errors

gxserver runs prefix reconciliation (ensureIssuePrefix) before create/list so ticket IDs use your configured display key.

Project settings

Settings → Projects → per main project:

OptionWhat it does
beadsDisplayKeyTicket key prefix — 3 letters like ZMX (Save Ticket Key)
beadsDirectoryAbsolute path to .beads directory (Save Beads Directory)

Settings → Agents → Default Prompt Agent drives board Start Work, Create & Start, and Git helper prompts.

Shortcuts

OptionWhat it does
Option+4Switch to Kanban view
Cmd+EnterSubmit in New Ticket / Edit ticket dialogs
EscapeClear ticket search field

Workarea views use Option+1..4: Agents, Source, GitHub, Kanban — all rebindable in Settings → Hotkeys.

Tips

  • Run bd init in the repo root before first board use — Ghostex shows the exact command when Beads is missing.
  • Use New worktree location for isolated feature work tied to a ticket.
  • Set beadsDisplayKey early so ticket IDs stay stable across the team.
  • Create & Start is the fastest path from idea to running agent — Create alone is for backlog grooming.
  • Conversation links on tickets enable Go to Session for resuming prior agent work on the same bead.

Related docs