Currents
Test results dashboard and analytics for Cypress and Playwright CI runs
Currents now lets agents walk a Playwright trace instead of downloading it.
◆Recent moves
- 3d ago
[New] Trace API for agents
⚡ SPARKThe trace API is the deepest layer of the agent-access arc so far: after failure links, OAuth MCP and run attachments, agents can now navigate the full Playwright trace. It turns Currents' richest debugging artifact into something an agent can query.
View source ↗ - 10d ago
[New] Run attachments
Runs can now carry server logs, build output and merged reports, all collected on a new Attachments tab. That widens the failure context Currents holds, which is the raw material its MCP server and agent-readable failure links depend on.
View source ↗ - 17d ago
[New] Remote MCP Server with OAuth
A hosted MCP endpoint with browser OAuth replaces pasting an API key and installing a package. It lands six days after personal access tokens and continues the run of releases that shorten the path from a coding agent to Currents failure data.
View source ↗ - 23d ago
[New] Personal Access Tokens
Personal Access Tokens replace the shared org-wide API key with per-user tokens that carry scoped permissions and enforced expiry — a security model upgrade that makes API access auditable and least-privilege by default.
View source ↗ - 1mo ago
[New] Shareable AI context for test failures
⚡ SPARKCurrents can now generate a shareable link for any Playwright failure — a human-readable page, or append `.md` for a structured Markdown document that AI agents can fetch with no authentication. This is the first explicit machine-readable API surface Currents has built for agent consumption.
View source ↗ - 2mo ago
[Improved] Better Slack notifications for CI test runs
Slack notifications gain clearer CI run summaries, recovery alerts when previously failing tests pass again, AI-assisted fix suggestions, and automated report delivery — making the Slack channel a more actionable CI status surface.
View source ↗