> 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/reference.md).

# Reference

- [Playwright SDK reference (@argos-ci/playwright)](https://argos-ci.com/docs/reference/playwright.md): Reference for @argos-ci/playwright: the Argos reporter, argosScreenshot options and stabilization, ARIA snapshots, sharding, and trace uploads for Playwright visual tests.
- [Vitest SDK reference (@argos-ci/vitest)](https://argos-ci.com/docs/reference/vitest.md): Reference for @argos-ci/vitest: the Vitest plugin, argosScreenshot for browser mode screenshots, and argosSnapshot for diffing any value from browser or Node tests.
- [Storybook SDK reference (@argos-ci/storybook)](https://argos-ci.com/docs/reference/storybook.md): Reference for @argos-ci/storybook: capture stories with the Storybook Vitest addon or Test Runner, choose which stories are captured, set viewports, modes, and fit-to-content, and take screenshots in
- [Cypress SDK reference (@argos-ci/cypress)](https://argos-ci.com/docs/reference/cypress.md): Reference for @argos-ci/cypress: the cy.argosScreenshot command, the upload task, stabilization options, and viewports for Cypress visual tests.
- [WebdriverIO SDK reference (@argos-ci/webdriverio)](https://argos-ci.com/docs/reference/webdriverio.md): Reference for @argos-ci/webdriverio: capture screenshots in WebdriverIO tests with argosScreenshot, hide, remove, or mask dynamic elements, and upload them to Argos with the CLI.
- [Puppeteer SDK reference (@argos-ci/puppeteer)](https://argos-ci.com/docs/reference/puppeteer.md): Reference for @argos-ci/puppeteer: argosScreenshot options, stabilization, and viewports for visual testing with Puppeteer scripts.
- [Argos CLI reference (@argos-ci/cli)](https://argos-ci.com/docs/reference/argos-command-line-interface-cli.md): Use the Argos CLI to upload screenshots, deploy static builds, inspect builds and flaky tests, and submit reviews from scripts, local workflows, or AI agents.
- [Node.js SDK reference (@argos-ci/core)](https://argos-ci.com/docs/reference/node.js-sdk.md): Upload screenshots and standalone media programmatically from Node.js scripts, or build your own Argos integration with @argos-ci/core.
- [Screenshot metadata](https://argos-ci.com/docs/reference/screenshot-metadata.md): Attach metadata to screenshots with a companion JSON file to add context on the Argos build page.


---

# 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/reference.md?ask=<question>&goal=<user_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.