Agent Board
A shared work board where users and AI agents keep work moving together.
AI agents register work for themselves and users. Users update tasks and answer decisions.
日本語 · Usage guide · Contributing · GitHub repository
What is Agent Board?
When an agent works for a long time, you need to see what is moving, what is waiting, and what response will unblock it. Agent Board gives users and agents one shared, history-backed board.
flowchart LR
A["AI agent"] -- "agboard CLI + hooks" --> D[("Local shared folder")]
U["User"] -- "Agent Board UI" --> D
D -- "local server" --> B["Browser"]
Features
1. One board for people and AI agents. Track work in Todo, Doing, and Done, with Running and Pending states showing what the agent is doing. Answer questions directly on a task from your PC or phone, and keep decisions and status changes in its history.
2. Keep one agent session moving through tasks. Order tasks within an epic and let agboard progress return the work that can advance, together with the paths to its plans and tasks. An agent can explicitly listen for the next eligible task with agboard --project "My project" wait --until task --idle-timeout 300 --json; it processes one task, then listens again in the same session. Existing Todo tasks and idle AI tasks already in Doing are included, and the command exits normally after the chosen idle interval. Folder-based project selection and hooks give agents the right context. When every acceptance condition is verified, eligible AI tasks move to Done automatically; completed work stays read-only for agents.
3. Local Markdown for plans and results. Keep epic details in EPIC.md and tasks in TASK.md, with images alongside them. A task's plan and verification results live in the TASK.md body, with acceptance conditions and history in its frontmatter; task metadata such as its current status lives in task.json. Each history entry has just a timestamp (at) and content (reason). Agents record meaningful work progress automatically, and UI or CLI operations add their own history. You may supply a reason or let Agent Board generate one from the current state. Everything stays in your local data area, with no account or hosted service required.
See the usage guide for editing, attachments, archiving, and settings.
Install
Build from source with Git, Rust (Cargo with edition 2024 support), Node.js, and pnpm:
git clone https://github.com/FooQoo/agent-board.git
cd agent-board
pnpm --dir web install
pnpm --dir web build
cargo install --path . --locked --force
Keep ~/.cargo/bin (or $CARGO_HOME/bin) on your PATH. Build the web UI before installing: agboard embeds it. See the usage guide for updates and installation checks.
Get started
agboard project create "My project"
agboard serve --port 7420
Open http://127.0.0.1:7420/, select your project, and add a task. Most board commands use --project NAME; agboard progress and hooks resolve the project from the current folder unless explicitly overridden.
To check progress and answer questions from your phone, open Settings → Mobile connection and connect with your ngrok authtoken. The phone has to enter a 4-digit passcode that the board shows on your computer and that changes each time the connection starts; the full board stays on your computer. You can also start it with NGROK_AUTHTOKEN set and agboard serve --monitor ngrok, which prints the passcode. A 4-digit passcode is weaker than an account sign-in, so keep the address private; the mobile monitor guide explains the limits.
Documentation
