The ready checklist
When a run finishes, the ready checklist runs your project's own checks against the exact change that would land, and answers each one: passed, failed, or no answer. It ships Off; turn it to Report only on a throwaway project first to see what it would say without changing anything.
On this page
What it is
Most finished work is declared ready by the agent that built it. The ready checklist is the opposite idea: the end of a run works out the answer for itself, from the checks your project already has.
It only applies to a project whose work ends by being merged into its own main copy on this computer. A project whose work lands through the app's lander, or that finishes by opening a pull request, keeps its own ending, and this switch changes nothing there.
Nothing new is invented for the list. It is what your project already declares: one gate command if it has one, otherwise its test, lint, typecheck and build commands, plus any command steps of the Dev Pipeline your project runs whose files the change touches. Those declarations are read from your main copy's own commit, never from the branch being judged, so a branching agent cannot quietly change the rules it is about to be measured by.
Where to find it
In the Dev Pipeline panel: Setup → the AI code review card → Measure every finish before the branch lands. It offers three positions — Off, Report only and On — and it ships Off. A change takes effect on the next finish; there is nothing to restart.
The result appears at the end of a run, in the finish's own report.
How it behaves
The three positions. Off is exactly what happens today: the finish still takes the run's word that its checks passed. Report only does today's path first — the merge has already happened before anything is measured — and then prints what On would have done from your main copy as it stood before that merge — the exact refusal On would have given when it would have stopped before measuring (such as newer work on your main copy that the branch lacks), otherwise one line per check; it cannot refuse, hold or relabel anything. On ignores the word and measures for real: it stops unless the newer work from your main copy is already in the branch, runs the list against that one exact commit, and moves your main copy onto precisely the commit it measured — a fast-forward, never a new merge commit. It also stops if the branch or your main copy moves after the measurement.
Three answers, never two. Every check ends as passed, failed or no answer. A check that could not start, ran out of time, or was refused by the machine is no answer, and is reported as that rather than being folded into a pass or a failure. A failed check is named, and nothing is merged. A check with no answer also stops the finish with nothing merged; the way forward is to get that check answering and finish again, make a new commit and finish again, or set the switch back to Off to finish the way you did before.
A project that declares no test command still finishes — and says so out loud, labelling its finish not tested rather than letting it read like a tested one.
A change cannot lower its own bar. The list comes from your main copy, so editing the files that define the checks does not change the rules for the change being judged. When a change does touch those files, the finish names it on its last line so you can see it happened.
A switch that cannot be read counts as Off, except in a run that started with it On, which holds instead of sliding back to Off.
Trying it on a throwaway project first. Report only is the safe way to see the real thing:
- Make a throwaway project — a copy of a small project you do not mind changing, or a scratch repository with a test command and one tiny, harmless edit.
- Turn the switch to Report only in the Dev Pipeline panel's Setup tab.
- Run the Dev Pipeline on that small edit and let it reach its finish.
- Read the finish's report. Each line says what On would have passed, refused or held, on the real code, in the real order.
- If the list is what you expect, turn the switch to On for that project. If it shows something you did not expect — a missing check, a check that never answers — fix the project's own declarations first and try Report only again.
Related
It is the finish described at the end of Dev Pipeline, whose switch lives on the Dev Pipeline panel's Setup tab.
Last verified 2026-11-12