Menu
Run beads.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Temporary inboxes for agent signup QA — create disposable addresses, wait for verification email, extract OTP or magic links. Use when automating signup, login, or email verification without parsing HTML manually.
Spin up isolated sandboxes ("boxes") for coding agents, run them in parallel, queue background runs with -i, and push commits safely through the host relay. Use when the user wants to run Claude Code / Codex / OpenCode in a sandbox, start more boxes, attach to a running box, or otherwise operate the `agentbox` CLI on their laptop.
Use when building an HTTP val — a web endpoint, API route, webhook receiver, or any val that responds to HTTP requests. Covers the handler signature, Hono usage, the endpoint URL, CORS behavior, redirects, and Val Town-specific limitations.
Use when creating a new val and choosing which starter to fork. Covers the catalog of official starter templates, which project shape each one fits, and when forking an existing val is the better starting point.
Switch coding-agent accounts on a usage/rate limit, routed by host and agent.
Use Agent Mail from Codex for file leases, notifications, inboxes, and conflict prevention.
| name | beads |
| description | Run beads. |
Graph-based issue tracker that survives conversation compaction.
br (beads_rust) replaces markdown task lists with a dependency-aware graph stored in git. bv adds graph-aware triage using PageRank and betweenness centrality. bd/Dolt is legacy unless a repository explicitly opts into it.
Key Distinction:
Decision Rule: If resuming in 2 weeks would be hard without persistent issues, use br.
br vs legacy bd: br is the current default. It never auto-commits; sync explicitly with br sync --flush-only, then commit the exported JSONL in the tracker repo or configured issue directory.
bv safety: NEVER run bare bv — it launches interactive TUI and blocks the terminal. Always use --robot-* flags.
br reads as authoritative. Use br show, br ready, and br list to inspect current tracker state. Do not treat JSONL exports as the primary decision source when live br data is available.br sync --flush-only.br close --reason text.
Name the touched files or explicit no-file evidence artifact, validation command(s), and parent
reconciliation outcome. Do not use generic closure reasons such as "done" or "implemented" for child beads.br ready returns a broad umbrella issue, do not implement directly against vague parent wording. First narrow the remaining gap into an execution-ready child issue, then land the child and reconcile the parent.br ... # mutate tracker state
br sync --flush-only # export DB -> JSONL
git add <issues-jsonl-or-dir>
git commit -m "Update issues" # if tracker changes are pending
git push # tracker remote, when configured
br init run once (humans do this, not agents)User says: $validate
What happens:
br show <id> to read issue metadataResult: Validation report includes issue context, no manual br lookups needed.
User says: $implement ag-xyz-123
What happens:
br show ag-xyz-123 to read issue bodybr close ag-xyz-123 after completionResult: Issue lifecycle managed automatically during implementation.
br is the current tracker CLI; the binary self-describes (br --help). Full command surface: references/BR_REFERENCE.md. Doctrine: sync is EXPLICIT, never automatic — br sync --flush-only (DB → JSONL, before git commit) / br sync --import-only (JSONL → DB, after git pull); session ends with pull-rebase → flush → commit the tracker JSONL/directory → push.
NEVER run bare bv. Always use --robot-* flags (--robot-triage, --robot-next, --robot-plan, --robot-insights, --robot-priority, --robot-alerts — selection guide in references/BV_TRIAGE.md).
Key metrics: PageRank = everything depends on this (fix first). Betweenness = bottleneck (blocks multiple paths). High both = critical bottleneck, drop everything.
Convert a markdown plan into fully dependency-wired beads:
br create for each issue, including full context in the description.gherkin
block or link to a filled intent issue. Mechanical chores may omit Gherkin
only when their acceptance criteria are fully command/file based.hexagon: boundary block from
docs/architecture/intent-to-loop-hexagon.md for substantial beads:
inbound port, bounded context, adapters, context packet, and done state.br dep add. Do not hand-edit JSONL or
database files.br dep cycles must be empty; run bv --robot-insights for graph
health; use bv --robot-next for the first bead. Never run bare bv.br sync --flush-only, then git add .beads/
and commit tracker changes when appropriate.Beads should be so detailed that a fresh agent can implement without consulting the original plan. Ready-to-implement beads have clear scope, explicit dependencies, BDD or mechanical acceptance, unit/e2e test expectations, detailed logging expectations, a named done state, and no dependency cycles.
Symptom → fix table (command not found, not-a-git-repo, init missing, ID prefix errors, bv hangs, dependency cycles, sync direction confusion): references/TROUBLESHOOTING.md. The two most common: a hung bv means a robot flag was omitted; br sync confusion means the direction (--flush-only vs --import-only) wasn't specified.