Currents - Currents for Claude & Codex to see all your tests

Currents records every Playwright test run in CI. Now Claude and Codex can read it. Connect from the Claude or ChatGPT/Codex plugin directory, sign in, and ask why CI failed. Your agent gets the failure, its history and the trace. Automatically.

Add a comment

Replies

Best

The 4 calls and ~1,600 tokens vs 20k for the raw trace is the number that sold me. Most MCP test tools I've seen just dump everything into context. Curious how it handles a monorepo where several Playwright projects report into the same run, does the agent get the failures grouped per project or all mixed together?

 Grouped, not mixed. Each Playwright project becomes its own group in the Currents run, so several projects that report into one run stay apart.

When the agent reads the run, every failed spec file comes with the project it ran in, and the run details have pass and fail counts per project. Failures with the same error are grouped too, so one broken shared helper doesn't show up as 30 separate problems.


The run summary has no per-project filter, but the agent can open any single spec file or test on its own. And if your packages are separate products, you can give each one its own Currents project, which keeps their test history apart as well.

Seeing whether a test failed before the current change is the detail that stands out. That bit of history can save a detour into fixing code that had nothing to do with the red build.

 Agreed, it's the cheapest check with the biggest payoff. The history answers three different questions:


- Failed on main before your change too: not your PR. Fixing it in your branch is the detour.


- Passed on main, fails only on your branch: most likely your change.


- Flips between pass and fail on main: a flaky test. A real problem, but a separate one from your PR.


But always compare the error, not only the status. The same test failing with a new error on your branch can still be yours.


Today the history is a tool the agent can call, not a fixed step in the skill. If you want it every time, put it in the prompt: "before you change anything, check if this test failed on main in the last 2 weeks."

congrats on the launch sumit. to your question, today its me first, and honestly the agent mostly reads what i copy paste from the log. what i would want is a short list after the run, which failures it fixed alone and which it left for me. i read that before merge, not the whole log. is something like this there?