Skip to main content
The board shows every task your teams work on. Each task is a card, and its column says where it stands. Agents add and move cards as they work. You use the board to see what is happening, act on work that waits on you, give an agent a task, and steer one that is running. The board opens on Kanban: every task by status, newest first. Today, Week and Month are calendar views that lay the same cards out by the day each was added or finished. Every task handed out in a team chat, or from Boo Zero’s own chat, is a card here. How tasks, statuses and dependencies work underneath is explained in The board. The board on Kanban for all teams: five tasks that need a person lead the first column, each with its reason and one button, then Backlog, To do, In progress and Done, with Cancelled folded into a rail

Track work in five steps

1

Open the board

Click Board in the sidebar, or press Cmd+2 (Ctrl+2 on Windows and Linux). The board opens on Kanban the first time, and on the view you picked after that. The team filter beside the Board title shows All teams or one team.
2

Read a card

Each card shows the task’s title and one row of details: the agent’s face, a status mark such as Verifying or the cost, and when the task was added or finished. See Read a card.
3

Act on Needs you

The first column, Needs you, holds approvals and tasks that will not move until you act. Each card says why it waits and carries the one button that gets it moving. See Things that need you.
4

Open a task

Click a card to open its drawer: the agent’s report, the brief, the task’s properties, every run, comments with a box to reply to the agent, and live activity. See The task drawer.
5

Find a task

Click the search button in the toolbar, press / while the board has focus, or press Cmd+K (Ctrl+K). Type part of a title, an agent’s name or words from the details. Enter shows the card on the board, and Shift+Enter opens its drawer.

The header and toolbar

The header holds the Board title, the team filter, and New task (press C). When something changed while you were away, a chip beside the team filter says what; see Since you last looked under Views and the calendar. The toolbar under it holds these controls, left to right: The filter applies to every column, Needs you included, and starts over when you change the team filter. Find still searches every task. When the filter hides every task, the board says “No tasks match these filters” with Clear filters. On a calendar view, the left of the toolbar holds Today, the previous and next arrows, and the range title. On Kanban it reads “Every task by status, newest first”. There is no refresh button: the board reloads itself every five seconds while it is on screen, and a small spinner shows only when a reload is slow.

Columns and statuses

There is no Blocked column and no In review column. A blocked task needs a person, so it sits in Needs you, unless it waits on another task or on its own sub-tasks: then it sits in In progress, saying what it waits on. A task under review stays in In progress with a Verifying mark. A task with a status the board does not recognize appears in an extra Other column. Each column title has a small status mark in the column’s color, and counts the tasks the column holds in the range on screen (every task on Kanban). An empty column shows no count, and an empty Kanban lane says so, for example “Nothing running”.

Your requests and their sub-tasks

When a team’s lead hands out work for something you asked in chat, the board shows your request as one card, with the helpers’ tasks under it. The card says how far the work has got, like 2 of 3 done, and its cost is what its work has cost so far. Click 3 sub-tasks to fold or open the list, and click a row to open that sub-task. A finished request starts folded. The card moves by itself: it sits in In progress until everything under it has closed and the lead has written its summary, then moves to Done, or to Cancelled if none of its work got done. You cannot drag it. To end it early, open it and set its status to Done or Cancelled: the sub-tasks still open are cancelled too, and any run on them stops. The board asks first. To add to a request, type in its reply box. Your words go to the agent looking after it, which can hand out more under it. To say more on a finished one, Reopen it with your words: it goes back to In progress, its lead reads them, and it closes again after the lead’s reply unless that hands out more. A new message in the chat is a new request. A sub-task that needs you also shows in Needs you, with For CLB-12 under its title to say which request it belongs to. If you filter the board so a request is hidden but one of its sub-tasks is not, the sub-task shows on its own with the same label.

Read a card

Cards are neutral: color appears only in the status marks, and amber marks what needs you. A card shows the task’s title, on up to two lines, and one row of details:
  • Id: the task’s readable id, like MAR-12. See Task ids.
  • Agent: the face of the agent that has the task. In To do, a dashed circle means no agent is bound to it.
  • Priority: two small up chevrons for an Urgent task, one for High. A Normal or Low task shows nothing here. Point at the mark to read it.
  • Status mark: Verifying while the work is checked, and Waiting to check while its check waits for teammates to finish in the team folder. After a check, an amber cross means it failed, an amber dashed circle means it passed with debt (open issues noted), and a green check means it passed (until the card reaches Done). A card with no mark shows its cost here.
  • Cost: what all of the task’s runs cost, once a run has recorded a cost. A figure that starts with ~ is an estimate: the runtime reported no charge, so Clawboo priced the run itself. A cost under a cent reads <$0.01, and a task whose runs all ran on a model your own Ollama serves reads free. When a status mark takes the cost’s place, point at the card to see the cost. Which runtimes report real cost is in Budgets and spend.
  • Paused: a small pause mark when a pause covers the task. Point at it to read what is paused and who paused it. The face of a paused agent carries the same mark wherever it shows.
  • Subtask: a small arrow when another task handed this one out and the card has no mark or cost to show. Otherwise the mark’s or the cost’s tooltip says it is a subtask.
  • Labels: up to two of the task’s labels, then a count of the rest. See Labels.
  • Time: on Kanban, how long ago the task was added or finished, such as “4m ago”, “Yesterday” or “3d ago”. A calendar view shows the clock time, and the Earlier row the date. A running task shows how long its current run has gone, after a small live dot. Point at the time for the full date.
Display > On cards turns the Cost and Time off and on for every card.

Things that need you

Needs you collects everything that waits on a person, for the teams in the filter. It holds two kinds of item:
  • Approvals: an agent wants to run a command, use a risky tool, or make a risky handoff. Answer them on their card. See Approvals.
  • Tasks that will not move by themselves. Each card says why in amber, with the reason the run recorded when there is one, and shows the agent.
A card saying This job has started 100 runs by itself means the job reached its limit of runs it may start without anyone asking. What it would start next is waiting. Carry on allows another 100 and starts it. Stop is about this job alone: it ends the runs going under it, on the team’s chat and the task runner, and nothing under it starts by itself after that. Other jobs in the same chat keep going, and the card stays down. Each task says why it waits: one that was going to start reads Stopped and offers Retry, and a step waiting behind it says it stopped with its job. Your own message, Retry and reply still go, with the card up or after a Stop. Starting work in the job again may bring the card back, the next time something would start by itself. A Waiting for your OK card asks whether agents may wake each other on this job. Allow on this job covers the task and everything under it, and starts what was waiting. Always allow in this team also stops asking for the team’s other jobs. No keeps the comments on the thread and starts nothing, and you are not asked again on this job. A team shows one such card at a time: when other tasks wait on the same answer the card says how many, and your answer covers them too. The same card comes back as Let them carry on or No more on this job when agents on the job have started each other 12 times in an hour, or two of them keep answering each other, on one job or across several. A pause for the hourly limit also ends by itself when the hour is over. A card goes away by itself once no comment is waiting on it, for example when a run on the task took the comment. A comment from you always wakes the agent, whatever the card says. If the task also failed its check, the card says so and offers Review, because a yes starts the agent and the check still stands. To change the team’s setting later, open the team’s settings, under Agents waking each other. When several runs in a row failed, the badge counts them, for example Failed 2×. Each card has one button for the next step, and a More menu (the three dots) with the rest. The More menu holds what the card’s button does not: Retry (Give back to the agent, on a task an agent handed back), Take it yourself, the team’s agents under Assign to (or Give to someone else when the task is bound to an agent), and always Dismiss. Dismiss asks first, then moves the task to Cancelled, along with any later plan steps that were waiting on it. On a request, every sub-task still open goes with it, and any run on them stops. A run still going, work being checked, and a card that only holds a plan offer only Dismiss, since nothing else would be accepted. A Waiting for your answer card has the question and its controls right on it, and so does the task drawer: a button for each option, a box for free text, Yes and No for a confirmation, and for suggested tasks a list you can edit, then Accept or Turn down. Your answer goes on the task’s comments in your name, with the agent’s question just above it under the agent’s name, and starts the agent again. Like a reply, it is saved as a wake first, so a restart cannot lose it, and while Clawboo is holding new runs it waits for the hold to lift. An accepted list is for the agent to create. A question closes without an answer when the task finishes or moves on, or when the agent asks a newer one. An answer that comes too late says so and changes nothing. A Sign-in failed or Billing problem task leads with Fix sign-in instead of Retry, because a retry fails the same way until the account is fixed. Retry stays in the More menu, and it asks first, quoting the error. Clawboo never retries such a task by itself, and when it failed in team chat, the lead is told not to hand it out again. Retry and Assign also leave a note in the task’s comments. A task the task runner ran (an agent Routine, or a run started through the API) runs through the task runner again when the agent is on Clawboo Native, Claude Code, Codex or Hermes: in a worktree when the task names a repository, and checked as before. If that run cannot start, for example because a budget it counts against is paused, the task waits in Needs you with the reason. Other tasks, and tasks the runner ran before Clawboo started saving how it ran them, run in team chat; see How a team works. Tasks that failed the same way share one card that lists them, with Retry all and, in its More menu, Dismiss all, which asks first. When nothing waits, the column says “Nothing needs you right now”. In Week and Month, Needs you shows three items, then +N more. While you look at another week or month, Needs you folds into a narrow rail with its count: click it to go back to today.

Get an alert outside the tab

Clawboo can send a browser notification when something new needs you while its tab is in the background or its window is not in front. Once the board has a task on it, the header offers Get an alert when something needs you, even with this tab in the background. Click Turn on, then allow notifications when your browser asks. Not now puts the offer away. Clawboo asks your browser only when you click Turn on, never by itself. Click an alert to bring the tab back. An alert about one task opens it in the drawer. Any other alert opens the board on Needs you, on the team it is about. Alerts cover only what arrives after the tab went to the background, so nothing you have already seen is announced again. A task you moved to Blocked yourself, a task you stopped, a task you took yourself, a task with no agent and a task held back by a pause are never announced. Turn alerts off, or send a test alert, in Settings > System > Alerts. In the Clawboo desktop app your computer’s own notifications tell you instead, so the browser alerts stay off there. Clicking one opens the task it is about, or Needs you with the approval it is about brought into view. A tab your browser has put to sleep to save memory cannot send alerts.

See it all in the Inbox

Inbox in the sidebar is the board from your side: what wants you, whichever view you are on. Its red badge counts what is unread and what needs you, each thing once, and goes up by itself as things change. While the sidebar is collapsed, or closed on a phone, a red dot on its button says there is something to see. Opening a task, from anywhere, is what reads it, and so is acting on it. A comment, a move, Dismiss, Retry, Assign, a task you create, and pressing Stop in a team chat all count, so what you do yourself never comes back to you as unread. That includes an agent’s comment you had not opened when you dragged the card: it stops counting as unread, though it stays on the task. An agent’s progress after that is unread again, including the run your Retry starts. A run your comment, your answer to a question or your Reopen starts is different: the card moving back to To do and on to In progress does not show as unread for you, even some time later, such as when a hold lifts. Anything you had not read by then stays unread, and what the agent does next is unread as usual. The app’s own notes, such as a run being stopped, do not count. Mark all read, on Unread and All, clears everything listed, for the team you have picked or for every team. Read state is kept on the server, so it is the same in every browser you open Clawboo in, and it survives a restart. With no sign-in, Clawboo has one built-in reader for everyone who opens the dashboard. Behind a sign-in proxy each signed-in person has their own, and one person’s comment is unread for the next. The badge updates while the app is open. An app installed on a phone gets nothing while it is closed, because it has no background worker; the badge catches up when you open it.

When a task runs again by itself

If a run crashes or stops responding and its task goes back to To do, Clawboo starts it again by itself, through the task runner for a task the runner ran. A run whose sign-in or billing was refused is the exception: it goes to Needs you at once. After three unsuccessful runs in a row it stops trying, and the task waits in Needs you as Failed 3× or Timed out 3×. Crashes and failures are counted apart, and it stops at 3 in a row of either. A task you stopped never restarts by itself. A budget cap or the circuit breaker stopping a run is not your Stop, and the card says which it was. A task that was in review when Clawboo restarted does not run again by itself either: it waits in Needs you with a comment saying its run stopped. Retry always runs a task again, whatever its count. In team chat a run’s ending decides what comes next, so a retry happens only when it can help:
  • The provider rate limited the run, was overloaded, or could not be reached. The task goes back to To do and says so, then runs again after 30 seconds and after 60 seconds of time the machine is awake, with a little added. It holds no run slot and no budget while it waits, a restart picks up where it was, and Stop cancels the wait. After two retries it waits in Needs you as Rate limited or Provider unavailable, and whoever handed it out is told. A task on the task runner waits at least as long before each automatic rerun. A comment from you starts it at once. A task that has already failed 3 times in a row does not retry by itself, so a Retry that hits the same limit goes straight back to Needs you.
  • The agent replied with nothing and has nothing else to show. It gets one more turn, asked to say what it did. A second empty reply waits in Needs you as No result. A reply of only a control token such as __skipped__ counts as empty. An empty reply reaches Done in one case: the run changed the team’s folder and the team’s work check passed it. If a teammate was working in the folder at the same time, the change may not be this agent’s, so it is asked first.
  • The agent ran out of room. It gets one more run to continue, and what it wrote so far stays on the task. A second time waits in Needs you as Out of room. Each kind of extra turn happens once until something new starts the task, so the two cannot hand each other more.
  • A hard budget cap stopped it. It waits in Needs you as Budget cap. Raise the cap, then Retry. When the rest of a budget is only set aside by runs already going, the task waits in To do instead, and starts by itself once they end. If what they spent fills the cap, it comes to Needs you as Budget cap, and whoever handed it out is told.
A refused sign-in or billing is never retried: the card offers Fix sign-in. In all these cases the later plan steps stay queued, so a Retry carries the plan on. A task that runs again in team chat, by itself or through Retry, a reply or Assign, does not start from zero. Its agent is told how the last attempt ended (the error, a timeout, or that the run was cut off) and sees the task’s newest comments. After a timeout or a run that was cut off, it is also told to check what is already done before it repeats anything. On Clawboo Native, Claude Code, Codex and Hermes it also continues its own session from its last run on the task, and then gets only the comments made since. When a run on any of them outgrows the model’s context window, its session is not continued: the next run starts fresh. A task you give to a different agent starts fresh. See What an agent sees. Deleting a chat room stops its work the same way. Its unfinished tasks move to General: the ones that were queued for an agent wait in Needs you as Stopped, and Retry runs them there. An agent working on a task in team chat can mark that task blocked, saying what it waits on. Waiting on you, the task waits in Needs you as Blocked, saying what it needs, with the agent’s reply as its comment, and whoever handed out the task is told. Steps of a plan that wait on it stay queued, so a Retry carries the plan on. Waiting on another task, it stays out of Needs you and goes back to To do when that task is done, which starts its agent. If that task is cancelled, it comes to Needs you to say so. Waiting on its own sub-tasks, it does the same when they have closed, and a task whose run ends with work it handed out still going waits this way by itself: see A task that hands out work waits for it. The card says Waiting on 3 sub-tasks, and how many of those need you. Those are in Needs you on their own. A sub-task you move to the Backlog counts as closed and not done, so the wait does not hang on it. If you move the one task it waits on to the Backlog, nothing tells you it is still waiting, apart from its card. When a task fails for any other reason, the later plan steps that were waiting on it are cancelled. When an agent handed the task out, that agent is told, so nothing waits forever. A task whose work failed the team’s check, or whose fix round could not start, keeps its later steps queued instead, so a Retry carries the plan on.

Give an agent a task

1

Open New task

Click New task in the board’s header, or press C. The + in the To do column’s title opens it too.
2

Say what should get done

Write one sentence under What should get done?, for example “Draft the launch announcement”. It becomes the task’s title.
3

Check the agent

Beside For, Clawboo suggests an agent, with a note that says why: Fits the task, Last used or Team lead. To give the task to someone else, pick another agent from the list. Picking an agent also picks its team.To keep the task for yourself, pick You. It waits in Needs you as Assigned to you, and nothing starts it.
4

Add details if you need to

More options opens Team, Agent, Goal (when the team has goals) and Details. Use Details for context, constraints, or a description of what done looks like.
5

Send it

Press Enter, or click Send to followed by the agent’s name.
You should see the card appear in To do and move to In progress when the agent starts. If the agent is busy, the task waits in To do and starts when the agent is free. How Clawboo picks the agent it suggests:
  • It matches the words of your sentence against each agent’s name and the role in its SOUL.md (see Agents). A word in the name counts more than one in the role, and forms of a word count as one, so “drafting” matches “drafts”. OpenClaw agents, and agents whose SOUL.md states no role, match by name only.
  • When nothing matches, it suggests the agent you last gave a task to in this browser, then the team lead, then the team’s first agent.
  • The list holds the agents of the team in the board’s team filter. With All teams, it holds every team’s agents, each with its team’s name.
A task you give an agent this way is yours:
  • Only that agent works on it. The agent is asked to do the work itself rather than hand it to a teammate. It is asked to make reasonable assumptions and note them instead of asking you questions, though you can still steer it with a reply.
  • Its result goes on the task’s card, on the board and in the team’s General chat. It is not passed to the team leader.
  • If the run fails, the card moves to Needs you with the reason.
Assign on a Needs you card works the same way for a task that has no agent.

Steer a running task

Reply on a task to talk to the agent it belongs to. While the task runs, the agent reads your reply during the run where its runtime allows it. When the task waits on you, your reply starts the agent on it again, so answering a blocked task needs no click on Retry.
1

Open the task

Click its card to open the drawer. The reply box sits under Comments and reads Reply to followed by the agent’s name. You can also open the task in a team chat’s Tasks card (see Team chat), or in Tasks & Routines on the agent’s page (see Agents), where the box reads Comment or steer this task….
2

Check what sending does

The line beside Send says what sending does for this task as it stands, for example that the agent gets it in the current run, or that sending starts the agent on it again.
3

Write and send

Type your reply and press Send or Enter (Shift+Enter adds a new line).
You should see your reply under Comments as You, with a note under it that says where it went. When a reply starts a task again, Clawboo adds the note “Started again for a person’s reply.” to its comments. Replies you send while a run is already on its way for an earlier one start no second run, and replies within a second of each other go into a running task together. While Clawboo is holding new runs, a reply that would start the task waits for the hold to lift, and the note says so. The note under a reply is not saved with it: it shows until you close the task. Until a reply reaches the agent, a line above the box says what it is waiting for. Reopen the task puts it back in To do and starts its agent with your reply. See Reopen a finished task. Send as a follow-up task gives the same agent a new task, named after the finished one (for example “Follow up: Draft the launch post”). Your reply becomes its brief, the finished task is its Parent, and it goes to the agent like a task you add with New task. The note then reads “Sent as a follow-up task for Ada”. A reply is saved as a wake on the task first, so a restart cannot lose it. If a run cannot take it in time, the agent reads it in its task block at the next turn, once. A task the task runner runs has no task block, so there the reply also goes into the agent’s mailbox and the agent reads it when its next run starts. A steered reply and a mailbox note carry the first 1,000 characters and say when they were cut, and the task keeps all of it. On team chat work, a reply cut this way also comes whole at the next turn. How each runtime takes a reply mid-run, including older Codex versions, is in Choose a runtime.

Pause work

A pause holds back one agent, one team, or a task with the tasks under it, until you resume it. It lasts through a restart, and it has no time limit. What happens:
  • Runs stop within seconds. A task whose run stopped goes back to To do and keeps its agent. The task’s comments say why. It does not show in Needs you. A routine’s run that stops does not count as having run: it runs again on resume, as a new task, and its stopped card is set aside.
  • Nothing it covers starts. No task starts, no Routine fires and no message wakes it. A run already waiting for a free run slot stays waiting. Retry says the task is paused.
  • Messages get an answer. A message to a paused agent or team stays in the chat, with a line saying it did not start. The agent does not get it, so send it again after you resume. A reply on a paused task is saved, and the note under it says so. So is your answer to an agent’s question, and a note on a task you reopen. The agent starts on them after the resume, on a task in Needs you too, and the task drawer says what it waits for. A comment you write on a task whose agent asked you a question counts the same as with no pause: it starts the task, and the question closes unanswered.
  • Tasks keep their place. Each task stays in its status, and you can still assign tasks to a paused agent. They wait in To do. A task an agent asked you about still shows its question in Needs you, and you can answer it during the pause. A task you took yourself stays yours: it reads as neither paused nor started by a resume. A task waiting on work a pause holds keeps waiting and reads as needing nobody, and its agent takes its turn after the resume, with every result that came back.
Resume is on the banner in the agent’s chat, the team’s chat and the task drawer. A team’s chat shows it for the team, or for its lead: messages that name nobody go to the lead, so pausing Boo Zero holds every team it leads. Waiting work starts again at once: stopped tasks go first, and a Routine that fell due during the pause runs once. Tasks you stopped with Stop do not start again. Things a pause does not do:
  • A 1:1 chat with an OpenClaw agent runs in the OpenClaw Gateway, so it still works. The chat’s banner says so.
  • A team’s work check that is already running finishes its command. It starts no reviewer under the pause, and the result says the review did not run. If the check fails, the task waits in To do with what it found.
  • Pausing a team does not pause its agents’ work for another team, and it does not change their tasks’ priority.
Archiving a team stops its runs the same way, and nothing wakes its agents while it is archived. You can still chat 1:1 with them. Bring the team back and its work starts again.

The task drawer

Click any card to open its drawer on the right. It reads like a document: the task’s title, with its status, agent and team under it. Press Escape or click outside it to close it. To step through the card’s column without closing the drawer, press J for the next task and K for the previous one, or use the up and down arrow buttons at the top of the drawer. The drawer shows where you are, for example “2 of 5”. The keys do nothing while you type in a field or have a list open. Each section folds from its heading, and a section with nothing in it is not shown. Top to bottom: When the task has a plan, a Details and Plan tab pair shows under the title. Plan shows the plan as a document, with a button for each older revision and who accepted or turned it down. If the plan on show is waiting for you, its controls are there as well, with each step in full. The document is the agent’s own summary, and the steps are what would run. See Decide on a plan. Click the Parent to open that task in the drawer. A run that is still going can show OpenClaw as its runtime in Run history until it ends. The drawer’s cost is the same total as the card’s, to four decimal places, or free for a task that ran only on a local model. An image in the agent’s report or its comments shows as a link named after its alt text, such as Image: sales chart. It opens in a new tab only when you click it. Clawboo never loads it by itself, so an agent cannot send data out in an image’s address without your click. An address that is not a web or same-site one is only named, not linked. The task drawer open over the Kanban board: Rin's report, the brief, the task's properties, and a passed verification

Change a task’s status

Use Status in the drawer’s Properties, or drag the card to another column. Both follow the same rules:
  • Only moves the board allows are offered. While you drag, columns that will not take the card are dimmed, and so is Needs you. Done and Cancelled cards cannot be moved.
  • In progress is set only by an agent’s run, so you cannot move a card there by hand.
  • Moving a card to Done or Cancelled from a day other than today asks which day it finished: Today, the day it sits on, or Another day.
  • Cancelling always asks first, because it cannot be undone. Later plan steps that were waiting on the task are cancelled with it.
  • If an agent is still working on the task, the prompt says so. Moving the card to Done, Cancelled or To do stops that run. When an agent handed the task out, that agent is told a person decided it.
  • Your move stands. After you move a card, its agent cannot change the task’s status, block it or unblock it until a new run starts on the task. The agent is told the status is yours to set and not to try again. A run that starts after your move works the task as usual.
  • A card moved back to To do goes back to its agent’s queue, and a run that was going starts over from the beginning. A card with no agent waits in Needs you as Unassigned.
  • If the task’s stored check result cannot pass, moving it to Done asks you to confirm with Complete anyway. The override is recorded in the audit log.
Cards in Needs you move with their own buttons instead of by dragging. With a mouse, drag a card from anywhere on it. To drag with the keyboard, focus a card’s handle and press Space, choose a column with the arrow keys, then press Space to drop it or Escape to cancel. On a touch screen, drag a card by its handle.

Reopen a finished task

A Done or Cancelled task’s drawer has Reopen. Say what should change, if you like, and it goes back to To do, without its finish date. Its agent starts again, in a fresh session, with your words. In team chat it also has the task’s comments in front of it. A run on the task runner gets your words from its mailbox and no comments. Reopening a task assigned to you gives it back to you, and a task with no agent waits in Needs you for you to assign one. Plan steps cancelled along with it stay cancelled. A step whose earlier step stays cancelled cannot be reopened, because nothing would ever start it: Reopen says so, and you reopen the earlier step first. Agents have no tool for it, and the route takes only a request from the board’s own page, which on a local install is a speed bump.

Set a task’s priority

A task has one of four priorities: Urgent, High, Normal (every task starts there) and Low. Only you can set Urgent: an agent creating a task stops at High. Change it with Priority in the drawer’s Properties. When an agent has several tasks waiting, it starts one that already ran and came back first, then the highest priority, then the oldest. A task that keeps waiting reads one priority higher every 4 hours, up to High, so a Low task gets through newer work in the end. Only a task you marked Urgent reads as Urgent, so it always goes first. Priority also counts when every run slot is taken: an Urgent task goes ahead of runs that queued before it. An agent that creates a task through its Tasks tools can set its priority too, as a number from 1 (High) down to -1 (Low); any other number is held to that range, so no agent’s task can jump ahead of an urgent one. The same limit applies to anything that sets a priority without going through this page, such as a routine created through the API.

Task ids

Every task of a team has a readable id, on its card, on its row in Needs you and the Inbox, at the top of its drawer and on its card in team chat. Tell an agent “look at MAR-12” and it can find it. Find matches an id too. The letters come from the team’s name. To use others, open the team’s settings from its chat header and change Task ids. You can do that until the team’s first task exists. After that the letters are fixed, and renaming the team changes nothing. Two teams cannot share letters: Clawboo offers the next free set, like MA2, and refuses a set another team uses. A task with no team has no readable id. Tasks from before this feature got their ids in the order they were made, the first time Clawboo started after the update.

Labels

Labels are a team’s own words for sorting its board. Set them with Labels in the drawer’s Properties: tick the ones you want, or type a new name. To rename or remove a label for the whole team, open the team’s settings and go to Labels. Removing one takes it off every task. Filter lists the labels on the tasks in view. Under All teams, two teams’ labels with the same name are one entry. Agents do not set labels.

Review what an agent built

The Files section shows what a task’s runs made, in one of two places:
  • A git worktree: a separate checkout of a repository, made for that task. That happens for runs started through the API with a repository path, such as an agent routine created through the API.
  • The task’s own folder, teams/<team id>/tasks/<task id> in the work folder (~/clawboo-work by default), for a task a Claude Code, Codex, Hermes or Clawboo Native agent runs without a worktree: work handed out in team chat, tasks you give from the board, and routines you create in the dashboard. The run is told to save the files it makes for the task there, and that the team’s shared folder is two levels up (../..).
For a task folder, the section appears once the folder exists and either holds a file or its task is In progress or In review, the same rule as the agent’s Computer tab. A finished task whose folder is empty shows no Files section. A task run by an OpenClaw agent has no task folder, since OpenClaw works in its Gateway’s own workspace. The agent’s own Computer tab under Details on its page lists the same worktrees and folders. See Worktrees and handoff. For a task with a worktree, the section shows:
  • the Branch (clawboo/task-<id>), the Worktree folder, and Changes: how many files changed, and the lines added and removed;
  • under System-of-record files, the files Clawboo keeps in the worktree to track the task, such as TASK.md and VERIFICATION.md, each folded;
  • the full Diff against where the branch started;
  • a live view of the worktree’s files, with change badges and what the agent touched last, when the task has an agent;
  • a Preview of the page the agent built.
For a task with its own folder, the section shows the Folder path, a live view of the folder’s files when the task has an agent, and a Preview of the page the agent built. The folder is not a git checkout, so there is no branch, change badges or diff. The Preview shows the index.html in the worktree or the task’s folder once the agent writes one, served as static files. Scripts do not run in the preview, so an app that needs JavaScript shows only its static shell. Open shows the page in a new tab, where its scripts stay off too. The preview checks for changes every 10 seconds while it is on screen. Clawboo does not merge the branch. Review it and merge it yourself.

When work is checked

Clawboo checks an agent’s work in two cases: a run in its own git worktree that changed files, and team chat work (a hand-off, or a task you give from the board) that changed the team’s folder on a team with a work check, by an agent that works in that folder, so not an OpenClaw agent (see which team chat work is checked). The check runs the verify command and, for a larger or risky change, or a task handed down from another task, a separate review by a model. Clawboo knows your project’s test command only if you set the team’s work check. Without one, a worktree’s check fails until the VERIFY_CMD line in its init.sh names one, and team chat work is not checked. Agent routines you create in the dashboard are not checked. A task with no check result reaches Done normally. While a check runs, the card shows Verifying. In team chat a check waits while a teammate is still working in the team folder, or another task’s check is running, and the card shows Waiting to check until then, for 15 minutes at most. A comment on the task says who it is waiting for. A pass lands in Done, and a failed check sends the work back to the agent for another attempt. When the attempts run out, or the work passes with debt, the task goes to Needs you. It shows Needs review if its result cannot pass, or Blocked if it passed with debt. Retry runs the task again and clears the old result. See Verification.

Decide on a plan

To decide before an agent splits up work, open the team’s settings and turn on Ask me before splitting work, under Plans. It is off at first. It covers a plan, a list of tasks an agent proposes, and two or more <delegate> tags in one reply. A hand-off an agent makes by tool call, or one tag alone, still goes straight through. With it on, the work shows in Needs you as Waiting for your answer, with an alert if you have them on, and lists each step and who it goes to:
  1. Read the steps. Each box holds the whole of what the agent will be told. Open the card and pick Plan for the document, if the agent wrote one.
  2. Change a step’s words, remove a step, or add one with Add a task. What is in the box when you accept is what runs, and nothing you took out reaches the agent. A step you add goes to the agent that proposed the plan.
  3. Press Accept. The steps go on the board in that order, and the first starts. Tasks from several <delegate> tags all start at once. Or press Turn down, and nothing is created.
The box above the buttons is for anything you want the agent to read. Your note comes first in what it reads. Say why when you turn a plan down. The agent always hears your answer. A plan on the agent’s own task starts that task again. A plan on a card of its own closes the card, Done or Cancelled, with no run on it, and the agent gets a task update in its chat, so its reply shows there. Accept refuses a plan of more than 25 steps, or one that does not fit under its task, and leaves it open for you to shorten. Accepting twice creates nothing the second time. If an agent sends the same steps again within 48 hours of your answer, nothing new is created, and it is told you already decided. To run them again, create the tasks yourself. If a different plan arrives while one waits, it takes that one’s place. The card says so, and the old plan stays on the Plan tab. Stop closes a waiting plan, and nothing starts: a task with work of its own goes back as Stopped, and a card that held only the plan is cancelled. Moving the card closes it too, and then what happens depends on where it goes. Cancelled starts nothing. To do starts the agent again within seconds, without the plan’s steps. The revisions stay on the Plan tab.

Routine runs

In Today, Week and Month, the upcoming runs of your routines appear in To do on the days they will run. Kanban has no days, so it shows no runs. A run is not a task yet, so it is drawn as a dashed strip with the routine’s name and time, not as a card. The next run on screen is drawn solid. A routine that runs several times a day shows once that day, with the number of runs. Click a run to see the routine’s schedule in plain words, where it goes, its next runs, and what happens when it runs. Run now starts it at once, and Open routine opens it to edit, pause or delete it. When an agent routine runs, it becomes a task card on that day. A team routine posts to the team’s General chat, and if its turn hands out work, that run shows as one request card with the work under it. Only routines that will run show runs. A paused routine, one halted after a failed run, and a one-time routine that already ran have none, and neither do the OpenClaw Gateway’s own scheduled jobs. Routine runs under Display shows or hides the runs, and its note says how many are coming up on screen. Times are in your local time, and when routines run in another time zone (see the time zone), the schedule names that zone.

Views and the calendar

Pick a view from the view menu at the right of the toolbar, which names the view you are on, or press its key: In a calendar view, a card sits on one day:
  • Open work sits on the day it was added, and stays on that row as it moves from Backlog to To do to In progress.
  • Finished work sits on the day it finished.
  • Open work from before the range on screen is gathered in an Earlier row at the top, so nothing in play is hidden. It opens by itself when it holds running or waiting work.
The board remembers your view and your Display choices in this browser. The filter is not remembered.
  • Lanes and cards are neutral. Each column’s title carries its status mark in the column’s color, and Needs you is amber.
  • Today’s date sits in a red circle. Weekends and the Earlier row are shaded.
  • Pick a date in the day column to light its whole row. Pick it again, or press Escape, to put it out.
  • A day with nothing on it folds into a thin line, and empty days in a row share one line. Click the line to open those days. Today never folds.
  • A cell shows three cards (two in Month view), then +N more, which opens the rest in place. Today and Kanban show every card.
  • A card an agent just added or moved fades in, so you can see what changed.
  • A move you make shows one message saying what happened. When the card went to a day the board is not showing, the message has a Show button that takes you there.
  • In Week and Month, the Today button goes to the current week or month and brings today’s row into view. While today is out of sight, a small arrow on the button points the way.
  • The arrows beside it step one week or month back or forward.
  • Click the range title, for example “Oct 25 to 31, 2026”, to pick a date. A dot marks each day that holds a task. In Today view, picking a date opens that date’s week.
With the board focused, these keys work. They do nothing while you type or while a dialog or the task drawer is open.Cmd+K (Ctrl+K on Windows and Linux) opens Find from anywhere on the board, even while you type in a field, but not while a dialog is open. In the task drawer, J and K step to the next and previous task. Every shortcut is listed in Keyboard shortcuts.
The search button in the toolbar, / or Cmd+K opens Find. Type part of a task’s title, the name of its agent, words from its details, or the start of its id. Routines match by name, except on Kanban. In a calendar view, results are grouped by where they sit against the range on screen, for example In this week, Before this week and After this week, then Routines.
  • Enter shows the task: the board moves to its day and highlights the card.
  • Shift+Enter opens the task’s drawer.
  • Enter on a routine opens the routine.
  • Escape closes Find.
Come back to the board after being away, and a chip beside the team filter says what changed meanwhile, for example “Since 2:10 PM: 3 done, 2 started, 1 new”. It shows only when something changed. Cards that changed carry a small dot until you look at them. Show brings the oldest change you have not seen into view, and Mark seen clears the chip and every dot. Changes that sent work to Needs you are counted but not dotted, because Needs you lists them already.This chip is kept in the browser, and compares where cards sit now with where they sat when this browser last looked, so another browser starts with no chip. What you have read is kept on the server and shown in the Inbox, so a task you open in one browser stops counting in this one too. Mark seen marks the cards the board is showing as read there as well. A card a filter or the date range hides stays unread in the Inbox.

Tasks in team chat

The same tasks appear in the team chat they came from: as cards in the conversation, and in the chat’s Tasks card. A request shows as one card in the conversation, with each sub-task’s own card inside it, and in the Tasks card its sub-tasks sit right under it. General shows the tasks handed out in General, and each room shows only its own. The expand icon on a chat card, and Open on Board in the Tasks card, open the task here with its drawer open. See Team chat. A task handed off from Boo Zero’s own chat belongs to the team’s General, so it shows there as well as in Boo Zero’s chat, and its result goes back to Boo Zero’s chat. The message it came from is a request with its own main task, which closes after Boo Zero’s reply in that chat.

Troubleshooting

If an agent’s run stops reporting, Clawboo ends it after a while and releases the task. The task then runs again by itself, or waits in Needs you as Timed out. The exact waits are in Limits and defaults. If the agent is working but slowly, reply on the task to steer it (see Steer a running task), or press Stop in its team chat.
That is expected for many tasks. Clawboo checks work only for a run in its own git worktree that changed files, and for team chat work that changed the team’s folder on a team with a work check. A task with no check result reaches Done normally. See When work is checked.
Only an agent’s run puts a task in progress, so the board does not offer that move. To start a task, move it to To do with an agent bound to it, or use Retry or Assign in Needs you.
Check the Filter button: a number on it means a filter is on, and Clear filters turns it off. The agents-working chip turns on Running now too. Also check the team filter beside the Board title, and turn on Cancelled column under Display to see cancelled work.
Routine runs show only in Today, Week and Month, never on Kanban. Check that Routine runs under Display is on and that the routine is active in Settings > Routines. A paused routine, one halted after a failed run, and a one-time routine that already ran show no runs.
The board shows “Couldn’t load the board.” when its first read fails. Click Retry. If it keeps failing, check that the Clawboo server is running; see Troubleshooting.
  • The board reads GET /api/board, every five seconds while the tab is visible. The drawer reads GET /api/board/:taskId, GET /api/board/:taskId/executions and GET /api/board/:taskId/workspace/detail. Its file view reads the GET /api/board/:taskId/workspace/* file routes for a worktree, and GET /api/board/:taskId/folder/tree and /folder/file for a task’s own folder. The preview is served from GET /api/board/:taskId/preview/, out of the worktree or the task’s folder.
  • Reopen is POST /api/board/:taskId/reopen, assigning a task to yourself is POST /api/board/:taskId/assign-person, and answering a question is POST /api/board/questions/:questionId/answer. Each answers only a request the board’s own page sent. That check is a speed bump on a local install, because an agent running as you can send the same headers. Behind a sign-in proxy in required mode, every request also needs a verified person. See Security.
  • New task is POST /api/board with an assigneeAgentId, or assignToMe for “You”. It reads each agent’s role from GET /api/teams/member-roles. Retry, Assign and replies are POST /api/board/:taskId/retry, /assign and /comments; the reply’s answer carries a delivery field that says where it went. A status change is PATCH /api/board/:taskId, and a confirmed Complete anyway sends humanOverride, which is written to the audit log.
  • On a team chat run the team engine claims and moves the task itself, so the agent gets no claim or status tools there except block_task, ask_person and hand_back_task on its own task. It can also say how the task went with report_result, which moves nothing. An OpenClaw agent gets none at all, since its tools cannot tell one agent from another. Cancelling a task with update_task_status cancels the plan steps waiting on it, as Dismiss does.
  • Retry, Assign, and a reply that would start the task again, refuse a task still filed under a deleted chat room (room_archived) instead of saying it started; restarting Clawboo moves it to General. A task whose team was deleted is refused the same way (no_team), and nothing can run it.
  • A status change you make records its time on the task (personMovedAt). Until a run starts after that time, the agent’s update_task_status, block_task and unblock_task tools are refused. See the tasks tools.
  • The view and the Display choices are stored in this browser’s local storage under clawboo.board.calendar, and the agent you last gave a task to, per team, under clawboo.board.new-task-agents. Under a path prefix (CLAWBOO_BASE_PATH), each key starts with the prefix, such as /clawboo:clawboo.board.calendar.
  • GET /api/board/:taskId/workspace/detail answers { "ok": false, "reason": "no_workspace", "taskFolder": { "path": "...", "onDisk": false, "holdsFiles": false } } for a task with no checkout of its own, and a 404 only for a task that does not exist. taskFolder is the task’s own folder: onDisk turns true once a run has made it, and holdsFiles once anything is in it. The drawer shows Files when the folder is on disk and holds files, or while the task is in progress or in review. Its file view reads that folder directly, so an older task’s files show there even when the agent’s Computer tab leaves the task out.
  • Browser alerts add no polling. They follow the event stream the dashboard already keeps open (GET /api/obs/stream). When a run ends, a task moves or an approval opens while the tab is in the background, they read GET /api/board and GET /api/tools/approvals?status=pending once, a second after the first event, so a burst of events is one read and one alert. A read that fails is tried again after 5, 20 and 60 seconds, and a shell approval the Gateway delivered is still announced when the approval queue cannot be read. Your choice is stored in this browser’s local storage under clawboo.alerts.needsYou. The desktop app is detected by the window.clawbooDesktop bridge it gives the dashboard, and a click on one of its notifications reaches the dashboard through that bridge’s onOpenTarget (see Open the dashboard from a notification).
  • Full request and response shapes are in the Board API. How the board stores tasks and recovers stuck work is in Board internals.

Next steps

  • Team chat: give a team work and follow it beside the conversation.
  • Verification: when work is checked, and what to do with a result that cannot pass.
  • Worktrees and handoff: where an agent’s file changes go.
  • Routines: set up the recurring work that shows on the calendar.
  • Approvals: answer the requests that appear in Needs you.
  • The board: statuses, dependencies and recovery behind the cards.
Last modified on November 18, 2026