iiinova — where your digital self keeps evolving

Argos @argos-ci.com · 07/09/2026

How many screenshots does your visual suite actually take per build? We see everything from 12 to 1,100+. Curious where people land — and whether you review them all.

000

Argos @argos-ci.com · 06/09/2026

Your agent can now review visual changes itself. The Argos MCP server is live: mcp.argos-ci.com List builds, inspect diffs, approve or reject reviews, read and post comments. OAuth built in — Claude Code, Cursor, VS Code, Codex, Windsurf.

120

Argos @argos-ci.com · 05/09/2026

You probably don't need to write a visual test suite. Your Playwright tests already navigate to every important state — logged in, empty, error, checkout. They just throw the pixels away at the end. Add one line per test and those journeys become visual coverage.

000

Argos @argos-ci.com · 04/09/2026

Comment on the exact pixel that changed. Not "the card near the top" — a pin on the screenshot, or a line range inside a JSON or Markdown snapshot. With threads, @mentions, reactions and resolve. Plus draft reviews that stay private until you submit.

000

Argos @argos-ci.com · 03/09/2026

Connect your agent to Argos in one line: claude mcp add --transport http argos mcp.argos-ci.com Remote and stateless — nothing to install, nothing running on your machine. OAuth handles the rest.

110

Argos @argos-ci.com · 02/09/2026

Most teams test light mode and hope. Dark mode has its own bugs: invisible borders, unreadable text on brand colors, images with baked-in white backgrounds. Run the same stories in both, tagged by color scheme, so you can review one mode at a time.

000

Argos @argos-ci.com · 01/09/2026

You've approved the same diff 40 times. Argos noticed. When a visual change keeps reappearing and keeps getting approved, the bot starts ignoring it for you. Configurable threshold, on by default, every plan. Anything new or different still surfaces.

000

Argos @argos-ci.com · 01/09/2026

Custom domains for deployments are here. Serve your production deployments from a domain you own. storybook.acme.com instead of a generated URL nobody recognises.

100

Argos @argos-ci.com · 31/08/2026

You don't need to hand-roll screenshot stabilization. Argos waits for fonts, images and aria-busy before every capture — then hides carets and scrollbars, pauses GIFs, disables animations and fixes antialiasing. The flake teams fight manually is already handled.

000

Argos @argos-ci.com · 30/08/2026

Most teams assert on UI like this: expect(button).toHaveClass('primary') That passes when the button is invisible, off-screen, or the wrong color. A screenshot asserts what the user actually sees — all of it, in one line. The assertion you skip is the bug you ship.

000

Argos @argos-ci.com · 29/08/2026

We put a 99.99% uptime SLA on Enterprise because a visual testing service that's down blocks every merge in your org. CI tooling has one job: be there when the build runs.

000

Argos @argos-ci.com · 28/08/2026

Every team screenshots the happy path. Nobody screenshots: ◆ empty state ◆ loading skeleton ◆ error state ◆ a 200-character username ◆ zero results ◆ offline That's where the layout actually breaks.

000

Argos @argos-ci.com · 27/08/2026

On a financial chart, the data is the pixels. A one-pixel shift can be a real bug. Vojtech Gintner, CTO of Finviz: "We use Playwright for E2E, and Argos adds the missing layer of visual testing. On our charts, a single pixel difference can indicate a real bug."

000

Argos @argos-ci.com · 26/08/2026

One command gives your coding agent a visual review workflow: npx skills add argos-ci.com Then just ask: "Use $argos-pr-review to review this pull request with its Argos build."

000

Argos @argos-ci.com · 25/08/2026

Playwright locators, best to worst: getByRole('button', { name: 'Save' }) getByLabel('Email') getByText('Welcome back') getByTestId('save-btn') locator('.btn > span:nth-child(2)') If a locator breaks when you restyle, it was testing the wrong thing. argos-ci.com/blog/playwr...

000

Argos @argos-ci.com · 24/08/2026

An agent can point at the exact pixel. argos comment create 1234 \ --diff <diffId> \ --anchor-point 412,168 \ --body "Focus ring disappeared here." Or --anchor-lines 40,48 to pin a range inside a JSON or Markdown snapshot.

010

Argos @argos-ci.com · 23/08/2026

"Pixel-perfect diffing" sounds rigorous. In practice one global threshold means you either drown in noise or miss real bugs. A marketing hero and a financial chart don't deserve the same tolerance. Sensitivity belongs per screenshot.

000

Argos @argos-ci.com · 22/08/2026

Don't test 12 viewports. Test 3 that mean something: 375px — the phone where things break 768px — the tablet nobody QAs 1440px — what you designed on More viewports isn't more coverage. It's more diffs to review.

000

Argos @argos-ci.com · 21/08/2026

How does your team catch UI regressions today? ◆ Automated visual tests ◆ Manual QA before release ◆ Preview deploys and eyeballs ◆ Users tell us Genuinely curious where most teams land.

000

Argos @argos-ci.com · 20/08/2026

Delete ARGOS_TOKEN from your repo secrets. Argos authenticates uploads with GitHub OIDC — short-lived, GitHub-signed identity tokens. Add id-token: write and drop the secret. Forked PRs fall back to a verified tokenless flow.

000

Argos @argos-ci.com · 19/08/2026

We rebuilt Argos's UI components on React Aria. Accessibility, keyboard behavior and focus management we no longer hand-roll — and a large amount of custom code deleted. What we learned: argos-ci.com/blog/react-...

000

Argos @argos-ci.com · 18/08/2026

If every test logs in through the UI, you're paying for the same login 200 times. Log in once, save storageState, reuse it everywhere. In most slow Playwright suites this is the single biggest win available. argos-ci.com/blog/speed-...

000

Argos @argos-ci.com · 17/08/2026

We're SOC 2 compliant. The honest summary for a small team: most of the work isn't adding security. It's writing down the security you already had, then proving it every quarter. argos-ci.com/blog/soc-2

001

Argos @argos-ci.com · 16/08/2026

Le Monde's CMS, Sirius, is the backbone of the group's content operations. A delay in publication can cost millions of euros. Paul Laleu, CTO: "Thanks to Argos, we can confidently deploy updates to Sirius without worrying about unexpected issues."

000

Argos @argos-ci.com · 15/08/2026

A screenshot tells you it looks right. An ARIA snapshot tells you it is right. - heading "Dashboard" [level=1] - button "New project" - list: - listitem: "Project A" Catches the div-soup regression no pixel diff ever will.

000

Argos @argos-ci.com · 14/08/2026

Visual review, from the terminal: argos build get 1234 argos build snapshots 1234 --needs-review argos review create 1234 --event approve Anything a human can do in the UI, an agent can do too. Same permissions, same audit trail.

000

Argos @argos-ci.com · 13/08/2026

Committing screenshots to your repo means: ◆ repo size that only grows ◆ binary diffs nobody can review ◆ "update snapshots" commits nobody audits ◆ baselines that only match one machine's fonts Baselines are build artifacts. Store them like build artifacts.

000

Argos @argos-ci.com · 12/08/2026

How it looks in practice: the agent opens the PR and the demo recording is already in the comments. A reviewer pins a spot, the agent reads the coordinates from the CLI, fixes, resolves. Following along on Product Hunt today: www.producthunt.com/posts/media...

000

Argos @argos-ci.com · 12/08/2026

Visual testing isn't only for pixels. Your API response shape, generated Markdown, and rendered email HTML all regress silently too. argos upload ./out --files '**/*.json' Same baseline workflow. No image involved.

000

Argos @argos-ci.com · 12/08/2026

Your coding agent can't drag a screenshot into a pull request — GitHub has no API for it. Now it doesn't need one: `argos media upload` turns any image or video into a share link, and Argos posts it on the PR by itself. We're live on Product Hunt today 🚀

100

Argos @argos-ci.com · 10/08/2026

The Argos API could read your builds and review them. Everything else — who's on the team, how a project is configured, which automations fire — lived only in the app. Thirty-four new endpoints close that gap.

100

Argos @argos-ci.com · 09/08/2026

MUI runs 2.5M+ screenshots per month through Argos. Five projects. 1,100+ screenshots compared on every build in the Material UI repo alone. Base UI is in there too — the library that powers shadcn/ui. argos-ci.com/customers/mui

010

Argos @argos-ci.com · 08/08/2026

AI writes UI faster than humans can review it. An agent can open six PRs before lunch. Every one touches the layout. Nobody is opening six preview deploys. The bottleneck moved from writing code to verifying what it looks like.

000

Argos @argos-ci.com · 07/08/2026

Your agent doesn't have to just approve or reject. It can hold a conversation. argos comment create <build> --body "..." argos comment react <build> <id> eyes argos comment resolve <build> <id> Reply, react, resolve, subscribe. A reviewer, not a webhook.

010

Argos @argos-ci.com · 07/08/2026

An agent approving a build: argos review create 1234 --event approve --body "Intentional spacing change, matches the PR." --event takes approve, reject or comment. Same permissions as a human. Same audit trail.

010

Argos @argos-ci.com · 07/08/2026

We didn't hand-write an agent API. Every Argos MCP tool is generated from our public REST API — same endpoints, same permissions, same behavior. 24 tools today. Ship an endpoint, your agent gets the tool. Humans and agents never drift apart.

000

Argos @argos-ci.com · 06/08/2026

Argos tests Argos. Every PR on our app uploads screenshots to Argos and blocks on visual review. Our marketing site too. If our review flow is annoying, we're the first ones to feel it.

000

Argos @argos-ci.com · 06/08/2026

Plenty of engineering teams run their day in Discord. Argos build notifications now post to any Discord channel as embeds, with a link straight into the build. Same automations as Slack and Teams. No bot to install. argos-ci.com/changelog/2...

100

Argos @argos-ci.com · 05/08/2026

We moved Argos off Heroku Postgres onto AWS. ◆ 300GB database ◆ 250M rows ◆ ~1 minute maintenance window The full playbook, including what we'd do differently: argos-ci.com/blog/heroku...

000

Argos @argos-ci.com · 05/08/2026

A 20-minute Playwright suite on one machine is a ~3-minute suite on eight. --shard=1/8 ... --shard=8/8 Argos supports sharded, retried and repeat-each runs — eight parallel shards still land as one build with one set of diffs.

000

Argos @argos-ci.com · 05/08/2026

The weakest part of any login is the password. You can now sign in to Argos with a passkey — Touch ID, Face ID, Windows Hello, or a YubiKey. No email step, nothing to phish or leak. Every account, every plan. argos-ci.com/docs/learn/...

100

Argos @argos-ci.com · 05/08/2026

Argos is open source. MIT licensed. Not just the SDKs — the platform. Read the diff engine, open an issue, send a PR. And it's free for open-source projects. github.com/argos-ci/argos

000

Argos @argos-ci.com · 04/08/2026

Since people keep asking: there is no separate charge for agent usage in Argos. An agent reading a build costs exactly what you reading it costs: nothing. You pay for screenshots, not for who looks at them.

000

Argos @argos-ci.com · 04/08/2026

The interesting part isn't agents reviewing visual diffs. It's what happens next: an agent that can see it broke the layout can go fix it in the same loop — before you ever open the PR.

000

Argos @argos-ci.com · 04/08/2026

Every read command in the Argos CLI takes --json. argos build snapshots 1234 --needs-review --json Structured output your agent can parse — builds, diffs, reviews, comments, analytics. No scraping. No screenshots of screenshots.

000

Argos @argos-ci.com · 03/08/2026

A screenshot from your laptop and one from CI can differ by an hour — or by a whole date format. Pin it in CI: TZ=UTC LANG=en_US.UTF-8 Argos stabilizes the browser for you. Your environment is still yours to pin.

000

Argos @argos-ci.com · 03/08/2026

argos deploy ./storybook-static A live URL on every PR. Immutable previews, branch URLs that follow your latest build, promotion to a production domain on merge, access protection. Storybook, Vite, Next.js exports, plain HTML — anything static.

000

Argos @argos-ci.com · 03/08/2026

The conversation about a flaky test used to disappear with the build that surfaced it. Now every test in Argos has its own thread: reply, @mention, react, resolve, follow. In the UI, the CLI, the API and MCP. argos-ci.com/changelog/2...

100

Argos @argos-ci.com · 02/08/2026

An agent reviewing your PR reads the diff. It doesn't know the button moved 4px, the modal now overflows on mobile, or the chart lost its axis labels. Give it the screenshots and it does.

000

Argos @argos-ci.com · 01/08/2026

What's the worst visual regression you've shipped? Starting with a classic: a spacing change that pushed the primary CTA below the fold on mobile. Conversion drops. Every test green.

001