Stop merging code blind.

Review any PR in a connected GitHub repo. Aether runs it in a dev preview and can post screenshots from before and after the change. Turn on recording for a full replay.

Review a PR freeInspect the full public demo

One seeded failure. One unexpected finding. Every comment and second review public.

An Aether review of an acme-checkout pull request: run 1 completed at head ac1858e, a Changes requested verdict with 6 findings, and the traced overcharge, quoted 159.30 dollars but charged 177.00.
A real Aether review of a public acme-checkout pull request, captured from the app.

Transparent demo: Acme Checkout is a controlled demo repository. I intentionally seeded the checkout overcharge so the failure, fix, and second review would be reproducible. In the same review, Aether found another bug I did not intentionally add: the promo remained active after checkout and silently discounted later orders. PRs 13 through 16 were rehearsal runs while producing this demonstration.

Run the code. Keep the evidence.

When visual verification is enabled, Aether opens the dev preview and posts before-and-after screenshots or a browser recording with its verdict.

Inspect a real PR →
The Screenshots section of the review body: a before and after pair of the shop cart, base main with a 177.00 dollar total beside the reviewed head with the promo row and a 159.30 dollar total.
Before/after screenshots the reviewer captured: the cart on the base branch, then running at the reviewed commit.

Demo video the review agent recorded while driving the changed checkout flow in a real browser inside its review environment.

0:00 / 0:00

Demo video the reviewer recorded while driving the change in a real browser.

Project settings: the visual verification group with Post screenshots and Post demo video toggles, both on.
Visual verification is a project setting: post screenshots, post demo video, or neither.

The diff, in the order it matters.

Use it on PRs from Aether, Claude Code, Codex, or your team. The reviewer traces behavior across the repository, not just the diff.

Findings arrive grouped into a guide. Each section says what changed and why it matters, so you review consequences, not every line.

The Changes section of a review: a lines left pill, guide section one titled The discount math and the type that carries it with the reviewer prose, a files viewed pill, and a file card opening a unified diff with word level highlights.
The review guide ordering the diff, captured from a real review.

Comments are not the finish line.

When Aether wrote the code, the author agent fixes every finding and the reviewer checks the new commit. They repeat until the reviewer approves.

For outside pull requests, you still get the same independent review and dev preview, with visual evidence when enabled.

Author agent
Reads every finding, changes the implementation, and pushes a new commit.
Reviewer agent
Checks the new commit against the original failure and either approves or sends it back.
The Reviews stream of one pull request: a Changes requested verdict at head ac1858e with 6 findings, two replies, then an Approved verdict at head bc5bf5a with 0 findings and the reviewer probe output.
One pull request, reviewed twice: changes requested, a fix pushed, approved at the new commit.

A reviewer you can answer.

Every finding is a thread on the exact line. Answer it and the reviewer answers back. Resolve it, or hand the fix straight to an agent.

A review thread anchored inside the diff: the reviewer finding that the promo outlives the order, the author reply posted via Aether, and Resolve, Reply, and Hand to agent actions.
A review thread on the changed line: the finding, the reply, and the hand off.

Review the next PR before it ships.

Start with free credits. Bring any repository and any pull request.

Review a PR free