LoginSign Up
← Back to all sparks
C

Currents

INFRA · APIS
Velocity3.8

Test results dashboard and analytics for Cypress and Playwright CI runs

currents.dev ↗

Currents positions itself as the CI intelligence layer that AI coding agents query when fixing broken tests.

ai-agent-nativeplaywright-testingci-intelligenceide-integrationdeveloper-tooling
◆Current state
Currents is executing a clear pivot toward agent-native CI workflows. The shareable AI failure context (a link that surfaces the full failure context at a `.md` endpoint, no login required) and the VS Code/Cursor IDE extension both explicitly target AI coding agents as consumers of test intelligence — not just human developers. The Slack integration adds AI-assisted fix suggestions. Pricing moved to a self-serve Business plan with fairer overage and yearly pooling, lowering the friction to get more users inside the platform.
◆Where it's heading
Currents is repositioning from a Playwright test dashboard to the CI intelligence layer in AI-assisted development workflows. The bet is that AI coding agents (Cursor, Claude, Copilot) will become the primary consumers of test failure data, and Currents wants to be the authoritative source they query. The .md endpoint on failure links is a minimal-friction agent integration; the IDE extension closes the loop by putting that intelligence directly in the agent's editing context.
◆Prediction
A structured MCP server or direct agent API is the logical next step — the .md URL endpoint is Currents testing whether agents will actually consume failure context, and if usage confirms it, a more formal agent integration surface will follow. Additional IDE integrations (JetBrains, Neovim) are likely.

◆Recent moves

  1. 8d ago

    [New] Shareable AI context for test failures

    ⚡ SPARK

    Currents now lets any Playwright failure be turned into a shareable link with an `.md` variant that an AI agent can fetch without a Currents login — making test failure context directly consumable by coding agents as part of their fix loop. This fits the trajectory of Currents building the CI intelligence layer that agents query rather than the dashboard humans review.

    View source ↗
  2. 1mo ago

    [Improved] Better Slack notifications for CI test runs

    Slack notifications for CI runs are overhauled to include clearer test outcome summaries, recovery alerts, AI-assisted fix suggestions, and automated reports. The AI-assisted fixes in Slack align with Currents' broader push toward surfacing test intelligence in the tools developers already use.

    View source ↗
  3. 1mo ago

    [Improved] New Pricing Plans

    Currents cuts prices, adds a self-serve Business plan, expands user counts, and replaces hard overage with yearly usage pooling. The self-serve Business tier is the most impactful change — it removes a sales step that was blocking mid-market adoption.

    View source ↗
  4. 1mo ago

    [New] Currents IDE Extension

    ⚡ SPARK

    The VS Code and Cursor IDE extension brings CI test results, failure context, and Playwright traces directly into the developer's editor — and explicitly supports AI agent workflows by letting agents access failure details without switching to the Currents dashboard. This is the first surface Currents owns inside the IDE itself.

    View source ↗
  5. 2mo ago

    [New] Integration with Linear

    Test failure details can now be pushed to Linear issues directly from Currents, with explicit support for human or agent-driven troubleshooting workflows. A straightforward issue-tracker integration that widens the surface where Currents failure context shows up.

    View source ↗
  6. 3mo ago

    [New] @currents/playwright 2.0 - Playwright 1.60+ Support

    The @currents/playwright package reaches 2.0 with full support for Playwright 1.60+, keeping compatibility current with the upstream framework. A necessary maintenance release for teams running Playwright's recent versions.

    View source ↗