- name
- pikaboard
- description
- Interact with PikaBoard task management API. Use when creating, updating, listing, or managing tasks. Agent-first kanban for AI teams. Triggers on: tasks, kanban, board, todo, backlog, sprint.
- metadata
- openclaw
- emoji
- 📋
- requires
- bins
- ["node", "npm"]
- install
- kind
- git
- repo
- https://github.com/angelstreet/pikaboard
- branch
- main
- label
- Clone PikaBoard repository
- kind
- script
- cwd
- pikaboard/backend
- run
- npm install && npm run build
- label
- Install backend dependencies
- kind
- script
- cwd
- pikaboard/frontend
- run
- npm install && npm run build
- label
- Build frontend
- kind
- prompt
- message
- Create .env with DATABASE_PATH and PIKABOARD_TOKEN
- label
- Configure environment
PikaBoard
Agent-first task/kanban dashboard. PikaBoard is the source of truth for tasks.
Quick Start
After install, start the server:
cd pikaboard/backend && npm startAccess dashboard at http://localhost:3001
Configuration
Create backend/.env:
DATABASE_PATH=./pikaboard.db
PIKABOARD_TOKEN=your-secret-token
PORT=3001Add to your TOOLS.md:
## PikaBoard
- **API:** http://localhost:3001/api/
- **Token:** your-secret-tokenAgent runtime variables:
export PIKABOARD_API="http://localhost:3001/api"
export PIKABOARD_TOKEN="your-secret-token"
export AGENT_NAME="bulbi"Task Commands
Reference tasks by ID:
task 12or#12→ view taskmove #12 to done→ status changecreate task "Fix bug"→ new task
API Reference
See backend/API.md for full endpoint documentation (single canonical doc).
Common Operations
List tasks:
curl -H "Authorization: Bearer $PIKABOARD_TOKEN" "$PIKABOARD_API/tasks"Create task:
curl -X POST -H "Authorization: Bearer $PIKABOARD_TOKEN" \
-H "Content-Type: application/json" \
-d '{"name":"Fix bug","status":"inbox","priority":"high","tags":["bug","backend"]}' \
"$PIKABOARD_API/tasks"Update status:
curl -X PATCH -H "Authorization: Bearer $PIKABOARD_TOKEN" \
-H "Content-Type: application/json" \
-d '{"status":"done"}' \
"$PIKABOARD_API/tasks/123"Enums
| Field | Values |
|---|---|
| status | inbox, up_next, in_progress, testing, in_review, done, rejected |
| priority | low, medium, high, urgent |
Agent Onboarding (Simple Path)
Use the helper to map each agent to a board automatically:
cd pikaboard
MY_BOARD_ID="$(
./skills/pikaboard/scripts/setup-agent-board.sh | sed -n 's/^MY_BOARD_ID=//p' | tail -n1
)"
export MY_BOARD_IDWhat it does:
- Reads
PIKABOARD_API,PIKABOARD_TOKEN,AGENT_NAME - Finds board by
BOARD_NAME(default:AGENT_NAME) - Creates board if missing
- Prints
MY_BOARD_ID=<id> - Verifies
GET /api/tasks?board_id=<id>&status=up_next
Optional:
export BOARD_NAME="Bulbi"
export BOARD_ENV_FILE="$HOME/.openclaw/agents/bulbi/.pikaboard.env"
./skills/pikaboard/scripts/setup-agent-board.shMulti-Agent Setup
Each agent can have their own board. Use board_id parameter:
curl "$PIKABOARD_API/tasks?board_id=6" -H "Authorization: Bearer $PIKABOARD_TOKEN"Board assignments:
- Board 1: Pika (main)
- Board 2: Tortoise (personal)
- Board 3: Sala (work)
- Board 4: Evoli (VirtualPyTest)
- Board 5: Psykokwak (EZPlanning)
- Board 6: Bulbi (PikaBoard)
- Board 7: Mew (Ideas)
Validation Checklist
Run after setup:
# 1) API reachable
curl -s http://localhost:3001/health
# 2) Auth works
curl -s -H "Authorization: Bearer $PIKABOARD_TOKEN" "$PIKABOARD_API/boards"
# 3) Board mapping works
echo "$MY_BOARD_ID"
# 4) Agent can read own queue
curl -s -H "Authorization: Bearer $PIKABOARD_TOKEN" \
"$PIKABOARD_API/tasks?board_id=$MY_BOARD_ID&status=up_next"