The pull request opens last.

A run moves through investigation, thesis, patch, preview, QA and review, in that order. The pull request opens last, with the thesis, evidence, QA verdict and video, and reviewers are requested.

Book a live run

Try it on your repo

How it works

Investigation to pull request, seven stages.

Investigation and thesis decide what to fix. Patch, preview and QA build and test it. Review checks the diff. The pull request opens last.

01
Investigation
Three finders read the backlog, the support desk and the repository in parallel, each working blind.
3 finders, in parallel

02
Thesis
A judge links what they found, picks one problem and writes a thesis.
One problem, one thesis

The candidates log of an example run in the Atlantic app: the request that started the run, the check against work already in flight, and the candidate that was picked. — Example workspaceA run started from a session: the gate checks the request against work already in flight, and the candidate is picked.

03
Patch
Atlantic re-reads the repository at HEAD to confirm the problem still exists, then writes the patch on a branch. Every diff is checked against a 2,500 changed-line budget by default.
2,500 changed lines
04
Preview
Atlantic boots the branch on a fresh, isolated preview machine and checks its health. The preview machine is built from factory.deploy.yml.
Fresh, isolated machine

The browser agent's setup steps in an example run in the Atlantic app, each with a check mark. — Example workspace

05
QA
A browser agent drives the change for up to 40 steps, recorded on video.
Up to 40 steps

Example workspaceThe browser agent types a test name and an example address into the form it is testing.

06
Review
A second model reviews the diff. Blockers go back through up to 2 fix cycles.
Up to 2 fix cycles
07
Pull request
The pull request opens last, with the thesis, evidence, QA verdict and video, and reviewers are requested. Atlantic never pushes to your default branch. Auto-merge stays off unless you turn it on for repositories you name.
Opens last

The code step of an example run in the Atlantic app: a review note that blocks the change, and the files the run changed. — Example workspaceThe code step: a review note that blocks the change, above the files that changed.

The page of an example run in the Atlantic app, a run whose change touched seven files. — Example workspaceThe run you have just read, on its page in the app, with the files it changed.

Evidence and guardrails.

Every external call a run makes is logged, and every diff is checked against a budget.

01
Evidence
Every external call a run makes is logged with source, status and time. Each provider is marked live or mocked, and a production run refuses mocks.
Source, status, time
02
Guardrails
Every diff is checked against a 2,500 changed-line budget by default. The diff guardrail rejects binary changes. The diff guardrail includes a repository-mismatch check.
Default budget: 2,500 changed lines