Skip to main content
The Board is Clawboo’s durable record of every task your agents work on — who owns it, what state it’s in, whether it passed verification, and what it cost. It’s the canonical source of truth: group chat narrates it, but the board is the decision. Use this page to open the board, read its columns and cards, dig into a task’s detail drawer, and understand how task cards appear inline inside group chat.
The Board is always available — no feature gate and no setup required. An empty board just means no tasks have been created yet. The board polls for updates every five seconds, so you’ll see status changes appear without refreshing.

​
Open the board

Click Board (the kanban-square icon) in the secondary nav of the left sidebar. The panel fills the main content area.

​
The seven columns

Every task lives in exactly one column at a time. The columns run in lifecycle order from left to right:
ColumnStatusWhat it means
BacklogbacklogTriaged, but not ready to work
To dotodoReady and claimable by an agent
In progressin_progressActively owned by an assignee
In reviewin_reviewWork done, awaiting the verification gate
BlockedblockedStalled — a failed dependency or unresolved debt
DonedoneCompleted (terminal)
CancelledcancelledAbandoned (terminal)
Each column shows a live task count. The board header shows the total ({N} tasks). Use the Refresh button for an immediate re-fetch if you need it outside the five-second poll window.

​
Task cards

Each task appears as a card showing its title and a row of badges:
BadgeWhen it appearsWhat it means
RuntimeAlwaysThe runtime that owns the work (defaults to openclaw)
VerificationAfter a verdict is storedpass (green), fail (red), or debt (amber, for completed_with_debt)
CostWhen a cost is recordedUSD spend formatted to three decimals, e.g. $0.012
SubWhen the task has a parentThis task was spawned by a delegation from another task
Click any card to open its task-detail drawer.

​
The task-detail drawer

Clicking a card slides open a right-hand drawer that loads the task, its execution history, and its workspace detail all at once. Press Escape or click outside the drawer to close it.

​
Overview

The task’s core fields: Status, Assignee, Runtime, Cost, and (for subtasks) Parent — a truncated parent task ID.

​
Verification

The stored verification verdict, if one exists. It shows the verdict pill (pass / fail / completed_with_debt), the reviewer runtime and model, any debt notes, and any critic findings with their severity. A task with no verdict isn’t failing — it simply hasn’t been through the verification gate yet.

​
Workspace

The per-task git worktree detail:
  • Branch (clawboo/task-<id>) and the absolute Worktree path on disk.
  • A Diff summary — how many files changed, insertions, and deletions.
  • System-of-record files — TASK.md, task-progress.md, DECISIONS.json, init.sh, VERIFICATION.md, and AGENT_HANDOFF.json — each expandable to show its full contents.
  • The unified diff against the branch-point baseline.
Tasks without a worktree (research or review tasks, or work not yet provisioned) show “No worktree provisioned for this task.”

​
Execution ledger

Every run spawned for the task, oldest first. Each row shows the executor type, run status, cost, and token counts (input / output). If a run errored, the reason appears inline beneath the row.

​
Activity

A live terminal scoped to this task — streams tool calls, tool results, and errors in real time as the task runs. You can watch a run progress here without leaving the board.

​
Comments

The task’s discussion thread and system notes, each tagged with its author type. When a specialist finishes a delegated subtask, its report-up summary lands here as a comment.

​
Lineage

The task’s full ancestor chain, rendered as a chain of short IDs. Top-level tasks show “Top-level task (no ancestors).”

​
Create a task

You can create tasks directly on the board — just click New task in the board header and fill in the title, assignee, and optional metadata. If you prefer the API: 
# Create a task via the REST API
curl -X POST 'http://localhost:18790/api/board' \
  -H 'Content-Type: application/json' \
  -d '{"title": "Refactor auth module", "teamId": "<team-id>"}'
Tasks also appear automatically when an agent in group chat issues a delegation — see Group Chat.

​
The chat-fused board

In group chat, board tasks don’t live in a separate tab — they appear as inline cards in the conversation timeline at the moment the delegation was issued. Each inline card shows the task title, a status pill (Queued → Working → Review → Done / Blocked), and the assignee’s avatar. As the board’s status changes, the inline card updates in place. When a task completes, the card flips to Done and displays the report-up summary. These cards reload from the board after a page refresh, so they survive a browser reload.
Inline task cards and the standalone Board panel read the same canonical board. Neither is a write path back to the board — the card is narration; the board mutation is the actual state change.

​
Troubleshooting

A task is stuck in “In progress.” The board can’t detect a dead run just from timestamps. A long-running task and a dead one look the same from the panel. Check the task’s Activity terminal in the detail drawer for signs of life, or see the reconciliation docs for the server-side stale-sweep (60-minute default TTL).
A task is “Done” but has no verification badge. A task with no stored verdict is unverified, not failing. It reaches done normally. The verification gate only blocks a known non-promotable verdict. Manually completed tasks may carry no verdict at all.
  • Group Chat — where chat-fused board cards appear
  • Ghost Graph — visual agent activity overlaid on the org graph
  • Costs & Budgets — per-task cost shown on cards and in the drawer
  • Approvals — how risky delegations pause before landing on the board
  • Scheduler — how scheduled routines create board tasks automatically