Original build with Codex on GPT-6 Astra (without zeroshot)
If you need to look at the code,
you’re behind.
A workflow engine for coding agents, built to enforce your team’s QA process. For engineering teams whose agents write code faster than anyone can review it.
today with zeroshot ana claude code + her prompt ──┐ ben codex + skills_v3_final ───┤ kai copilot + "be careful" ────┤ ana ben kai mo mo pi + whatever works ───────┤ └────┴──┬─┴────┘ │ │ │ │ 47 open PRs zeroshot │ │ │ │ you, 1:40am, LGTM × 47 every change tested + reviewed │ │ "tests pass," says the agent "tests pass," say your checks │ │ prod, PagerDuty at 3:12am prod, quiet at 3:12am token bill ↑↑↑, owner unknown you, asleep. one process, whole team
today ana claude code + her prompt ──┐ ben codex + skills_v3_final ───┤ kai copilot + "be careful" ────┤ mo pi + whatever works ───────┤ │ │ 47 open PRs │ │ you, 1:40am, LGTM × 47 │ "tests pass," says the agent │ prod, PagerDuty at 3:12am token bill ↑↑↑, owner unknown with zeroshot ana ben kai mo └────┴──┬─┴────┘ │ │ zeroshot │ │ every change tested + reviewed │ "tests pass," say your checks │ prod, quiet at 3:12am you, asleep. one process, whole team
Runs our own million-line codebase
Starred by engineers at
- Meta
- Shopify
- Uber
- Booking.com
- GitHub
- Cloudflare
- Atlassian
- JetBrains
Your CI starts at the PR. zeroshot starts at the issue.
Experiment: a small model with a review loop ↗
what the platform offers.
Harness and provider agnostic
A meta-harness over Claude Code, Codex, Copilot CLI or Pi, on Anthropic, OpenAI, OpenRouter, Bedrock or your own gateway. Every step in the graph can use a different one.
Enforced by code
No agent can skip a step. Nothing merges until your QA process passes.
We run the agents
Every run gets its own hosted environment, in parallel, off your engineers’ laptops.
Your team’s software factory
Your standards live in one graph, not in anyone’s skills folder or head. Every engineer’s issue runs through it. Shared team profiles ↗
Book a call with a founderOpen the platform
Free for one run at a time, then $100 a month for each extra run in parallel, not per seat. Models run on your own API keys.
Run it locally, the zeroshot engine is open source
npm install -g @the-open-engine-company/zeroshot
MIT licensed. Installation guide
go to bed :)
today
GitHub
47 pull requests are waiting for your review
Slack · ben in #ai-tools
can you send me the skill?
Slack · kai in #eng
you have to run the /test-performance command
Slack · mo in #ai-tools
why are you using fable for this?
Slack · ana in #reviews
LGTM pls, it's only 4,000 lines
Slack · kai in #ai-tools
there are 3 CLAUDE.md files and they disagree
Slack DM · ben
can you just approve my 14 PRs? standup is in 6h
Slack · ana in #eng
i have to go home now. i'll review it tomorrow
Email · finance
why is the AI bill bigger than payroll?
Slack · ben in #ai-tools
skills_v4_final_FINAL or skills_v4_final_actually?
GitHub · mo
merged #90: “tests pass on my machine”
Slack · kai in #eng
who the hell rewrote the system prompt?
Email · alerts
Checkout error rate: 94%
Slack · ben in #incidents
wtf, who merged #90??
Slack · mo in #incidents
i told my fucking agent to test it omg
Slack DM · ana
classic mo
Email · support
214 tickets: customers can't pay
Email · legal
a customer just said the word lawsuit
X
@yourapp down again?? switching vendors
Slack · kai in #incidents
fuck. checkout is down
PagerDuty
Critical: checkout is down
Slack · ana in #incidents
@channel is anyone awake??
Slack · ben in #incidents
who the fuck approved #90
Slack · mo in #incidents
it worked on staging tho
PagerDuty
Escalated: still not acknowledged
Slack · kai in #incidents
shit. the rollback failed too
Phone
PagerDuty is calling you
Email · ceo
call me. now.
Email · investor
saw the outage on X. quick call?
Calendar
9:00 AM · Postmortem: checkout outage
a recruiter: are you open to new roles?
0 PRs shipped1 PR shipped
with zeroshot
zeroshot
10 PRs merged · 3 sent back by checks and fixed
zeroshot
20 PRs merged · 6 sent back by checks and fixed
zeroshot
30 PRs merged · 9 sent back by checks and fixed
zeroshot queue
#412retried webhook books twiceana#418dark mode for settingskai#424remove dead feature flagsana#430trim the bundle sizekai#436export orders to S3anaworkerchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓
#413bump stripe-node to v18ben#419retry failed emailsmo#425speed up search queryben#431retry on 429 from Stripemo#437debounce the search boxbenworkerreview ✗repairchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓
#414add CSV exportkai#420paginate the orders APIana#426validate coupon codeskai#432sign outgoing webhooksana#438index orders by emailkaiworkerchecks ✓merged ✓workerchecks ✓merged ✓workere2e ✗repairchecks ✓merged ✓workerchecks ✓merged ✓workerreview ✗repairchecks ✓merged ✓
#415fix flaky login testmo#421fix timezone in invoicesben#427upgrade to node 24mo#433fix password reset linkben#439fix PDF receipt layoutmoworkerchecks ✓merged ✓workeracceptance ✗repairchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓
#416rate-limit the export APIana#422cache product imageskai#428add refund reasonsana#434check nightly backupskai#440archive old cartsanaworkere2e ✗repairchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓workeracceptance ✗repairchecks ✓merged ✓workere2e ✗repairchecks ✓merged ✓
#417audit log for refundsben#423SSO for adminsmo#429fix N+1 on dashboardben#435localize checkout errorsmo#441add a health checkbenworkerchecks ✓merged ✓workerreview ✗repairchecks ✓merged ✓workerreview ✗repairchecks ✓merged ✓workerchecks ✓merged ✓workerchecks ✓merged ✓
0 PRs shipped1 PR shipped2 PRs shipped3 PRs shipped4 PRs shipped5 PRs shipped6 PRs shipped7 PRs shipped8 PRs shipped9 PRs shipped10 PRs shipped11 PRs shipped12 PRs shipped13 PRs shipped14 PRs shipped15 PRs shipped16 PRs shipped17 PRs shipped18 PRs shipped19 PRs shipped20 PRs shipped21 PRs shipped22 PRs shipped23 PRs shipped24 PRs shipped25 PRs shipped26 PRs shipped27 PRs shipped28 PRs shipped29 PRs shipped30 PRs shipped
draw your own graph.
These are just some examples. Draw the graph that matches your QA process. Click a node to inspect its configuration.
see it work.
An arctic flight game, built with and without zeroshot.
With zeroshot
The zeroshot graph used for this experiment
Run start
Candidate 1
Candidate 2
Candidate 3The experiment: Claude Code on Opus 5.5 builds zeroshot’s landing page from its README three ways: on its own, with the reviewer’s standards in the prompt, and inside a custom graph with a design slop reviewer. To keep it a design test, that graph skips code review.
one session, no reviewer
plain Claude Code
Its final report
“I checked it with headless-Chrome screenshots at phone, tablet and desktop widths, in light and dark mode, and with reduced motion.”
one session, no reviewer
Its final report
“Checked in the rendered page: desktop, tablet and phone layouts in light and dark, with no horizontal scroll from 320 to 1920 px.”
What it shipped
- Eight screens. The reviewed page is five.
worker → design slop reviewer → repair
a custom graph for this experiment
Round 1: sent back
- Too long: the README poured into ten screens.
- It explains how zeroshot works five times.
- Every section looks the same, so nothing stands out.
- Apart from the demo, it could be any dev tool’s page.
- The install command, the one line people copy, breaks in two.
- On phones the staged demo run loses its “illustrative” label and passes as real.
Fix: make the rejection the page, with the run up top and the rest cut by half.
Round 2: accepted
Five screens instead of ten.
not just
for coding.
Autoresearch runs experiments through three independent judges.
Explore autoresearch
Watch a research run · 20 sec