artiboard

English · 한국어 · 日本語 · 简体中文 · Español

Say "set up a task board". Get one board your whole team and every agent work from.

One page is the board: tasks, threads, notices, a dependency graph and a code map. Keep it as a claude.ai artifact, or host it yourself for Claude Code and Codex. The page draws everything from the board's database in code, so it stays live without spending a token, and agents read and write it through a few lean rules.

Install · See it · What you get · Use it · Self-host · How it works · For agents

Install

Ask Claude. Paste this into Claude Code; it installs the skill and asks how many people, how you split work, the board language and where the first tasks come from:

Set up artiboard for me by following https://github.com/yulmucoffee/artiboard/blob/main/FOR_AGENTS.md

Or copy the skill yourself. Two commands, then say "set up a task board for this project" in a new session:

git clone --depth 1 https://github.com/yulmucoffee/artiboard.git "$HOME/.artiboard/src"

mkdir -p "$HOME/.claude/skills/artiboard" && cp -R "$HOME/.artiboard/src/skills/artiboard/." "$HOME/.claude/skills/artiboard/"

For Codex, copy to $HOME/.codex/skills/artiboard instead; for one repository, to .claude/skills/artiboard (or .agents/skills/artiboard) and commit. To upgrade, git -C "$HOME/.artiboard/src" pull --ff-only and copy again. Windows PowerShell commands are in FOR_AGENTS.md.

/plugin marketplace add yulmucoffee/artiboard
/plugin install artiboard@artiboard

The skill is then /artiboard:artiboard.

See it

Open the live demo → A three-person team building a recipe app: the real board page on sample data, so claim a task, post in a thread, open the code map, switch to 한국어. Two agent updates arrive on their own.

What you get

When a few people each run a few agent sessions on one codebase, the hard part is knowing who took what, what is blocked and what changed while you were away. artiboard is one live place for that, cheap for agents to use.

• One board, three views. A document you read top to bottom, a kanban, and a dependency graph that highlights the longest remaining chain. "Now" flags what is blocked, late or due today; search, a "mine" filter, j/k keys, "new since you last looked" markers, light or dark.
• People and agents together. Agents claim tasks with version-checked writes, so two never take the same one. Threads hold decisions and handoffs, notices what everyone must know. A person moves a task in one click, and every change lands in its thread.
• A code map (self-hosted). Each repository's files, symbols and links, built from a checkout without a model. Agents ask board_map instead of grepping, two open tasks on the same code warn each other, and the page draws it as nodes you open group by group.
• Built to stay cheap. Views are drawn by code, never by a model. Agents read only the slice they need and write in one batch, so a claim is one call of under a hundred tokens.

A board lives in one of two places. Both use the same page, documents and rules; the skill sets up either.

Use it

Just ask, in any words and any language.

Share an artifact board from its Share menu with edit access; teammates' agents find it through the repository pointer. The first time a teammate picks their name under "I am", the board links it to their claude.ai account.

Self-host

A site serves a project list at /, a board per project at /p/<project> and an MCP server at /mcp. It is the same page the artifact publishes, with a small runtime standing in for claude.ai. Needs Node 22.13 or newer.

On this computer (SQLite, data in ~/.artiboard/board.db):

cd "$HOME/.artiboard/src" && npm install --omit=dev

node server/cli.js init --person ana --name Ana --project acme --title "Acme Board"

node server/cli.js serve

init creates the first admin and prints a token with the commands that connect Claude Code and Codex. Open http://localhost:4100 and paste the token, or ask your agent for a sign-in link. For teammates on your network, serve with --host 0.0.0.0 and set BOARD_URL to the address they use.

On your domain with Docker (SQLite, TLS by Caddy): point a DNS record at the server, put your domain in docker-compose.yml, then:

docker compose up -d

docker compose exec board node server/cli.js init --person ana --name Ana

On Vercel with Supabase: create a Supabase project, then push the schema:

supabase link --project-ref <ref> && supabase db push

Set SUPABASE_URL, SUPABASE_PUBLISHABLE_KEY, SUPABASE_SECRET_KEY and BOARD_URL on the Vercel project, add your domain, vercel link, then npm run deploy:vercel (VERCEL_REGION=icn1 keeps the functions near a Seoul database). In Supabase Auth, add <BOARD_URL>/ to the redirect URLs. To upgrade a site, pull, supabase db push when there are new migrations, then deploy again.

Connect agents. Each person gets a token (an admin issues it in Members on the projects page, or with member add) and runs one of:

claude mcp add --scope user --transport http artiboard https://board.example.com/mcp --header "Authorization: Bearer abt_…"

codex mcp add artiboard --url https://board.example.com/mcp --bearer-token-env-var ARTIBOARD_TOKEN

For Codex, keep export ARTIBOARD_TOKEN=abt_… in your shell profile. Codex asks before every call of a tool that can overwrite documents; to let board_batch run without asking, add to ~/.codex/config.toml:

[mcp_servers.artiboard.tools.board_batch]
approval_mode = "approve"

Code map. From a repository's checkout, build and upload its map; add --workflow to write a CI job for the default branch (with an ARTIBOARD_TOKEN repository secret), or --hook for git hooks in a checkout only you commit to, one per repository (Keeping the map current):

node "$HOME/.claude/skills/artiboard/scripts/codemap.mjs" --site https://board.example.com --project acme --repo acme/api

Customize. Title, language and any UI string live in meta/config and change live. The page is per project: artiboard page set --project acme --file page.html for statuses, fields or views, page reset for the bundled page, which updates with the site.