> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/resources/reporters.md). # Reporters - [@currents/playwright](https://docs.currents.dev/resources/reporters/currents-playwright.md): Setup and usage instructions for Playwright integration with Currents Dashboard - [Compatibility Guide](https://docs.currents.dev/resources/reporters/currents-playwright/compatibility.md): Discover the compatible versions of @currents/playwright - [Configuration](https://docs.currents.dev/resources/reporters/currents-playwright/configuration.md): @currents/playwright configuration reference - [pwc](https://docs.currents.dev/resources/reporters/currents-playwright/pwc.md): pwc command-line executable documentation - [pwc-p (orchestration)](https://docs.currents.dev/resources/reporters/currents-playwright/pwc-p.md): Currents orchestration pwc-p command-line executable documentation - [pwc-p discover](https://docs.currents.dev/resources/reporters/currents-playwright/pwc-p/pwc-p-discover.md): pwc-p discover command documentation - test discovery and filtering for Playwright orchestration - [pwc-p run](https://docs.currents.dev/resources/reporters/currents-playwright/pwc-p/pwc-p-run.md): pwc-p run command documentation - orchestration execution for Playwright - [Playwright Fixtures](https://docs.currents.dev/resources/reporters/currents-playwright/playwright-fixtures.md): Enhance Playwright functionality with Currents fixtures for Playwright - [@currents/cmd](https://docs.currents.dev/resources/reporters/currents-cmd.md): The currents command line tool: upload test results, attach files to a run, get or cancel a run, capture sessions as evidence, cache files between CI jobs, and call the Currents REST API - [currents run upload](https://docs.currents.dev/resources/reporters/currents-cmd/currents-upload.md): Upload test results of the Jest and Node.js test runner reporters, JUnit XML reports or Cypress run results to Currents with the currents run upload command, with environments and Currents Actions - [Upload JUnit XML reports](https://docs.currents.dev/resources/reporters/currents-cmd/currents-convert.md): Convert JUnit XML reports of Cypress, Postman, Vitest, WebdriverIO or the Node.js test runner, or Cypress run results, to the Currents format and upload them with currents run upload - [currents run attach](https://docs.currents.dev/resources/reporters/currents-cmd/currents-run-attach.md): Attach logs, screenshots and other files to a run recorded in CI, after the tests finished, with the currents run attach command - [currents run get](https://docs.currents.dev/resources/reporters/currents-cmd/currents-run-get.md): Get the data of a Currents run by CI build ID, or the last run of a branch or tag, with the currents run get command - [currents run cancel](https://docs.currents.dev/resources/reporters/currents-cmd/currents-cancel.md): Cancel a Currents run from CI, for example when the CI job is cancelled, with the currents run cancel command - [currents session](https://docs.currents.dev/resources/reporters/currents-cmd/currents-session.md): Capture an agent or browser session as evidence in Currents, attach screenshots, Playwright traces and logs, and share a link, with the currents session commands - [currents cache](https://docs.currents.dev/resources/reporters/currents-cmd/currents-cache.md): Save files to the Currents cache in one CI job and restore them in another with the currents cache command - [currents api](https://docs.currents.dev/resources/reporters/currents-cmd/currents-api.md): Call any route of the Currents REST API from the command line with the currents api command - [currents skill](https://docs.currents.dev/resources/reporters/currents-cmd/currents-skill.md): Install the currents-cli agent skill, which tells coding agents such as Claude Code, Codex and Cursor how to use the currents command - [Upgrade to 2.0](https://docs.currents.dev/resources/reporters/currents-cmd/upgrade-to-v2.md): Upgrade @currents/cmd from 1.x to 2.0: the breaking changes and the commands to change in scripts and CI jobs - [@currents/jest](https://docs.currents.dev/resources/reporters/currents-jest.md): Currents reporter for Jest - [@currents/node-test-reporter](https://docs.currents.dev/resources/reporters/currents-node-test-reporter.md): Currents Reporter for Node.js Testing Framework - [@currents/cli](https://docs.currents.dev/resources/reporters/currents-cli.md): Setup and usage instructions for Cypress integration with Currents Dashboard - [cypress-cloud](https://docs.currents.dev/resources/reporters/cypress-cloud.md): Setup and usage instruction for cypress-cloud - [Batched Orchestration](https://docs.currents.dev/resources/reporters/cypress-cloud/batched-orchestration.md): Batched orchestration for cypress-cloud - [Migration to Cypress@13](https://docs.currents.dev/resources/reporters/cypress-cloud/migration-to-cypress-13.md): Use cypress-cloud with Cypress@13 - [Data Format Reference](https://docs.currents.dev/resources/reporters/data-format-reference.md): Currents Reporting API - Data Format Reference - [Alternatives to Currents](https://docs.currents.dev/resources/reporters/alternatives-to-currents.md): How to chose the best Playwright Reporter --- # 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://docs.currents.dev/resources/reporters.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.