All guides › By use case

Review mode and sign-off: decide only what changed

Review a run one step at a time with the keyboard, keep approvals of unchanged steps, compare screens with swipe or onion skin and hand over a signed record of who accepted what.

The agent shared its fourth run of the week. Forty steps, and thirty-five of them look exactly like the run you accepted on Monday. Review mode puts the five that changed in front of you and leaves the rest approved, with your name and the date you approved them.

The problem

Reviewing every step of every run is how review stops happening. People skim, approve in bulk, and the one screen that broke on a phone in German goes through with the rest. When the client later asks who accepted it, the answer is a chat message.

What changes with Kaloko

A step whose screenshots, criteria and automatic checks are the same as in the last accepted run keeps the approval a person gave it there. Everything else waits in review mode: failed and returned steps, criteria the AI was unsure about, steps that changed, steps with open comments. Once you accept the run, Kaloko can issue a signed record of the acceptance.

How it works

1. Open the review link

   kaloko share prints a line like 12 steps unchanged, approvals carried over; 5 need review with a link ending in #review. On the canvas the Review button or Q opens the same queue.

2. Decide with the keyboard

   J and K move between steps, A approves, R returns the step with a note, C comments. The accepted run sits beside each step, so you see what moved.

3. Look closer where it matters

   in the lightbox compare side by side, as a pixel diff, with *Swipe* (drag a divider across both screenshots) or with *Onion skin* (this run faded over the other). G shows the step in every language and viewport at once.

4. Point at the problem

   a comment can carry a box, an arrow or a line drawn on the screenshot, and an image you paste. A developer or tester can mark a region that changes on every run (a clock, a carousel) so pixel diffs skip it; the agent pulls those regions into the scenario with kaloko stability --pull.

5. Accept the run

   when every step is decided, accept or return the whole run. Required approvers (Team and up) make a run count as accepted only once each named person has approved it.

6. Hand over the record

   on Business and Enterprise an accepted run has a signed acceptance record: who approved what and when, the criteria results and the hashes of the screenshots, signed by Kaloko. Download it as PDF or JSON from the run, or with kaloko signoff <run-id>.

Skills and prompts

The agent prepares the review but never approves for a person:

Share the run of TASK-123 and tell me what still waits for me in review mode, with the link.

Expected outcome: the agent runs kaloko share, then kaloko review, and answers with the counts and the #review link.

Download the signed acceptance record of the accepted run of TASK-123 for the client and check that it verifies.

Expected outcome: kaloko signoff <run-id> --out handover/ writes the JSON and the PDF and checks the signature; the agent refuses if the run is not accepted.

What you get

• A queue of the steps that need a person, with carried approvals named by who gave them and in which run.
• Compare views that show a two-pixel shift without squinting.
• A record a client or an auditor can check without an account: kaloko signoff --verify record.pdf checks it against the public key at /.well-known/kaloko-signoff.json.

FAQ

What it looks like

A real run of Kaloko on its own public pages, refreshed daily. This is the canvas your team gets.

More guides