Playwright tells you what failed. Now Currents tells you why. Open a failed test and our specialized agent gives you the root cause and a fix to try. It combines failure information with execution steps, network logs and test behavior before and after a failure.

  • Get the root cause of a failed test without opening the trace
  • Get suggested fixes, each with a confidence level
  • Watch what the agent checks while it works: the trace, the requests, the screenshots
  • Ask what any test does, passed or failed
  • Copy the answer into a pull request, an issue or your coding agent's prompt
  • Available now on every plan
A Playwright error says what failed but not why. The agent reads the Playwright trace, step by step, and writes the likely cause with a suggested fix. On real CI failures it found the right cause 81% of the time, against 6% from the Playwright output alone.

When a test fails, expand Likely cause of the failure in the test's Insights panel. The agent goes through the Playwright trace and comes back with the type of failure, the root cause in a few sentences, and fixes to try. The answer stays with the test, so the next person who opens it doesn't have to ask again.

The likely cause of a failed test

How we tested it

A wrong root cause is worse than none: you lose an afternoon chasing it. So we measured the agent before turning it on for everyone.

We took real CI failures from real production runs, each with a verified cause, and compared what an AI reading only the Playwright error output found with what our agent found:

  • Right root cause: 6% without Currents, 81% with Currents
  • Wrong root cause: 52% without Currents, 3% with Currents
  • First suggested fix fixes the cause: 11% without Currents, 76% with Currents
  • Suggests a fix that only hides the bug, like a longer timeout or a retry: 17% without Currents, 6% with Currents
Root cause and fix, with and without Currents

The gap is the same for app and backend bugs, test data problems and timing issues. A backend bug barely shows in the Playwright error, but it does show in the network log.

Right cause, by type of failure

The work went into what the agent reads, the tools it uses to dig through the trace, and the model behind it. Tests without a Playwright trace get an answer from the error and steps alone, so expect less from those.

Enabling AI assistance

AI analysis sends test data to an AI provider, so an admin turns it on once for the whole organization: open the organization settings, select AI and data, and turn on AI assistance.

Want an agent to fix the failure in your code as well? Connect it to the Currents MCP server. It reads the same failure data and works in your repository.