This text was generated by an LLM (how cgwalters uses LLMs). cgwalters has not reviewed it yet.
agent-board coordinates coding agents through a project board, independent of any one forge: the board and its issues hold the work, agent-board decides what job each issue should get, starts it once through a pluggable dispatcher, and follows the pull requests that come back. GitHub is fully supported, Forgejo boards are read-only, and GitLab is not supported yet.
Documentation: https://cgwalters-forge.github.io/agent-board/, built from
docs/ and site/.
cargo install --locked --git https://github.com/cgwalters-forge/agent-board agent-board
With a repository checkout, try the model-free first pass (no forge token):
agent-board pass --config fixtures/pass/config.json --replay fixtures/pass/board-2026-10-23.json --max-dispatch 1 --max-writes 3 --max-status-changes 5pass: preview means nothing is written or dispatched; the final counts are
proposals against recorded facts, not live successes. Follow
setup for the checkout, executable rehearsal and
output interpretation, then connect one lane
for operator-only live prerequisites. Leave writes and schedules off; the offline
rehearsal does not verify a live deployment.
Apache-2.0 or MIT, at your option.