coordinate work / board

Give work to a Session as an item, and follow it to done.

After this page, you can create a Board item, assign it to a Claude Code or Codex Session, and tell from the card which phase it is in and what it still needs from you.

Checked against the product on 6 October 2026

Latest release: Clawdline v2.9.0 · platform support

Before you start

  • Free and local. Each machine keeps its own items.
  • The console is in Traditional Chinese only. Each label below is shown as it appears, with its meaning in parentheses.
  • Sessions move items themselves once they have the Clawdline skill; see Dispatch, handoff, and landing.

Turn the Board on

  1. Open 設定 (Settings).
  2. Find 啟用看板系統 (Enable Project Board) and press it so it reads 已啟用 (enabled).

Expected result: the block says 已儲存 (saved). The 看板 (Board) row is always in the menu. Undo: press it again; turning the Board off keeps its history.

Create an item

  1. Open 看板 and press + 建立項目 (create item).
  2. Choose the Project and the 類型 (kind).
  3. Fill in 標題 (title), 描述 (description), and 驗收條件(Markdown) (acceptance criteria). You can dictate the description and add up to six reference pictures. Two or more top-level list items in the description become the item's steps.
  4. Press 建立 (create).
KindWhere it goes
Feature, Issue, Epic待指派 (unassigned), ready to assign
Refactor, Plan規劃區 (planning); not assigned

Assign it to a Session

On the card, do one of these:

  • Press 選擇既有 Session (choose an existing Session), pick one, and press 指派 (assign).
  • Choose Claude Code or Codex and press the 開新 … Session (open a new Session) button.

Expected result: the card leaves 待指派. 前往 Session (go to Session) opens its owner, and 提醒 Session (remind Session) reminds it of the item.

Plan review and verification gates

Two switches in 設定 → 規劃與驗證 gate decide what an item must pass:

  • Planning: on by default. A Feature or Epic needs a plan and an independent plan review before implementation starts. An Issue is exempt.
  • Independent verification: off by default. When on, the card shows the latest result. NEEDS_WORK, stale evidence, and a technical failure never count as a pass. When evidence fills up, export it from 驗證詳情容量與匯出 before clearing old detail.

An item keeps the values it had when it was first assigned in that cycle; changing a switch affects later cycles.

How an item moves

The owning Session moves the item. Clawdline refuses a move without the evidence it needs:

On the cardPhaseThe Session must show
實作implementing—
驗證verifying—
Merge 回 Gitmerginghow it was verified
部署deployinga verified landing of the commit
已完成doneevery step completed

Epics. A card split out of an Epic shows ↑ Epic〈title〉; the Epic's detail lists its 子項目 (child items). A card a Session created carries an Agent 建立 (created by agent) badge.

Proposals and questions. A Session can suggest an item under Agent 提案 (agent proposals); press 接受並建立 (accept and create) or 拒絕 (reject). Nothing is accepted for you. When the owner needs an answer, the question and its buttons appear in the card under 需要你決定 (needs your decision), with the default answer it takes at the deadline.

Session to-dos

Small tasks for one Session do not need a Board item. Open the Session and use the Session 待辦 (Session to-dos) fold. It lists the items that Session owns and its direct to-dos. Press + to add one; press the checkbox to complete it or restore it. A Session adds its own to-dos only when you ask:

A direct to-do is work saved for later. Adding it does not send a conversation message, interrupt the current turn, or wake an idle Session. The Session can take it when it next checks its work. If you need action now, send a message with 送出 (Send). Use a Board item for larger work that needs its own assignment and delivery record.

clawdline todo add "Write the migration" "Update the README"
clawdline todo list
clawdline todo done <to-do id>

Verify a change later

Some changes can only be judged later, such as a setting you lowered to cut cost. 驗收 (Verify; heading 等待驗收, Waiting to be verified) keeps each one with why, what counts as it holding, the data, notes, and a verdict.

  1. Create a record from a terminal or a Session (below).
  2. When it is due, open it and mark each criterion 標為通過 (passed) or 標為未通過 (failed).
  3. Finish with 驗收通過 (accept) or 不通過 (reject). A reason is required.
clawdline verify add --title "Earlier compaction" --due 7d \
  --criterion "cost per task is lower" --why "compaction window lowered"
clawdline verify list
clawdline verify done <id> --accepted "held for two weeks"

Where to go deeper