There are two kinds of tools wearing that sentence. Some conjure new apps in their own cloud. Some work inside the repos you already run. Red Wheelbarrow is the second kind — with one difference nobody else has: a PR can't exist until your gates have passed.
Cursor, Replit, Lovable, Bolt, v0. Brilliant at zero-to-demo — a human (or the tool's own cloud) owns everything after generation: review, testing, hosting, consequences.
Jira Rovo Dev, GitHub Copilot's cloud agent, Devin. Same shape as us — ticket in, PR out. The difference is what's guaranteed to be true when the PR appears.
Scored from each vendor's own public documentation as of July 2026. Every column header links to the full, sourced breakout.
| Red Wheelbarrow | Rovo Dev | Copilot | Devin | Cursor | Replit | Lovable | Bolt | v0 | |
|---|---|---|---|---|---|---|---|---|---|
| Works on your existing repos (brownfield) | ✓ | ✓ | ✓ | ✓ | ✓ | ± | — | ± | ± |
| Delivery contract: a PR into your repo | ✓ | ✓ | ✓ | ✓ | ± | — | — | — | ± |
| User-defined fail-closed gates — no green checks, no PR | ✓ | — | — | — | — | — | — | — | — |
| Independent AI reviewer with a veto, before the PR exists | ✓ | ± | ± | ± | ± | — | — | — | — |
| Recon & plan approval as a hard gate before code | ✓ | ± | ± | ± | — | — | ± | — | — |
| Bounded cost per task — converge or stop | ✓ | — | — | ± | — | — | — | — | — |
| Agent blast radius limited to a pull request | ✓ | ✓ | ✓ | ± | — | — | — | — | — |
| Your stack, your toolchain — not theirs | ✓ | ✓ | ✓ | ✓ | ✓ | ± | — | — | — |
| Sprint planning by chat + built-in ticket board | ✓ | ± | ± | — | — | ± | — | — | — |
Assessments reflect each vendor's public documentation and reporting as of July 2026 — the nuance behind every mark (and the sources) lives on the breakout pages. Examples: Rovo Dev and Copilot open draft PRs before checks pass and their reviewers are advisory; Devin caps spend per session but meters failed attempts; Lovable's docs state repos can only be exported, never imported. If a vendor ships something that changes a mark, tell us — we'll update it.
These three share our shape: ticket in, PR out. The breakouts compare the spine — gates, review, budgets, and what reaches your team.
Jira ticket → sandbox → tests → draft PR. The closest competitor.
Opens the draft PR whether or not checks pass; review is advisory comments after the fact. And it requires the Atlassian stack.
Full comparison → vs · GitHub / MicrosoftAssign an issue → agent works in an Actions sandbox → draft PR.
Fail-open by design — CI doesn't even run on agent PRs until a human approves it. Microsoft's own data: half of merged agent PRs needed human commits.
Full comparison → vs · CognitionAn autonomous engineer in a cloud VM that plans, codes, and opens PRs.
One generalist agent grading its own work, metered in ACUs — its documented failure mode is expensive persistence. Trust the agent, or trust the process.
Full comparison →Great at conjuring something new, fast. None of them ship gated changes into the codebase your business already runs — that's the job we do.
The best-selling AI code editor — a power tool for developers.
Quality depends entirely on who's driving. No fail-closed gates, advisory-only review, unbounded metered spend — and a pending SpaceX acquisition.
Full comparison → vs · ReplitPrompt-to-app in Replit's cloud, aimed at knowledge workers.
The agent publishes; nothing merges through gates. Home of the category's defining incident: a production database deleted mid–code freeze.
Full comparison → vs · LovablePrompt-to-full-stack-app for non-technical founders.
Can't import an existing repo at all — export only. Self-verified output whose showcase apps were found leaking data at 10% rates in 2025.
Full comparison → vs · StackBlitzIn-browser prompt-to-app on WebContainers. Instant previews.
The preview is the only test. JS-only, degrades past ~20 components, and users report half their tokens go to fixing the agent's own errors.
Full comparison → vs · VercelBest-in-class prompt-to-UI for Next.js, inside Vercel's ecosystem.
Gorgeous sketches, one stack, self-corrected output the prompter merges themselves. v0 for the sketch — Red Wheelbarrow for the ship.
Full comparison →The field moves fast. So do we.
Think we should cover a tool that isn't here yet? Tell us and we'll research it the same way — receipts included.
Suggest one →"What must be true before a human sees the change?" Our answer: your gates passed, an independent reviewer approved, and the budget held. Everyone else's answer is shorter.