Currents - Currents for Claude & Codex to see all your tests
by•
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.


p/many-displays
p/runevr
p/producthunt
p/google-cloud-platform
p/reso
p/kodlo
p/ai-context-flow
p/htmldrag
p/dex-by-exmergo
p/jot-2-0
p/beamfy
p/refs
p/dino-kids
p/nexupira
p/duckfightclub
p/nudgeforme
p/seshka
p/talanoa-2
p/murror
p/supabase
Replies
Hi Product Hunt!
I'm Sumit from Currents.
Currents records every Playwright test run in your CI: the errors, the steps, the traces, screenshots and videos, and the history of each test.
Until now, people read that record in our dashboard.
Now Claude and Codex can read it too.
Why we built this
I watched the same loop happen again and again this year. An agent writes the code and runs the tests on its machine. It says "done". Then CI goes red on the PR, and the agent doesn't know, because it can't see CI. So a person opens the dashboard, finds the failed test and pastes the error back into the chat. The agent guesses a fix, and the loop starts again.
Writing code got fast. Proving that the code works did not. The person who copies errors from CI into the chat became the slowest step.
But the odd part was: Currents already had the answers. Did this test fail before this change? Does it fail only in CI? Did other tests fail with the same error? It was all in the record. But the record lived in a dashboard, and agents don't open dashboards.
So we spent the last few months on the agent side of Currents. We shipped a hosted MCP server with OAuth sign-in. We shipped a Trace API, so an agent can read a Playwright trace one piece at a time. In our launch example, that took 4 calls and about 1,600 tokens. Every file in that trace comes to about 20,000.
The last gap was setup. An MCP server helps nobody if people can't find it, or if they first have to copy a server URL and an API key into a config file. So we listed Currents in the Claude directory and in the ChatGPT/Codex plugin directory. You find it, click connect and sign in.
What you can ask
"What broke in the last failed run on main? Open a Jira issue for it."
"Which tests were flakiest on main this week, and why?"
"Is this pull request safe to merge? Compare its runs with main."
The plugin also brings three skills:
fix-failing-tests finds the failed run, reads each failure with its steps and trace, fixes the cause, runs the test again and asks before it commits.
collect-evidence finds the run before your change and the run after it, and writes up both with links.
browser-evidence (experimental) records the browser before and after a change and shares the link.
You act as yourself, so your Currents role decides what the agent can do.
Who it's for
Teams that run Playwright in CI and work with Claude, Claude Code, ChatGPT or Codex. The Claude listing works on every Claude plan, including Free. Currents has a 14-day free trial, and you don't need a credit card.
What I'd love from you
Try it, and tell me where it broke or where it confused you. I also have a question for you: when an agent's PR fails in CI today, who reads the failure first, you or the agent?
I'll answer every comment today, and so will the team.
Claude: https://claude.ai/directory/currents
ChatGPT and Codex: Open Plugins and search for "Currents", click connect and just sign in!
Docs: https://docs.currents.dev/ai/connect
Also, if you are participating in the puzzle, just drop your answers down in the comments.
See you in the dashboard, or your nearest AI agent!
@sumitsaurabh927 the agent, for us. our ci is off right now so the checks run locally and the agent reads the failure first. anything near payments I still read myself
what does it do when the test itself is out of date?
@leoheo Good question! It updates the test. The rule the agent follows is "change the code or the test, whichever is wrong", and keep the change to what the failure needs.
To tell which one is wrong, it reads what Currents recorded at the failure: the error, the steps before it, and the page as it was at that moment. Then it compares that with your code changes.
Example: a PR renames "Sign in" to "Log in". The test fails because it can't find "Sign in". The page snapshot shows a "Log in" button and the diff shows the rename, so the agent fixes the test, not the app.
When it's less clear, like the app now shows a different total, the report says which side it changed and why. It also doesn't commit anything unless you ask, so you make the final call.
@sumitsaurabh927 ok the rename example cleared it up, thanks
when the agent reads the failure does it ever just retry until green instead of fixing anything
@igorblink Good question, and yes, agents do this. When all an agent has is "CI is red", a rerun or a bigger timeout is the cheapest guess that turns it green.
Two things push against that with Currents:
1. The fix-failing-tests skill the agent reads first has an explicit rule: fix the cause, not the symptom. No adding retries, raising timeouts, or skipping or quarantining a test unless you ask for it. If the cause is outside the code (the environment, a third-party service, test data), it should say so instead of editing the test.
2. It doesn't rerun to find out what failed. It reads the run Currents already recorded: the error, the steps before it, the trace and screenshots. For a test that passed on retry, it reads the failed attempt too, and has to say whether that flake is worth fixing now and why.
Congrats on the launch! Looks like a promising product! 🎉👍
@madzadev Thank you so much!
I'd love for you to try it out!
Congrats on the launch @sumitsaurabh927 and the @Currents team! 🎉
@camelcaseguy Thanks a ton! 🚀
Can agents file issues to Linear over MCP too?
@relli7 https://docs.currents.dev/resources/integrations/linear
Cool product, congratulations on the launch🚀
@dunsin Thank you Duns!
The "did this test fail before my change?" bit is the part that stuck with me. That's the first thing I check when a CI run goes red, and it's usually the difference between a real regression and chasing a flaky test. Giving the agent that history instead of just the raw trace feels like the right shape for this.
I've had many failed CI runs on main hold up deploys this month, and honestly a lot of the time the Agent reads the failed workflow before I do! Question: a job that times out with every test passing... does that show up as a failure? Congrats on the launch
Congrats on the launch! Gonna try this on our project. We’ve got a ton of unit and e2e tests, and tbh a lot of them are garbage at this point 😅
Any plans to go beyond observability and use the run data to actually help clean up the tests? Like telling us which ones are useless, duplicated, or just flaky noise. That’s the part I’d pay for.
@hungrydog Thanks!
And "a lot of them are garbage at this point" is the most honest description of a test suite I've read today.
Part of this works today, because the plugin gives the agent your run history, not only the latest failure.
Two prompts you can try rightaway:
1. "Use Currents to list the 20 flakiest tests on main in the last 30 days. Read their failed attempts and group them by cause." That's your flaky-noise list, with a reason for each test.
2. "List the slowest tests, and the tests that ran 100+ times in the last 90 days without a single failure." That's your shortlist of tests to cut or merge.
Duplicates aren't in the run data, but the agent has your code too. Ask it to compare the tests on that shortlist and point out the overlap.
One caveat: "never failed" doesn't mean useless. A test that never fails isn't automatically good/bad.
The data gives you candidates, and someone who knows the code makes the call, so ownership is clear.
A proper "clean up my suite" report is exactly the feedback we hoped to get from this launch.
What does "useless" mean for your team: never fails, too slow, or already covered by another test?
I'll take your answer back to the team.
Also, I'd love to onboard you should you require any assistance in using Currents!