anchors next
Pull and claim the next item from the queue (the worker calls this).
ATOMICALLY claims the next pending task and prints it. Called by theworker (ideally a background subagent; or, if your AI client has no background,a dedicated blocking session — never the main conversation).
The claim is atomic: two workers in different terminals NEVER take the same task,so you can run 'anchors next' in parallel in several sessions.
When you FINISH the step (code written, check passed), close it with 'anchors done <id>'.If the queue is empty, it prints that and exits with code 0.
In github mode the queue is the board: 'next' asks the claim pipeline and WAITS(up to 3 minutes) for the card it hands out. It never dispatches a second claimwhile one of yours is still pending — re-running it waits on that same claim.
NOTIFICATIONS: whatever is in 'notifications.md' at the repository root is printedon top, before the card, on every call — it is how whoever runs the project tellsevery agent something. In github mode it is read from the integration branch onthe platform (not your checkout); HTML comments in it are not printed. Read it andact on it before the card.anchors next [flags]| Flag | Default | What it does |
|---|---|---|
--root |
. |
project root |
--worker |
worker identifier (default: pid@host) |
The work queue — family
Section titled “The work queue — family”Commands of the same family — what tells each apart:
| Command | What it does |
|---|---|
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 |