> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn.md). # Learn - [Core concepts](https://argos-ci.com/docs/learn/platform-fundamentals.md): The core concepts behind Argos — builds, baselines, comparisons, and the statuses you see on your pull requests. - [How Argos detects visual differences](https://argos-ci.com/docs/learn/platform-fundamentals/how-argos-detects-visual-differences.md): Discover how Argos uses deterministic pixel diffing with the odiff library to surface meaningful visual changes. - [Baseline build](https://argos-ci.com/docs/learn/platform-fundamentals/baseline-build.md): Argos compares screenshots to a chosen baseline build, determined by analyzing the commit history of your Git project. - [Build modes](https://argos-ci.com/docs/learn/platform-fundamentals/build-modes.md): Compare Argos Continuous Integration mode and Monitoring mode to choose the right one for your workflow. - [Review workflow](https://argos-ci.com/docs/learn/review-workflow.md): Bring Argos visual changes into your review process across the dashboard, pull requests, and status checks. - [Builds list](https://argos-ci.com/docs/learn/review-workflow/builds-list.md): Browse, filter, and open builds for a project to scan status and drill into the runs you care about in Argos. - [Review a build](https://argos-ci.com/docs/learn/review-workflow/review-a-build.md): Review visual changes as a team — request reviewers, comment on the exact pixel or line that changed, discuss in threads, and approve or reject in real time. - [Pull request comments](https://argos-ci.com/docs/learn/review-workflow/pull-request-comments.md): Get the latest Argos build status and a link to the build page posted automatically on your GitHub pull requests. - [Summary checks](https://argos-ci.com/docs/learn/review-workflow/summary-checks.md): Configure Argos summary checks to combine commit statuses into one required status check before merging. - [Tags](https://argos-ci.com/docs/learn/review-workflow/tags.md): Categorize and filter screenshots by tag so you can focus a build review on the changes you care about. - [Review builds with AI agents](https://argos-ci.com/docs/learn/review-workflow/review-builds-with-ai-agents.md): Let an AI agent read Argos build data to summarize visual changes, check intent, and approve or request changes. - [Automations](https://argos-ci.com/docs/learn/review-workflow/automations.md): Create 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. - [Reliability & flakiness](https://argos-ci.com/docs/learn/reliability-and-flakiness.md): Detect unstable tests and use Argos tools and strategies to track and fix flakiness in your visual suite. - [Flaky test detection](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-test-detection.md): See flaky badges, stability scores, and detailed history so you can review changed tests in Argos with confidence. - [Tests dashboard](https://argos-ci.com/docs/learn/reliability-and-flakiness/tests-dashboard.md): Get a project-wide view of test stability, with every test ranked by flakiness score in the Argos dashboard. - [Test page](https://argos-ci.com/docs/learn/reliability-and-flakiness/test-page.md): Investigate a single test on its own page: flakiness metrics over time, every change it produced, discussion with your team, and a prompt to hand to an AI agent. - [Ignored changes](https://argos-ci.com/docs/learn/reliability-and-flakiness/ignored-changes.md): Review every change your project has ignored, see how much review noise each one absorbs, and unignore the ones that went quiet. - [Fix flaky tests with AI agents](https://argos-ci.com/docs/learn/reliability-and-flakiness/fix-flaky-tests-with-ai-agents.md): Hand 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. - [Stabilize screenshots and fix flaky visual tests](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-tests.md): A playbook for tackling visual flakiness, with detection, ignoring noisy changes, and stabilization strategies. - [Stabilize text rendering](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-tests/stabilize-text-rendering.md): Disable subpixel text and font hinting in headless Chromium to reduce glyph rendering differences between machines. - [Wait for loading](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-tests/wait-for-loading.md): Use aria-busy so argosScreenshot waits for full page load before capturing, and see what Argos waits for before each screenshot, in Storybook too. - [Wait for background images](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-tests/wait-for-background-images.md): Wait for CSS background images to load before capturing with the waitForBackgroundImages stabilization option. - [Pause animated GIFs](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-tests/pause-gifs.md): Freeze animated GIFs on their first frame with the pauseGifs stabilization option so they no longer capture a random frame on each run. - [Stabilize date & time](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-tests/stabilize-date-and-time.md): Hide or freeze dynamic dates and times to remove a common source of flaky visual diffs in Argos. - [Browser glitches](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-tests/browser-glitches.md): Eliminate browser-induced visual discrepancies like border-radius differences with a consistent test environment. - [Argos helpers](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-tests/argos-helpers.md): Use data-visual-test attributes or SDK options to hide, remove, or mask dynamic elements for consistent, flake-free screenshots. - [Deployments](https://argos-ci.com/docs/learn/deployments.md): Deploy your Storybook or static build to a unique Argos URL on every pull request to preview and share it. - [Use deployments in CI](https://argos-ci.com/docs/learn/deployments/use-deployments-in-ci.md): Run argos deploy from CI to create a deployment on every pull request, with a GitHub Actions Storybook example. - [Environments](https://argos-ci.com/docs/learn/deployments/environments.md): Understand how Argos assigns each deployment to a preview or production environment from your branch patterns. - [URLs and domains](https://argos-ci.com/docs/learn/deployments/urls-and-domains.md): Understand the deployment, branch, and production URLs Argos generates, and serve production from a domain you own. - [Access protection](https://argos-ci.com/docs/learn/deployments/access-protection.md): Require viewers to sign in before opening deployment URLs to keep your Argos previews private per project. - [Lifecycle and retention](https://argos-ci.com/docs/learn/deployments/retention.md): How long Argos deployments last, why they can't be overwritten, and how to pick a deploy cadence without cleaning up old builds. - [Media sharing](https://argos-ci.com/docs/learn/media.md): Upload a standalone image or video to Argos and get a shareable link with ready-to-paste Markdown, so a screenshot or a screen recording can go straight into a pull request. - [Upload media](https://argos-ci.com/docs/learn/media/standalone-media-upload.md): Upload images and videos to Argos from the CLI, the Node.js SDK, the REST API or an AI agent, and get them into a pull request with a managed comment. - [Share links, retention and limits](https://argos-ci.com/docs/learn/media/share-links-retention-and-limits.md): Who can open an Argos media share link, how long an uploaded file is kept, the formats and sizes accepted, and how uploads are billed. - [How-to guides](https://argos-ci.com/docs/learn/how-to-guides.md): Task-focused guides for wiring Argos into your CI pipeline and expanding what your screenshots cover. - [CI pipelines](https://argos-ci.com/docs/learn/how-to-guides/ci-pipelines.md): Run Argos in GitHub Actions, GitLab CI, CircleCI, Buildkite, or any other CI, with patterns for monorepos, sharding, preview deployments, and subset builds. - [Run Argos in CI (GitHub Actions, GitLab CI, CircleCI, Buildkite)](https://argos-ci.com/docs/learn/how-to-guides/ci-pipelines/run-argos-in-ci.md): Run Argos visual tests in GitHub Actions, GitLab CI, CircleCI, Buildkite, or any other CI: working pipeline examples, the CI providers Argos detects automatically, and the environment variables to set - [Parallel testing (sharding)](https://argos-ci.com/docs/learn/how-to-guides/ci-pipelines/parallel-testing-sharding.md): Collect screenshots from sharded or parallelized test runs into a single Argos build across your CI nodes. - [Subset builds](https://argos-ci.com/docs/learn/how-to-guides/ci-pipelines/subset-builds.md): Run subset builds to upload a partial test run without affecting the baseline of screenshots it didn't cover. - [Skipping a build](https://argos-ci.com/docs/learn/how-to-guides/ci-pipelines/skipping-a-build.md): Skip an Argos build to report success without screenshots when a required check shouldn't run a visual comparison. - [Cached CI pipelines (Turborepo, Nx)](https://argos-ci.com/docs/learn/how-to-guides/ci-pipelines/cached-pipelines.md): Run Argos reliably in pipelines where a task cache like Turborepo or Nx decides which test suites actually run. - [Monorepos setup](https://argos-ci.com/docs/learn/how-to-guides/ci-pipelines/monorepos-setup.md): Use build splitting to run separate Argos visual tests for each package or app in your monorepo within one commit. - [Run on preview deployments](https://argos-ci.com/docs/learn/how-to-guides/ci-pipelines/run-on-preview-deployments.md): Run Argos visual tests against Vercel, Netlify, or Cloudflare preview deployments to catch regressions before merging. - [Visual coverage](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage.md): Techniques to capture more of your interface, from responsive viewports and injected CSS to non-image file diffs. - [Responsive viewports](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage/responsive-viewports.md): Capture the same page at multiple breakpoints in one test with Argos using Playwright, Cypress, or Puppeteer. - [Storybook story modes](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage/storybook-story-modes.md): Capture separate Storybook snapshots for each mode, combining theme, viewport, and locale globals in Argos. - [Capture screenshots from URLs](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage/capture-screenshots-from-urls.md): Capture screenshots of a list of web pages with Argos using Playwright, Cypress, or Puppeteer. - [Injecting CSS](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage/injecting-css.md): Apply custom CSS at capture time to hide or restyle elements and fix flaky visual diffs in your Argos screenshots. - [Fallback baselines](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage/fallback-baselines.md): Compare a new screenshot against an existing one so variants and A/B tests show real changes instead of appearing as brand new screenshots. - [Adding ARIA snapshots manually](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage/adding-aria-snapshots-manually.md): Include ARIA accessibility snapshots alongside screenshots when uploading files to Argos manually with the CLI. - [Compare non-image files](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage/compare-non-image-files.md): Upload and diff text-based artifacts like JSON, HTML, Markdown, and CSS in Argos using the CLI files option. - [Migrate to Argos from another visual testing tool](https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos.md): Step-by-step guides for switching to Argos from Percy, Chromatic, Applitools, native Playwright or Vitest screenshots, BackstopJS, or Lost Pixel. - [Migrate from Percy to Argos](https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos/from-percy.md): Migrate visual testing from Percy (BrowserStack) to Argos. Replace the Percy SDK and percy exec with the Argos reporter for Playwright, Cypress, or Storybook. - [Migrate from Chromatic to Argos](https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos/from-chromatic.md): Migrate visual testing from Chromatic to Argos. Move your Storybook, Playwright, or Cypress visual tests off the chromatic CLI to the Argos SDK. - [Migrate from Applitools to Argos](https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos/from-applitools.md): Migrate visual testing from Applitools Eyes to Argos. Replace the eyes.check() lifecycle and the Ultrafast Grid with Argos screenshots for Playwright or Cypress. - [Migrate from Playwright toHaveScreenshot to Argos](https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos/from-playwright-native-screenshots.md): Move from Playwright's built-in toHaveScreenshot() snapshots to Argos. Stop committing PNG baselines to Git and review visual changes on the pull request. - [Migrate from Vitest toMatchScreenshot to Argos](https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos/from-vitest-native-screenshots.md): Move from Vitest's built-in toMatchScreenshot() to Argos. Stop committing \_\_screenshots\_\_ reference images and review visual changes on the pull request. - [Migrate from BackstopJS to Argos](https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos/from-backstopjs.md): Migrate visual testing from self-hosted BackstopJS to Argos. Turn backstop.json scenarios into Playwright screenshots with cloud baselines and pull request review. - [Migrate from Lost Pixel to Argos](https://argos-ci.com/docs/learn/how-to-guides/migrate-to-argos/from-lost-pixel.md): Migrate visual testing from Lost Pixel to Argos. Map the Storybook, Ladle, Histoire, page, and custom shots of lostpixel.config.ts to the Argos Storybook SDK, Playwright, or argos upload. - [Integrations](https://argos-ci.com/docs/learn/integrations.md): Connect Argos to your Git provider for pull request statuses, authenticate your CI uploads, and get notified in Slack. - [GitHub integration](https://argos-ci.com/docs/learn/integrations/github-integration.md): Connect Argos to GitHub for automated visual testing, commit and pull request checks, and baseline selection. - [GitHub Actions authentication](https://argos-ci.com/docs/learn/integrations/github-actions-authentication.md): Authenticate Argos uploads from GitHub Actions with a project token, OIDC, or tokenless authentication. - [GitLab integration](https://argos-ci.com/docs/learn/integrations/gitlab-integration.md): Connect Argos to GitLab for visual testing, baseline selection, and direct feedback on your merge requests. - [Other Git providers](https://argos-ci.com/docs/learn/integrations/other-git-providers.md): Bitbucket and Azure DevOps support in Argos, and how to use Argos with an unsupported Git provider. - [Slack integration](https://argos-ci.com/docs/learn/integrations/slack-integration.md): Connect Argos to Slack for build notifications and rich previews when you paste an Argos build URL. - [Microsoft Teams integration](https://argos-ci.com/docs/learn/integrations/microsoft-teams-integration.md): Send Argos build notifications to a Microsoft Teams channel using an incoming webhook. - [Discord integration](https://argos-ci.com/docs/learn/integrations/discord-integration.md): Send Argos build notifications to a Discord channel using an incoming webhook. - [Account & access](https://argos-ci.com/docs/learn/account-and-access.md): Manage your Argos account, configure how your team signs in, and control who can access which projects. - [Account management](https://argos-ci.com/docs/learn/account-and-access/account-management.md): Create and manage your Argos account, sign up with Google, GitHub, or GitLab, and pick the plan that fits. - [Analytics](https://argos-ci.com/docs/learn/account-and-access/analytics.md): Track builds, screenshots, change rate, and approval rate across every project in your Argos account — from the dashboard, the REST API, or the CLI. - [Team members & roles](https://argos-ci.com/docs/learn/account-and-access/team-members-and-roles.md): Invite team members and assign team and project roles to control permissions with role-based access control. - [Passkeys](https://argos-ci.com/docs/learn/account-and-access/passkeys.md): Add passkeys to your Argos account and sign in with your fingerprint, face, screen lock, or a hardware security key. - [GitHub single sign-on](https://argos-ci.com/docs/learn/account-and-access/github-single-sign-on.md): Enable GitHub single sign-on to sync your Argos team with a GitHub organization and let members sign in with GitHub. - [SAML single sign-on](https://argos-ci.com/docs/learn/account-and-access/saml-single-sign-on.md): Configure SAML single sign-on with providers like Okta or Auth0 to authenticate your Argos team members. - [SCIM provisioning](https://argos-ci.com/docs/learn/account-and-access/scim-provisioning.md): Provision and deprovision Argos team members from Okta, Microsoft Entra ID or any SCIM 2.0 identity provider, and map their roles. - [Security and compliance](https://argos-ci.com/docs/learn/account-and-access/security-and-compliance.md): Where Argos hosts your data, its SOC 2 Type II and GDPR compliance, the DPA, and how long your data is kept, how to export it, and how to delete it. - [Billing & subscription](https://argos-ci.com/docs/learn/billing-and-subscription.md): Understand Argos plans, payment, and usage so you can keep your team's billing under control. - [Argos pricing plans](https://argos-ci.com/docs/learn/billing-and-subscription/pricing-plans.md): Compare the Hobby, Pro, and Enterprise plans to find the right Argos pricing for individuals, teams, or companies. - [How to subscribe](https://argos-ci.com/docs/learn/billing-and-subscription/how-to-subscribe.md): Move from the free Hobby plan to a Pro team, with a 14-day trial, Stripe checkout, or GitHub Marketplace — and manage the subscription afterwards. - [Usage & spend management](https://argos-ci.com/docs/learn/billing-and-subscription/spend-management.md): Track your team's screenshot usage, understand what happens at your plan limit, and set spend thresholds to get notified or pause builds. - [Open-source sponsorship](https://argos-ci.com/docs/learn/billing-and-subscription/open-source.md): Find out how qualifying open-source projects can get sponsored, free access to Argos visual testing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://argos-ci.com/docs/learn.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.