One place for humans and agents to approve what changed
Baseline and changes side by side, comments pinned to the exact pixel, approve or reject with a keystroke. Every reviewer's verdict counts on its own, including the agent reviewing from the CLI, and the result lands on the pull request as a check.
Review diffs at full speed
The build page puts the baseline next to the changes and highlights what moved. Split or single view, an overlay you can tune, and a shortcut for every action, so you get through a build without touching the mouse.
PR #402 - Reduce image size
Find and inspect changes instantly
Split view or single view, a changes overlay in your own color and opacity, and a highlighter that flashes the changed regions. J and K jump from one change to the next, and zoom and pan stay in sync between the baseline and changes panes.
NinaFixed in 3f2a1c, matches the design.
AndrewNinaPrice tag is clipped on mobile.
Decide in one keystroke, keep the record
Y accepts a change, N rejects it, ↵ opens the review popover. Add a summary in Markdown, submit, and the review stays in the build's history: who decided what, and when. A progress chip such as 2 / 3 reviewed shows how far along you are.
Keyboard shortcuts
↑ ↓ move between snapshots, ← → show one side, S D H switch views, Y N decide. Press ? for the full list.
An overlay you can tune
Changed pixels are highlighted in red. Toggle the overlay with D and pick its color and opacity from the toolbar, so it stands out on any screenshot.
Reference a screenshot
From either pane, copy a direct link, copy an embed as Markdown for a PR description, or download the screenshot, its diff mask, or the composed changes.
Learn moreEvery reviewer's verdict counts
Request the people you need and track each verdict on its own; a new review never overwrites someone else's. One rejection blocks the build. Without one, a single approval passes it.
The logo shifted 4px right here. Intended?
@andrew can you confirm?
Good catch, pushing a fix now.
Comment on exactly what changed
Pin a comment to a point on a screenshot, or to a line range in a Markdown or JSON snapshot. Comments are Markdown with / commands and @mentions. Reply in threads, react with emoji, and resolve the thread once it's settled.
- Nina10:24 localApproved
- Andrewvia CLI · just nowRejected
- SSam17:24 localPending
Request reviewers, track each verdict
Each reviewer is Approved, Rejected, Commented, Pending, or Dismissed, and only their latest review counts. A review submitted from the CLI or the API is attributed to the token's user, so an agent's verdict appears under the person who ran it, beside the rest of the team.
Draft reviews
Comments gather into a pending review only you can see until you submit; then everyone is notified at once. Hold Alt to post a single comment immediately.
Real time, with presence
Comments, reactions, and decisions appear as they happen, with no refresh. Presence dots show who is on the build, and each user card shows their role and local time.
Learn moreOne digest, not a flood
Review notifications arrive as a single digest instead of one message per action. Subscribe or unsubscribe per build from the Activity section of the sidebar.
Learn moreThe verdict lands on your pull request
Argos reports each build as a commit status you can require in branch protection, keeps one comment on the pull request current, and tells the channel that needs to know.
Statuses post as argos, argos/<build-name>, or argos/summary when a commit has several builds. Require them in branch protection and a rejected build blocks the merge.
Learn moreEach build's status, an Inspect link, and a Details column such as 4 changed, 3 ignored, edited in place on every update. Deployments list their preview URLs too.
Learn moreWhen a build completes or is reviewed, if it matches your conditions, then post in Slack, Microsoft Teams, or Discord. Rules are per project, so nobody has to watch Argos.
Learn moreGitLab too
On GitLab, Argos posts commit statuses on your merge requests through a bot user, with the same baseline selection from your commit history.
Learn moreAuto-approved branches become baselines
Builds on main, or any branch pattern you set, are approved automatically so they can serve as baselines without a manual review. A build with an active rejection never becomes one.
Summary check, your way
Post argos/summary only when a commit has more than one build, always, or never. Require the summary and the requirement keeps working as you add or rename builds.
Agents show their work
GitHub has no API for attaching an image to a pull request. With Argos, an agent uploads a screenshot or a screen recording from the terminal, stages it on its branch, and Argos posts it on the PR the moment it opens: proof of the change, beside the diff.
Add quick add-to-cart to the product grid
Done. Uploading a screenshot of the new grid.
No pull request yet, so it's staged on the branch: app.argos-ci.com/m/mp21qmkhpe…
Agents review beside your team
Install the skills and point the agent at a pull request. It finds the build, reads the snapshots that need review, weighs them against the PR's intent, and approves or rejects under the name of whoever ran it.
npx skills add https://argos-ci.com
# Read: a project token is enough
argos build get <build>
argos build snapshots <build> --needs-review --json
# Decide: needs a personal access token
argos review create <build> --event approve \
--body "Matches the PR intent."
argos comment list <build> --jsonReview from the CLI
Install the skills, then ask: Use $argos-pr-review to review this pull request. The agent finds the build, reads the snapshots that need review, and submits its verdict with argos review create.
Review over MCP
Connect mcp.argos-ci.com and the agent can approve or reject builds, request reviewers, and read or post comments, within the reviews:write and comments:write scopes you grant.
Every action in the API
Submit, list, and dismiss reviews; create comments and replies, react, resolve. Project tokens read, personal tokens decide. Agents use build data as review evidence; they do not replace your team's ownership of review decisions.
Learn more
“Pinning a comment to the exact thing that changed ended our endless back and forth. Reviews now happen in a single thread, in real time.”
Frequently asked questions
One platform, from pull request to merge
Review is the third step. Argos also deploys every pull request, diffs everything that changed, and stabilizes the tests behind it.
Supercharge your product quality
See every change your team and your agents make. Review with confidence, and merge faster.