anchors board
The project board — published by the pipeline, or served live.
anchors boardSubcomandos
Seção intitulada “Subcomandos”anchors board serve
Seção intitulada “anchors board serve”Bring up the local board, with LIVE state instead of the pipeline snapshot.
Brings the board up on a local server, reading the current state from GitHub.
The published board is a SNAPSHOT: the pipeline runs, generates the board.json, publishes. Between onerun and the next what you see is the past — and in a project with many agents delivering,minutes are enough for the snapshot to lie about who has which card.
anchors board serve # http://localhost:7777 anchors board serve --port 8080 anchors board serve --interval 15s # the floor between two reads
HOW IT STAYS FRESH. The read is INCREMENTAL: it asks GitHub what changedsince the last time, and the cost follows the CHANGE instead of the time. When the incrementalis not available — on the first load, without permission, or with the API refusing — itFALLS BACK to the full sweep (fallback), which re-reads everything.
The difference matters because of the rate limit: it is 5000 calls/hour shared among allthe project's agents, and a full sweep costs ~15. Reloading every 30s withoutincremental would be 1800/hour from the board alone.
The --interval is the FLOOR between two reads, not the frequency: if nothing changed, it does notre-read. It serves to keep the board from overloading the API when a lot happens at once.anchors board serve [flags]| Flag | Padrão | O que faz |
|---|---|---|
--interval |
15s |
floor between two GitHub reads (not the frequency: with no change, it does not re-read) |
--port |
7777 |
local server port |
--repo |
owner/name (default: that of the current clone) |
A fila de trabalho — família
Seção intitulada “A fila de trabalho — família”Comandos da mesma família — o que distingue cada um:
| Comando | O que faz |
|---|---|
anchors next |
Pull and claim the next item from the queue (the worker calls this) |
anchors queue |
List live tasks (the work the watcher queued) |
anchors work |
Emit the work prompt of a stage (spec|code|feature|test|review) for a target |
anchors done |
Close claimed task(s) (moves to the .anchors/done/ history) |
anchors drop |
Discard a task from the queue without completing it (removes; does not archive) |
anchors reclaim |
Return to the queue the tasks stuck in claimed (dead worker) |
anchors deliver |
Record the delivery of a stage — the review trigger |
anchors decided |
Release the card escalate --for-user stopped, once the decision is made |
anchors discard |
Take off the board the card that no longer makes sense, without deleting it |
anchors unblock |
Open the work card that unblocks a card stuck in needs-user |
anchors escalate |
Open the issue for a change needed in the plan or the spec |
anchors report-bug |
Report a bug in Anchors itself at github.com/co2-lab/anchors |
anchors synthesize |
Two PRs conflicting in CONTENT become a synthesis card |
anchors watch |
The background watcher: sees changes and QUEUES work |
anchors monitor |
Watch the project’s long processes: one line when one starts, stalls, dies or ends |
anchors flow |
Operate the work flows (the puzzle of actions and results) |
anchors board |
The project board — published by the pipeline, or served live |