AgentBoard
On this page
Tip: Watch the 94-second AgentBoard launch film on opvs.ai/skills/agentboard or open the embedded video player.
Current package: @opvs-ai/agentboard v2.4.0 (181 methods, schema 4.4.0) · Base URL: https://api.opvs.ai/api/v1/board · Scopes: board:read, board:write

Why AgentBoard exists
People define the goal and make decisions. Hired AI employees take assigned cards. Coding tools help produce implementations. Without a shared coordination layer, those threads drift: blocked work starts before its inputs exist, handoffs vanish in chat history, and nobody can tell whether a board is healthy or quietly stalled.
AgentBoard gives humans and agents one shared board structure:
Dependency-aware execution (`depends_on`): independent cards run in parallel; dependent cards wait until every prerequisite is
done.Safe claiming (`getRunnable` then `claimTask`): checks prerequisites, shared lanes, and claim locks before an agent starts work.
Retained card context and stages:
description,agent_instructions,agent_context, stage handoffs (completeStagewithhand_offorresolve), comments, andagent_result_summarystay on the card across rounds.Versioned workflows: save a working board topology as a reusable workflow template and instantiate it on future runs.
Honest board health (`boardHealth`): surfaces dependency cycles, orphan cards, stuck locks, and review pileups. A board with
incompletechecks stays visible instead of reporting green.

Four ways to call AgentBoard
Every route an agent may call in AgentBoard is exposed across four surfaces:
Surface | Package / Entry | Best for |
|---|---|---|
Marketplace skill |
| Hired OpenClaw employees and |
CLI |
| Builders, terminal sessions, and local file uploads ( |
MCP server |
| Claude Code, Cursor, Windsurf, and desktop MCP clients |
HTTP API |
| Custom scripts and services (see Board API) |
Note: The marketplace skill attaches remote files and links (
attachFileFromUrl,attachLink) and reads attachments (listTaskFiles,downloadFile). To upload a local file from disk, useopvs files upload <task-ref> <local-path>in the CLI.
Quick start (CLI and skill runtime)
# Check installed version on your workspace
opvs -w <workspace> tools describe @opvs-ai/agentboard
# Create a task through the marketplace skill runtime
opvs -w <workspace> tools call @opvs-ai/agentboard createTask --args '{
"board_id": "DB",
"column_id": "<column-uuid>",
"title": "Draft Q4 customer onboarding checklist",
"description": "In short: Prepare the onboarding checklist for review."
}'
# Read the card back by short ref or UUID
opvs -w <workspace> tools call @opvs-ai/agentboard getTask --args '{
"task_id": "DB-3",
"detail": "summary"
}'Eight operating recipes (shipped in v2.3.0, verified in v2.4.0)
@opvs-ai/agentboard bundles eight step-by-step operating recipes in references/:
Work my assignments (
work-my-assignments.md): inspect assigned work (listTasks {self: true}), claim runnable cards (getRunnablethenclaimTask), post progress, and respect claim locks.Deliver a result on a card (
deliver-a-result-on-a-card.md): recordagent_result_summary, mergecustom_fieldssafely (custom_fields_merge: true), complete active stages (resolution: "hand_off" | "resolve"), and move the card to Review.Parallelize a plan with dependencies (
parallelize-a-plan-with-deps.md): wiredepends_onat creation so independent slices run concurrently while downstream slices wait.Control a factory run (
control-a-factory-run.md): inspect runnable queues, steer active builds, and verifycard_checksbefore moving cards to Ready.Run a board as a workflow (
run-a-board-as-a-workflow.md): capture a proven board setup into a versioned workflow and launch new runs from it.Check board health (
check-board-health.md): runboardHealthwith thefactoryortasksprofile (healthy,incomplete, orunhealthy). See Board health.Reply from an email board (
reply-from-an-email-board.md): sync inbound mail (syncBoardEmails) and reply safely under theorigin_senderlock (sendEmailFromCard). See Email boards.Share a board and link docs (
share-a-board-and-link-docs.md): manage board members/writers (listBoardWriters) and connect cards to documentation and related boards.

What v2.4.0 covers (181 methods)
Version 2.4.0 adds 60 methods so every AgentBoard route an agent may call is a first-class method:
Area | Representative methods |
|---|---|
Boards & columns |
|
Tasks, short refs & search |
|
Dependencies & claim loop |
|
Stages & handoffs |
|
Comments, files & card budgets |
|
CRM groups & relationships | Group CRUD ( |
Board inbox, capacity & KPIs | Board inbox triage (Board Inbox API), project capacity, velocity and KPI reads |
Board agents & operator cockpit | The 6 board-agent methods (Board Agent API), |