AgentBoard

AgentBoard is a CLI for collecting work from task trackers and running an action for each matching item.

Define a Workspace that selects only the work you care about—for example, open GitHub Issues assigned to you with a ready-for-agent label. AgentBoard stores local copies, then runs the commands you configured. That command can launch a coding agent, create a worktree, send a notification, or do anything else available in your shell.

AgentBoard provides the queue and action pipeline. It does not include an agent runtime.

Sources -> local Store -> configured Actions

Install

AgentBoard publishes platform archives in component releases named agentboard-v<VERSION>.

ubi

Install a pinned release and select the agentboard executable from its archive:

ubi --project zenobi-us/agentboard \
  --tag agentboard-v0.1.0-next.53.1 \
  --exe agentboard

See ubi installation if ubi is not installed.

mise

Add the GitHub backend to mise.toml. The version prefix prevents latest from selecting releases for other components in this repository.

[tools]
"github:zenobi-us/agentboard" = { version = "latest", version_prefix = "agentboard-v" }

Then install it:

mise install

GitHub Issues quickstart

Authenticate GitHub CLI first. AgentBoard uses it as a credential helper:

gh auth login
agentboard workspace init work
agentboard workspace edit work # opens $EDITOR

Configure the Workspace:

[[sources]]
id = "github-assigned"

[sources.source]
kind = "github"
mode = "issue"
query = "repo:OWNER/REPO is:open assignee:@me label:ready-for-agent"
limit = 50
status_map = { ready-for-agent = "ready" }

[sources.source.credentials]
helper = "gh auth token"

[[sources.actions]]
uses = "agentboard/run-cmd"

[sources.actions.with]
cmd = "echo 'launch your agent for {{ item.url }}'"

Replace OWNER/REPO with the repository to watch. The example Action is deliberately harmless: replace the echo command with your agent launcher when the dry run shows the expected Issues. AgentBoard runs that command through sh -c for each matching Item.

agentboard doctor work
agentboard run work --dry-run
agentboard watch work --interval 60s

A dry run collects and renders pending Actions without executing them or writing to the Store. watch repeats the Run until you stop it with Ctrl-C.

How AgentBoard fits together

• Workspace — TOML file containing Sources and their Actions.
• Source — GitHub Issues, Jira Cloud, or QMD-backed markdown selected by a query.
• Item — normalized local copy of one task-like record, including its raw source payload.
• Store — local append-only JSONL history of Item observations and Action attempts.
• Action — configured side effect, currently a shell command or Git worktree creation.
• Run — one pass that collects Items, updates the Store, and executes pending Actions.
• Watch — repeated Runs for one Workspace.

The upstream tracker remains the source of truth. Successful Actions are recorded locally and skipped on later Runs unless their rendered inputs change.

Documentation

• CLI commands
• Workspaces and schema
• Sources, including GitHub Issues, Jira Cloud, and QMD
• Actions, including run command and create worktree
• Store layout and retry state
• Contributing and development setup