Greg Bergé @gregberge.com · 01/09/2026Available today on paid plans. Point your domain at Argos and share URLs people actually recognise. argos-ci.com/changelog/c... 000
Greg Bergé @gregberge.com · 01/09/2026Your team sees it everywhere: every commit status and every PR comment on GitHub now links to your domain. 100
Greg Bergé @gregberge.com · 01/09/2026Your domain always serves your latest production deployment. You merge, it updates. Pull requests keep their own preview URLs, so nothing reaches your domain before you ship it. 100
Greg Bergé @gregberge.com · 01/09/2026We made the setup ridiculously simple: one DNS record. That's the entire thing. No ownership verification dance, no certificates to buy or renew. HTTPS just works. 100
Greg Bergé @gregberge.com · 01/09/2026Big one for Argos Deployments: custom domains are here. Your Storybook, your design system, your docs. All live on your own domain, storybook.acme.com instead of a generated URL nobody recognises. 110
Greg Bergé @gregberge.com · 12/08/2026Last hours of our Product Hunt day. Thank you for every question — the thread on the visibility model taught me more than the launch did. If you review agent PRs, I'd genuinely like your take: www.producthunt.com/posts/media... 000
Greg Bergé @gregberge.com · 12/08/2026Media Sharing is live on Product Hunt today. The thread is turning into a genuinely good conversation about a hole in GitHub's API most people never notice — until they run a coding agent. www.producthunt.com/posts/media... 010
Greg Bergé @gregberge.com · 12/08/2026It pairs with what Argos already does: builds catch what nobody intended, media shows the change you meant. We're on Product Hunt today — I'm answering questions all day: www.producthunt.com/posts/media... argos-ci.com/changelog/2...argos-ci.comMedia sharing · ChangelogUpload standalone images and videos from the CLI, SDK, API, or MCP, get a share link with ready-to-paste Markdown, and let Argos post them on the pull request automatically. 000
Greg Bergé @gregberge.com · 12/08/2026The loop I like most: a reviewer pins a comment to a point on the image. The pin is normalized coordinates plus the exact version it was written on — so an agent that can't see pixels reads the spot from the CLI, fixes, and resolves the thread. 100
Greg Bergé @gregberge.com · 12/08/2026We deleted the media processing pipeline before it shipped. ffmpeg worker + server-side re-encode: measured on a real screenshot, 711 ms of CPU to save bytes the CDN already optimizes at request time. Files are stored as sent, usable the moment the upload finishes. 100
Greg Bergé @gregberge.com · 12/08/2026The design decision I care most about: a media is an identity, every upload a version. Re-upload after review and the URL doesn't move — the embed shows the new image, and the version the reviewer commented on survives underneath. Iteration is the normal case; URLs assume it. 100
Greg Bergé @gregberge.com · 12/08/2026We just shipped media sharing in Argos: agents can finally put a screenshot on the PR they opened. It exists because of a hole that keeps surprising me — GitHub has no public API for comment attachments. A browser session can drag an image in; nothing else can. 110
Greg Bergé @gregberge.com · 10/08/2026Designing the API first and generating the rest from it keeps paying off. One spec moves, and the REST endpoints, the MCP tools and the CLI move with it. argos-ci.com/changelog/m... 000
Greg Bergé @gregberge.com · 10/08/2026Now it can't: team members and invites, project settings and contributors, automation rules, deployments, a project's flakiest tests, the reviewers a build is waiting on. No new OAuth scopes. account:admin had been declared for a year with nothing behind it. 100
Greg Bergé @gregberge.com · 10/08/2026The gap was obvious once you saw it. The API could read your builds and review them. But who is on the team, how a project is configured, which automations fire — that lived only in the app. An agent could review a build and then hit a wall. 100
Greg Bergé @gregberge.com · 10/08/2026We shipped 34 endpoints to the Argos API this week, and the part I like most is what we didn't have to build: the MCP server generates its tools from the API, so it went from 37 tools to 71 on its own. 110
Greg Bergé @gregberge.com · 06/08/2026Changelog → argos-ci.com/changelog/2... Setup docs → argos-ci.com/docs/learn/... Automations → argos-ci.com/docs/learn/...argos-ci.comAutomations | Argos DocsCreate rules that react to build events and notify Slack, Microsoft Teams, or Discord, so nobody has to watch Argos to know a build needs review. 000
Greg Bergé @gregberge.com · 06/08/2026Slack. Microsoft Teams. And as of today, Discord. Argos build notifications now land in any Discord channel as embeds. Create a webhook, paste the URL, pick your events. Nothing to install in your server. 🎉 100
Greg Bergé @gregberge.com · 05/08/2026Docs → argos-ci.com/docs/learn/... If your team enforces SAML SSO, worth reading this one too → argos-ci.com/docs/learn/...argos-ci.comSAML single sign-on | Argos DocsConfigure SAML single sign-on with providers like Okta or Auth0 to authenticate your Argos team members. 000
Greg Bergé @gregberge.com · 05/08/2026Every breach story starts the same way: someone's password. Argos now supports passkeys. Touch ID, Face ID, Windows Hello, a YubiKey — pick one and the password stops existing. Nothing to phish, nothing to leak. 🔐 Every account, every plan. 100
Greg Bergé @gregberge.com · 03/08/2026Changelog → argos-ci.com/changelog/2... Docs → argos-ci.com/docs/learn/... Handing it to an agent → argos-ci.com/docs/learn/...argos-ci.comFix flaky tests with AI agents | Argos DocsHand a flaky test to an AI agent: it reads the flakiness metrics and recurring changes from Argos, finds what makes the screenshot unstable, and fixes it in your repository. 000
Greg Bergé @gregberge.com · 03/08/2026A flaky test can haunt a team for months. The build that surfaced it is gone in a day. So we gave every test in Argos its own comment thread — the place to write "flaky since the carousel landed" and actually find it again later. 🎉 100
Greg Bergé @gregberge.com · 25/07/2026Slack has been the only chat integration in Argos for a while. But plenty of engineering teams live in Microsoft Teams, not Slack. So we shipped it: build notifications as adaptive cards in any Teams channel, and no app to install in your tenant. 🎉 100
Greg Bergé @gregberge.com · 21/07/2026Details in the changelog: argos-ci.com/changelog/2...argos-ci.comSAML SSO available as an add-on · ChangelogSAML Single Sign-On is no longer Enterprise-only — enable it on any Pro team as a $200/month add-on from your Billing settings. 000
Greg Bergé @gregberge.com · 21/07/2026SAML SSO used to be an Enterprise-only, talk-to-sales kind of feature. That never sat right with me — plenty of small teams need SSO too. So now any Pro team can flip it on as a $200/mo add-on, straight from Billing. No contract, no call. 🚀 100
Greg Bergé @gregberge.com · 20/07/2026We just shipped the official @argos_ci MCP server 🎉 My favorite part: tools are generated from our REST API — new endpoint ships, your agent gets it automatically. Zero drift. claude mcp add --transport http argos mcp.argos-ci.commcp.argos-ci.comMCP server | Argos DocsConnect AI assistants to Argos with the official MCP server: inspect builds, review visual changes, and manage projects straight from your agent. 100
Greg Bergé @gregberge.com · 13/07/2026Read more in our changelog: argos-ci.com/changelog/2...argos-ci.comAnalytics revamp · ChangelogA redesigned analytics dashboard with change rate, approval rate, and build outcomes — available in the app, the REST API, and a new CLI command. 000
Greg Bergé @gregberge.com · 13/07/2026We rebuilt Argos analytics from scratch. It used to tell you how much you tested. Now it tells you how visual testing is going — change rate, approval rate, build outcomes. Bonus: metrics in the API + CLI for the first time. Your data, your scripts, your agents 🚀 100
Greg Bergé @gregberge.com · 09/07/2026We shipped something big at Argos: official Vitest support 🎉 Your Vitest tests can now capture screenshots and snapshot any value — approved by your team in one click on the PR. No baselines in Git. No --update. Just review. argos-ci.com/blog/argos-...argos-ci.comArgos + Vitest: Visual Testing with Screenshots and SnapshotsThe Argos Vitest SDK is stable: capture screenshots in Vitest browser tests, snapshot any value from browser or Node tests, and review every change on your pull request. Full setup guide inside. 000
Greg Bergé @gregberge.com · 29/06/2026Read more in our changelog: argos-ci.com/changelogargos-ci.comChangelog · ArgosNew updates and improvements to Argos. 000
Greg Bergé @gregberge.com · 29/06/2026Reviewing UI shouldn't be lonelier than reviewing code. Today Argos reviews go collaborative — multiple reviewers, comments pinned to the exact pixel that changed, real-time threads, all in the API. One of my favorite things we've shipped. 100
Greg Bergé @gregberge.com · 28/05/2026Read more in our changelog: argos-ci.com/changelogargos-ci.comChangelog · ArgosNew updates and improvements to Argos. 000
Greg Bergé @gregberge.com · 28/05/2026We built Argos for visual diffs, but screenshots are not the only artifacts that catch regressions. You can now upload JSON, YAML, HTML, Markdown, CSS, JS, XML or text files and review their diffs in Argos. Small step, useful primitive. 100
Greg Bergé @gregberge.com · 19/05/2026argos-ci.com/blog/review...argos-ci.comStep-by-Step Guide: Reviewing Argos Builds with AI AgentsA comprehensive walkthrough on setting up AI agents to inspect and review visual changes in Argos builds using the CLI and the open-source skills. 000
Greg Bergé @gregberge.com · 19/05/2026AI agents can review code. But frontend bugs are often visual: spacing, layout, missing states, broken responsive UI. We wrote a guide showing how to give agents eyes with Argos builds, screenshots, diff masks and CLI data. Link below 👇 100
Greg Bergé @gregberge.com · 18/05/2026We just shipped one of the biggest Argos features since launch: Deployments. Run argos deploy ./storybook-static and get a live URL on every pull request. Storybook, Vite, Next.js exports, plain HTML. argos-ci.com/docs/deploy... 000
Greg Bergé @gregberge.com · 11/05/2026See what we ship: argos-ci.com/changelogargos-ci.comChangelog · ArgosNew updates and improvements to Argos. 000
Greg Bergé @gregberge.com · 11/05/2026We just shipped GitHub OIDC support in Argos. No more long-lived ARGOS_TOKEN secret required for GitHub Actions uploads. Internal PRs use OIDC. Forked PRs fall back to a safer tokenless flow, with Argos verifying the repo, commit, branch, and workflow run. 100
Greg Bergé @gregberge.com · 10/03/2026Read more in our changelog: argos-ci.com/changelog/argos-ci.comChangelog · ArgosNew updates and improvements to Argos. 000
Greg Bergé @gregberge.com · 10/03/2026Flaky visual tests slowly destroy trust in a test suite. You review the same diff again and again. Nothing changed. We solved it in Argos: If the same screenshot diff appears repeatedly across builds, Argos automatically ignores it. Visual tests that start to heal themselves. 100
Greg Bergé @gregberge.com · 06/03/2026Came across a solid set of plug-and-play React components, and it even includes an MCP ✨ 010
Greg Bergé @gregberge.com · 06/03/2026GitHub is the most unreliable service I have ever seen. Their SLA is crashing down so quickly 😱 • Jan: < 99.9% = down 10 min per week • Feb: < 99% = down 1h 40m per week • March: < 98% = down 3h 20m per week • April: ? 000
Greg Bergé @gregberge.com · 05/03/2026argos-ci.com/blog/heroku...argos-ci.comMigrating Argos from Heroku to AWSLessons and technical details from Argos’ move off of Heroku Postgres onto Amazon EC2 and RDS, and a playbook others can follow for large‑scale PostgreSQL migrations. 000
Greg Bergé @gregberge.com · 05/03/2026One of the biggest engineering projects at Argos recently was migrating our 300GB PostgreSQL database off Heroku. We accomplished this by building an EC2 bridge and replicating into RDS with two maintenance windows of 1 minute each. I wrote a deep dive on the full migration 👇 100
Greg Bergé @gregberge.com · 05/03/2026Preview: nodejs-api-docs-tooling.vercel.app/ PRs: github.com/nodejs/node..., github.com/nodejs/node...github.comRedesign of the Node.js API Docs · Issue #52343 · nodejs/nodeHey, y'all 👋 with the redesign of the Node.js Website done. We're ready to move our efforts into revamping the design of the Node.js API docs and its build process. We understand this is co... 000
Greg Bergé @gregberge.com · 05/03/2026Node.js is redesigning its docs site. Here’s the current version vs. the new one 👀 100
Greg Bergé @gregberge.com · 23/02/2026Yes, we ship. See what’s new: argos-ci.com/changelogargos-ci.comChangelog · ArgosNew updates and improvements to Argos. 000
Greg Bergé @gregberge.com · 23/02/2026SAML SSO is now available on Argos Enterprise 🔐 If you’re a larger team, identity management isn’t a “nice to have.” It’s table stakes. You can now: • Authenticate via your IdP • Auto-provision users on first login • Enforce SAML across your team 100