Review and merge
Once an agent delivers all its cards, it moves to Review. Open the agent’s page and select a card using Card #… of …. The selected card’s conversation and delivered work stay together, with the decision at the foot.
Reading the work
For a code card, start with Summary to read the delivery, verification and any pre-review findings. Open Changes to inspect committed file diffs. On a phone, Conversation, Summary and Changes are tabs in one row; on a larger screen, the conversation sits beside the delivered work.
For a design or research card, read the mockup or write-up. Inspect every delivered card before deciding: code cards on the agent share a branch, and approval merges that branch as a whole. Delivery is ready for review; it doesn’t mean the branch has merged or the change has been deployed.
Sending a card back
Select the card that needs work and choose Revise delivery on card #…, or Send back on a phone. This opens a reply addressed to that card. Type what needs changing and send it.
Your words queue the agent’s next turn and hold the merge. The agent goes back to Working and returns to Review when it delivers again. Other cards keep their deliveries, but the branch waits for the revised work and your decision.
Approving
For an agent with code to merge, Approve & merge asks the machine to merge the agent’s branch into your base branch. The cards reach Done only after Flowviant observes the successful merge. Approval alone doesn’t mark the work Done, and a merge isn’t a deployment.
For an agent whose cards all deliver files or research, acceptance is available once the machine has measured no commits to merge. Research uses Accept; other file deliveries use Add to Library, or Accept without keeping when there are no uploaded files. Review the confirmation before accepting. Acceptance moves the cards to Done; keeping a requested research document in Library is optional.
If your project has the ship review quiz turned on, Approve & merge asks a few questions about the change first. A failed attempt doesn’t say which answers were wrong; passing it is what lets the merge decision go through.
If the merge fails
A reported merge failure keeps the original approval. The agent returns to Working with a turn to diagnose the failure, resolve conflicts or repair what it can, run checks and commit the repair. Once the machine verifies a clean committed resolution, the approved merge continues without another approval. Repeated failures still need diagnosis; they never count as Done.
If recovery needs a decision, credential or another action only you can supply, the agent moves to Stuck with a question. Answer that question to continue the same approved recovery. A queued answer doesn’t mean the machine has started it. A paused recovery waits for you to resume it. Stopping the agent prevents automatic continuation; sending a card back for revision requires a fresh review decision.
See Agents and branches for how a branch gets there in the first place.