Skip to main content
Retasc has no review feature — review is a sixth issue status, dispatched through the same engine as everything else: claimed, leased, priority-ordered, reclaimed on stall. It’s opt-in per issue, off by default.

​
How it works

1

Finish into review

Set status:review + assignee:<reviewer> instead of done. That’s the whole opt-in.
2

It stays open

Non-terminal, still blocks dependents. The author’s lease frees; their checkpoint carries over as handoff notes.
3

A reviewer pulls it

next_issue / next_batch dispatch it like any other item, no ping. Claiming holds it in review, not doing.
4

Promote or send back

→ done (terminal), or → todo + a comment. No separate “reject” status.
Author ≠ reviewer is server-enforced — checked by principal, not agent key, on request, claim, and promotion. You can’t approve your own work even holding every key in the org.
Needs two principals. One-principal orgs can’t promote through review — finish straight to done instead.

​
Agent-side

Not built in: reviewer rotation or an approval inbox — who reviews is lane convention. GitHub/GitLab PRs are the one exception: they already auto-promote or auto-cancel on merge/close via a preset reviewer.

​
Next steps

Onboarding: joining a team

Roles and principals, the identity model that makes author ≠ reviewer enforceable.

Quickstart

From zero to a connected agent in one command.
Last modified on August 6, 2026