How teams scale Playwright in CI. For humans and agents.

From your editor to CI, fully integrated

• MCP server

  Give AI agents full access to test history, flakiness, and execution context.

• • 

  IDE extension

  Ask AI to fix failures in your editor, with full test history as context.

• • 

  GitHub, GitLab, Bitbucket

  PR status checks, AI failure summaries, and merge blocking on test failures.

• • 

  Slack / MS Teams

  Notifications for failures, flaky tests, and run results in the channels your team already uses.

• Issue tracker

  Link or create Jira/Linear issues from test failures, with visibility into existing tickets.

• REST API & Webhooks

  Stream data, trigger workflows, or build custom reports.

Why teams choose Currents

• The memory your agents don't have

  An agent starts every session from zero. Currents keeps months of runs, flakes and failures, and hands that history to whoever picks up the fix, person or agent.

  ?

• Red means broken. Green means ship.

  People learn to ignore a flaky test. Agents can't. Currents separates flakes from real failures, so agents stop chasing noise and your team stops writing off real bugs as flakes.

• CI in half the time, for a fraction of the bill

  Every agent pull request is another CI run. Currents cuts each one’s time by up to 50% and its cost by up to 70%.

• Say yes to faster releases

  Agents ship more code than anyone can review by hand. Currents proves each change works, with before-and-after evidence on the pull request and checks that block a failing merge.

• From startups to enterprises, since 2021

  From small startups to large enterprises, our cloud scales with your test suite, so your on-call can sleep at night. Enterprise customers can also bring their own storage or run Currents on-premises.

  • 01SOC 2 Type II
  • 02Cloud
  • 03Your storage
  • 04On-premises

• What is Currents?

  Currents is a Playwright reporter, dashboard and test orchestrator for teams running Playwright tests in CI. It records every test run with its errors, traces, screenshots and videos, detects flaky tests, tracks test health over time, and speeds up CI by balancing tests across machines. AI agents use the same data through the Currents MCP server to fix failing tests.

• Which test frameworks does Currents support?

  Currents is built for Playwright. It also reports results from Jest, Vitest, Cypress, the Node.js test runner and any framework that writes JUnit XML, so one dashboard can cover all your test suites.

• Does Currents run my tests?

  No. Your tests run in your own CI, as they do today. The Currents reporter sends each result to the dashboard as it happens, and Currents orchestration tells each CI machine which spec file to run next.

• Why does testing matter more when AI agents write code?

  Agents write code faster than anyone can review it by hand, so the test suite becomes how you know a change works. Currents makes that suite a verification layer: every run is recorded with its evidence, flaky tests are separated from real failures, and agents read the results to fix what they broke and prove the fix on the pull request.

• How do AI agents use Currents?

  Through the Currents MCP server. Claude Code, Cursor, Codex, ChatGPT and any other MCP client connect with a browser sign-in. A connected agent reads a failure’s error, steps, trace and history, so it fixes the cause instead of guessing. It can also quarantine flaky tests, file Jira issues, and record before-and-after evidence of a fix for the pull request.

• How long does it take to roll out Currents?

  Your first run shows up in Currents a few minutes after you install the reporter. From there, roll it out one CI pipeline at a time: add the record key to each job, invite your team or turn on SSO, and connect GitHub and Slack so results reach your pull requests and channels. Crunchbase migrated in hours, and Runa connected several Playwright projects in about a day.

• We use Cypress today. Can we move to Playwright with Currents?

  Yes, and you don’t have to move all at once. Currents reports Cypress and Playwright tests side by side, so you can migrate one suite at a time. Most Currents case studies are teams that made this move. See migrating from Cypress.

• Is our test data secure?

  Currents is SOC 2 Type II audited. It supports single sign-on over SAML 2.0 with Okta, Microsoft Entra ID and JumpCloud, user provisioning over SCIM, and roles for every member. Data retention periods are published in the docs, and the Security & Trust page has the rest.