IDE Extension
See CI runs and failures in VS Code or Cursor, and send a failure to your AI agent with its full context
The Currents extension shows your CI runs, failures and flaky tests in the editor, and sends a failure to your AI agent with its full context. It works in VS Code, Cursor and other editors that use the Open VSX registry.
You need:
A Currents account in an organization, or an API key
VS Code 1.85 or later, or Cursor
Install the extension
Open VSX Registry (Cursor and other VS Code forks)
Or search "Currents" in the Extensions panel of your editor.
Sign in and pick a project
Open the Currents panel in the Activity Bar.
Click Connect to Currents and sign in from the browser. On a remote machine, run Currents: Copy Sign-In Link and open the link yourself.
Select a project. Its runs appear in the panel.
Where a browser sign-in is not practical, run Currents: Set API Key and paste an API key instead. If you keep both, the extension uses the sign-in.
See CI failures
Run Feed
The latest CI runs, refreshed every 30 seconds.
Filter by branch, author, tags, or status
Toggle auto-refresh on or off
Load older runs on demand
Pull Requests
CI failures grouped by pull request, with a timeline of commits and builds for each one.
Filter by branch, author, tags, or status
Toggle auto-refresh on or off
Run Details
Every spec and test of a run, with errors and stack traces for failed tests.
Fix All Issues and Fix with agent: see Fix with AI
Go to file: jump to the test file and line in one click
Trace Viewer: open the Playwright Trace Viewer inline (see Inline Trace Viewer below)
Open in Dashboard: open the full Currents dashboard for deeper analysis of the run, spec, or test attempt
Fix failures with your agent
Fix with AI
The Fix actions send your editor's AI agent a prompt with the failure context: the error and stack, the test's history, and the error-context snapshot: the page's accessibility tree at the moment of failure.
Fix with agent on a test
That test's context
Fix all failures in spec on a spec file
The failed tests of that spec file, or its flaky tests
Fix All Issues on a run
The failures of the whole run
Fix With Agent in Test Explorer
The flakiness rate or average duration, for the agent to look into via MCP
In an editor without a built-in chat, the prompt is copied to the clipboard.
Analyze with Currents
Analyze with Currents appears above every test, it, describe and context in your code. It asks your agent to check the test's recent results in Currents for failures, flakiness and slowdowns, and to plan a fix. It is also a Quick Fix (Cmd+. or Ctrl+.) on any test line.
The Currents MCP server
The extension adds the Currents MCP server to the editor, connected as you, so the agent can ask Currents for more after the first prompt. Signing out removes it. Turn this off with currents.registerMcpServer if you set up the MCP server yourself.
View a trace
Inline Trace Viewer
Click Trace Viewer on a failed attempt to open the Playwright Trace Viewer in an editor tab, next to your code. The trace streams from Currents, so there is nothing to download. Another trace opens in the same tab. Open in browser opens it in a browser window.
Explore flaky and slow tests
Test Explorer lists the flakiest and slowest tests of the project over 14, 30, 60 or 90 days.
Sort by flakiness rate or average duration
Jump to the test file and line in one click
Send flaky or slow tests to AI for analysis and automated fixes
Open in Dashboard for historical trends
Settings
currents.filterByCurrentBranch
false
Auto-filter runs by the current git branch when a project is selected
currents.notifyOnRunComplete
false
Show an OS notification when a run finishes
currents.analyzeTestDisplay
always
Show "Analyze with Currents" above each test (always) or only as a Quick Fix (quickfix)
currents.apiBaseUrl
https://api.currents.dev/v1
API base URL (for self-hosted or enterprise setups)
currents.registerMcpServer
true
Auto-register the Currents MCP server for AI agents
Last updated
Was this helpful?