If Argos CI screenshots are missing or an upload fails, first check that the uploader ran, that its file root and glob match the screenshots CI actually produced, and that the upload job can authenticate to the Argos project connected to the repository. On GitHub Actions, a secret named ARGOS_TOKEN takes precedence over OIDC and tokenless authentication, so an unexpected secret can change the path Argos uses. The right fix depends on the error and workflow; use the checks below to isolate it.
1. Confirm the screenshot and uploader both ran
Taking a screenshot does not necessarily upload it. The Argos Playwright quickstart configures the Argos reporter and shows uploads gated by uploadToArgos: !!process.env.CI. Check that the reporter is present in the Playwright configuration and that the upload job sets the CI context expected by that configuration. See the Argos Playwright quickstart.
As an Amazon Associate I earn from qualifying purchases.
The quickstart’s argosScreenshot helper writes screenshots to ./screenshots by default. If you use the direct Node.js SDK or CLI instead, compare the configured root and file pattern with the actual output path and file extension. The SDK example uses root: "./screenshots" and a glob such as **/*.png; a different output folder, JPEG extension, or nested path can leave the uploader with no matching files. See the Argos SDK reference.
- Inspect the job log to confirm the reporter or upload command ran.
- List the generated screenshot files before upload, including their paths and extensions.
- Match the upload root and glob to those files; do not assume the test runner’s output directory is the uploader’s root.
For a CLI upload, the package README documents this command shape:
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
ARGOS_TOKEN="<your-argos-token>" npx @argos-ci/cli upload ./screenshotsThe package listing is at npmjs.com/package/@argos-ci/cli. Check the current official CLI documentation for flags that match your installed version before changing options.
2. Identify which authentication method Argos is using
For GitHub Actions, Argos tries authentication in this order: ARGOS_TOKEN, then OIDC when enabled and permitted, then tokenless authentication. Check whether a repository, environment, or reusable-workflow secret is injecting ARGOS_TOKEN; do not print its value in logs. If it is set, OIDC may be skipped. Argos documents the selection order in its GitHub Actions authentication guide.
Use a project token
ARGOS_TOKEN is supported across CI providers. Add it as a protected CI secret and make it available to the step that performs the upload. It is a long-lived secret, so provision and rotate it accordingly. The Playwright quickstart also shows passing a token through the reporter’s token option.
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
Use OIDC on GitHub Actions
OIDC avoids storing an Argos project token, but requires both Argos project configuration and permissions on the job that uploads:
- In Argos, open Project Settings → Authentication and enable GitHub OIDC.
- Grant
id-token: writeto the workflow or job that actually runs Argos. A permission on a different job does not carry over. - Include any other permissions needed by your workflow. Argos’s example includes
contents: readfor checkout andpull-requests: readfor PR association. - Check that
ARGOS_TOKENis not set if you expect OIDC to be selected.
Use tokenless authentication on GitHub Actions
Tokenless mode needs no Argos token and is useful for fork pull requests where GitHub withholds secrets and OIDC. Leave ARGOS_TOKEN unset and do not grant id-token: write when you intend to use tokenless alone. Argos must find a matching GitHub workflow run; the repository, commit, branch, and run context must correspond, and the run needs to be in progress when verification occurs.
If multiple Argos projects are connected to the same repository, specify the intended project slug, for example account/project-name, using ARGOS_PROJECT, the CLI option, or the SDK option. Tokenless authentication alone does not link the build to a pull request; pass GITHUB_TOKEN if the SDK needs to resolve PR metadata.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
Choose based on your CI setup
| Method | Availability and requirements | Trade-off |
|---|---|---|
| Project token | All CI providers; supply ARGOS_TOKEN. |
Requires storing and rotating a long-lived secret. |
| OIDC | GitHub Actions; enable it in Argos and grant id-token: write to the upload job. |
Short-lived identity without a stored Argos secret, but needs configuration and permissions. |
| Tokenless | GitHub Actions; relies on Argos matching the active GitHub workflow run. | Needs no token and supports fork PRs without secrets or OIDC, but depends on run lookup and may need an explicit project slug. |
Argos documents tokenless authentication as unavailable on CI providers other than GitHub Actions; use a project token there.
3. Match the error to the fix
| Error or symptom | What to check |
|---|---|
Unable to get OIDC token or a 403 from the OIDC endpoint |
Grant id-token: write to the upload job and confirm GitHub OIDC is enabled in the Argos project. |
Argos keeps using ARGOS_TOKEN |
Check repository, environment, and reusable-workflow secrets for an injected variable. Verify presence without exposing its value. |
Repository does not match the Argos project |
Confirm the workflow’s repository is connected to that Argos project; correct the connection if it is not. |
No matching workflow run found |
Check the repository link and confirm the upload occurs while GitHub reports the matching run as in progress. |
Multiple projects are linked to this repository |
Set the intended Argos project slug explicitly. |
| Upload accepted, but PR metadata is missing | This is distinct from upload rejection. Tokenless mode alone does not link the build to a PR; pass GITHUB_TOKEN so the SDK can resolve it. |
| No visible screenshots, with no authentication error | Check that the upload path ran and that root and glob select the files CI generated. |
4. Check size limits and separate test diagnostics from uploads
The Argos Playwright SDK reference sets a limit of 50 MB per uploaded snapshot, including screenshots and Playwright traces. If the log reports an item or payload size problem, inspect individual files and traces rather than only the total run size. See the Playwright SDK reference.
Failure screenshots and traces are useful for diagnosing test failures, but they require the reporter and relevant Playwright settings—for example, trace: "on-first-retry" and screenshot: "only-on-failure". These debugging attachments do not establish that ordinary visual snapshots are configured for Argos upload.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
For screenshot differences between local and CI, Argos’s Playwright example recommends Chromium flags --disable-lcd-text and --font-render-hinting=none to make text rendering more consistent. Those flags address rendering variation, not credentials or rejected uploads.
5. Preserve the files to prove what CI produced
When you cannot tell whether the failure happened during capture or upload, save the screenshot directory and relevant logs as GitHub workflow artifacts. GitHub artifacts preserve files produced by a workflow after a job and can make them available to another job; screenshots and test results are common examples. They help verify that files existed, but they do not authenticate with Argos or complete its upload. See GitHub’s workflow artifact documentation.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Or skip the browser setup
If your task is simply to capture a webpage rather than upload Playwright test snapshots into an Argos project, ScreenshotNeo provides a screenshot API and MCP server. One GET request can return a PNG, JPEG, WebP, or PDF. Here is a cURL example:
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. This is a separate website-capture workflow, not a fix for an Argos reporter or project-authentication error.
Sign up for ScreenshotNeo’s free plan to try 1,000 screenshots a month with no card.
Frequently Asked Questions
Can I use Argos tokenless authentication outside GitHub Actions?
No. Argos documents tokenless authentication for GitHub Actions; for another CI provider, use an Argos project token.
Recommended Free Tools
Does saving screenshots as GitHub artifacts upload them to Argos?
No. Artifacts preserve generated files for inspection or sharing between jobs, but they do not authenticate or perform the Argos upload.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
