Currents now posts its comment on the pull request when the run starts, and edits it in place as the run continues. The header line shows the result, the number of tests and groups, the Playwright version, the duration and the commit. The groups table lists failed groups first, then flaky, in progress and passed groups.
Failed tests
Each failed test shows its spec file, browser, attempt, duration and error line. Under it, a history line says how the test did in the last 30 days, overall and on main:
Last 30 days: failed 1 of 3 · flaky 0% · on main: failed 1 of 3
With context links on, each failed test also gets:
- Trace filmstrip — a preview of the trace, with the failure frame marked in red
- Links — Trace, At failure, Page at failure, Screenshot, Video, Error context and Context for agents
With context links off, the test links to its result in Currents and to the trace of the failed attempt. Both need a Currents sign-in.
Fix with AI
The comment ends with a Fix with AI section:
- For you — one link to the share page, which hands the failure to Claude Code, Cursor, Copilot or 4 more tools
- For your agent — a prompt to paste, in a code block with a copy button:
Fix the failed tests in <share URL>.md - Full prompt with failure context — the whole prompt, in a collapsed section
The last line says that the context links are public, and when they expire. With context links off, the prompt names the run ID instead, and works with an agent connected to the Currents MCP server.
New settings
The GitHub integration settings have three new options:
- Context links — on by default, set for each repository
- Link lifetime — 1, 3 or 7 days, 1 day by default
- Post when — always (the default), when the run has failures or flaky tests, or only when it has failures
In every mode, a green re-run updates the red comment that is already on the pull request.
Learn more: