Atlantic runs Atlantic on its own repositories.
Atlantic runs Atlantic on its own repositories through the same GitHub App customers install. Here is what a run does on our code.
What a run does on our code.
- 01
Our repositories are connected, and Atlantic watches our backlog.
About 60 seconds after a ticket is filed, Atlantic starts. - 02
A run investigates, writes the fix, then boots our branch.
Three finders read the backlog, the support desk and the repository in parallel, each working blind. A judge links what they found, picks one problem and writes a thesis. Atlantic re-reads the repository at HEAD to confirm the problem still exists, then writes the patch on a branch. Atlantic boots the branch on a fresh, isolated preview machine and checks its health.
- 03
The pull request opens last, with the evidence.
A browser agent drives the change for up to 40 steps, recorded on video. A second model reviews the diff. Blockers go back through up to 2 fix cycles. 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.
