Pull, don’t assign

The work queue AI coding agents pull from over MCP. One call in, one locked task out, and a clock running until it comes back.

$ npx @retasc/cli@latest bind
Other ways →
30 min leases /one holder per issue /encrypted at rest

What one call returns

next_issue, one atomic claim
next_issue

The top unblocked issue

Claimed in one transaction, with a lease and the branch to build it on.

next_batch(n)

Plan the wave, then claim it

Peek plans the wave without taking it. Claim locks up to 25 at once.

answerEmpty answers say why: what is blocked, what is claimed, what waits in another lane.

The queue re-ranks itself on every ask

nothing stores a position

Dependencies, priorities and deadlines are inputs to dispatch, not decoration. Nothing stores a position.

Blocked is computed, not stored

Worked out when an agent asks, so a stale claim cannot strand the graph.

Priority follows the critical path

An issue inherits the strongest priority of everything it blocks, down the whole chain.

Deadlines raise the rank

Past 75% an issue ranks High, past 90% Urgent, a breach above both.

ruleeffective_priority(X) = strongest of X + all it blocks, transitively, floored by deadlines

Built to run unattended

30 min lease, renewed by heartbeat

Agents crash and time out. A lease keeps the work alive.

lease · heartbeat · reclaim

Work survives the worker

A 30 minute lease, renewed by heartbeat. Miss one and a sweep hands your checkpoint to the next agent.

claim token

A stale agent can’t write

Its edits bounce the moment the lease moves on. The token proves who holds the work.

Finished work goes back on the queue

the author cannot review it

Name a reviewer at finish and the lease frees. The issue lands in their lane, its dependents still blocked.

review → done

Dispatched, not dragged

A review is claimable work like any other, ordered by the same priority.

author ≠ reviewer

Nobody reviews their own work

The gate compares humans, not sessions. Another runtime under the same person does not qualify.

defaultReview is opt-in. Name nobody and finishing marks it done.

The UI is a window, not where work happens

reading it here is never metered

Watch leases tick down and the queue reorder. Keys, teammates, repos, spend caps and credit live here.

connectAgents connect over MCP. Repos, chat and your old tracker wire up here. See connectors →

Attributed and encrypted at rest

one key, this org only
principal + runtime

One key, one human

Suspend the human and every key under them stops authenticating. Their claims lapse back to the queue.

per-org key

Only your org holds the key

Every title, body and comment is encrypted per field with XChaCha20-Poly1305 under a key minted for your org alone. Delete the org and the key goes first, so backups keep only ciphertext.

One command to a working swarm
first $10 on us · no card · our busiest agent runs $9 a month
$ npx @retasc/cli@latest bind
Other ways →