YOUR EDITOR. A SECOND SET OF EYES.
A second opinion
on your code.
BuildTurn coordinates your existing Claude Code and Codex tools. One makes the change, the other reviews it. You decide what ships.
LOCAL CODING WORKFLOW
PLANTED-DEFECT TRIAL
A condensed reconstruction of a reviewed, deliberately seeded trial. Code excerpts are shortened; review text is paraphrased. This is a webpage demonstration of the CLI workflow, not a released VS Code extension.
WHY THE SECOND LOOK?
A passing check can
still miss the point.
In this trial, the code used the wrong field. The smoke tests passed. The verifier tried two contrasting inputs, reproduced the mistake, and sent it back.
One repair later, the change matched the task. That is one useful catch in a controlled test, not a promise that every bug gets found.
Development notes ↗BEFORE YOU
GET STARTED.
Does BuildTurn use its own AI model?
No. BuildTurn uses your installed Claude Code and Codex tools, with your own accounts. It coordinates implementation, review and repairs. We haven't trained or fine-tuned a separate model.
What does BuildTurn add?
You can use both tools separately. BuildTurn handles the handoff, ties the review to an exact Git checkpoint, and sends blocking findings back for repair within the configured limits. You can inspect the changes, checks and review evidence together.
Can I choose who writes and who reviews?
Yes. Claude Code can implement while Codex reviews, or you can reverse the roles. Live runs require both tools to be installed and available through your own provider accounts.
How does account access work?
You explicitly allow BuildTurn to use each installed tool. Sign-in happens through the provider's own flow. Finding an installed tool does not grant permission or prove that you are signed in. Provider limits and billing still apply; BuildTurn does not include model access or guarantee subscription-only usage.
Does my code stay on my computer?
BuildTurn coordinates the run on your computer, but Claude Code and Codex communicate with their providers. Task prompts and relevant code may be sent through those tools under your account settings and the providers' policies. This is not an offline AI workflow.
Does it change my working checkout?
Runs use a separate Git worktree. You inspect the reviewed checkpoint before deciding what to integrate into your original checkout. Start beta testing in a disposable repository.
Does using two assistants produce better code?
We have recorded examples where a reviewer caught a defect, but we haven't established an overall advantage over either tool alone. A second review also uses more time and provider allowance. Our planned comparison will measure those trade-offs; scored runs have not started.
What does a finished run guarantee?
It means the configured completion gates passed for the recorded checkpoint. It is not automatic approval and does not guarantee that every defect was found. Read the review and check the changes before integrating them.
Is this a VS Code extension, and who can try it?
BuildTurn is a separate desktop app in private beta for Windows. The editor-style demonstration on this website is a reconstruction, not a released extension. Request beta access using the form below; invitations are sent manually and signing up does not guarantee immediate access.
TAKE THE
NEXT TURN.
Help test BuildTurn on real coding tasks. Tell us what you work on and where a second review would help.
The private beta is for Windows. Other platforms are welcome to register interest.