← Files CurrentsARCHIVED FILE
plugin.json
6.43 KB · Nov 3, 2026 · 19:02 UTC
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "currents",
"version": "1.0.1",
"description": "Fix failing tests. Prove PRs.",
"author": {
"name": "Currents Software Inc",
"email": "support@currents.dev",
"url": "https://currents.dev"
},
"homepage": "https://currents.dev",
"license": "MIT",
"extensions": {
"com.openai": {
"interface": {
"displayName": "Currents",
"shortDescription": "Fix failing tests. Prove PRs.",
"longDescription": "Currents gives AI agents the test results your CI records, from Playwright, Vitest, Jest and more.\n\nSelf-healing tests\n\u2022 Ask why a run failed and get the errors, stack traces, screenshots and traces behind it\n\u2022 Step through a run's Playwright trace, action by action, to see what the page did\n\u2022 Find the root cause and fix the test, flaky ones included\n\u2022 Compare a pull request's runs with main to see what the change broke\n\nProof of work for any change\n\u2022 Before-and-after screenshots, videos, Playwright traces and DOM snapshots from CI\n\u2022 A demo the agent records in a browser, saved as a run\n\u2022 Evidence links posted in the pull request, so reviewers see the change working\n\nTest suite health\n\u2022 Rank your flakiest and slowest tests and spec files\n\u2022 See which errors break the most tests\n\u2022 Quarantine, skip or tag tests with rules, and review what they affected\n\nDay-to-day CI work\n\u2022 Reproduce a bug from a failed run and verify the fix\n\u2022 Open an issue for a failure in your issue tracker\n\u2022 Cancel, reset or re-check runs without leaving the chat\n\nFor teams whose CI slows them down: flaky tests that block merges, failures nobody has time to dig into, and AI-written pull requests that are hard to trust without seeing the change work. Works with GitHub, GitLab, Slack, Jira, Linear and more. You need a Currents account.",
"developerName": "Currents Software Inc",
"category": "Developer Tools",
"capabilities": [
"Find the root cause of failing tests",
"Fix flaky tests",
"Compare pull request runs with main",
"Find runs by branch, commit or pull request",
"Follow a test's history across runs",
"Rank flaky and slow tests and spec files",
"See which errors break the most tests",
"Quarantine, skip and tag tests",
"Review which tests a rule affected",
"Explore Playwright traces step by step through a trace API",
"Collect screenshots, videos and traces from CI",
"Capture real DOM snapshots as evidence",
"Record a browser demo of a change",
"Attach high-fidelity proof to pull requests: videos, traces and DOM snapshots of the change working",
"Create expiring share links to traces",
"Reproduce bugs and verify fixes",
"Open issues for test failures",
"Cancel, reset and delete runs",
"Cancel GitHub Actions workflows from a run",
"Integrate with Linear, Jira, Slack and more"
],
"websiteURL": "https://currents.dev",
"privacyPolicyURL": "https://currents.dev/privacy-policy",
"termsOfServiceURL": "https://currents.dev/tos",
"logo": "./assets/logo.png",
"composerIcon": "./assets/logo.png",
"supportURL": "https://docs.currents.dev/resources/support"
},
"review": {
"test_cases": {
"positive": [
{
"description": "Ranks the flakiest tests in a project",
"prompt": "Which tests in the currents-e2e project were the flakiest over the last 30 days?",
"tools_triggered": "currents-get-projects, currents-get-tests-performance",
"expected_behavior": "Lists the flakiest tests in currents-e2e, each with its flaky rate and number of executions for the last 30 days."
},
{
"description": "Explains why the latest failed run failed",
"prompt": "Why did the latest failed run in currents-e2e fail?",
"tools_triggered": "currents-get-projects, currents-get-runs, currents-get-context",
"expected_behavior": "Names the failed run, the tests that failed and the error message and stack trace for each failure."
},
{
"description": "Collects evidence for a failed test",
"prompt": "Show me the screenshots, video and trace for a failed test in the latest failed currents-e2e run.",
"tools_triggered": "currents-get-runs, currents-get-test-evidence, currents-create-evidence-links",
"expected_behavior": "Returns links to the screenshots, video and Playwright trace recorded for the failed test."
},
{
"description": "Quarantines a flaky test",
"prompt": "Quarantine the flakiest test in currents-e2e.",
"tools_triggered": "currents-get-tests-performance, currents-create-action",
"expected_behavior": "Creates a quarantine rule for that test in currents-e2e and reports the rule name and the test it matches."
},
{
"description": "Deletes a run",
"prompt": "Delete the most recent run in mcp-review-project.",
"tools_triggered": "currents-get-projects, currents-get-runs, currents-delete-run",
"expected_behavior": "Asks for confirmation, then deletes the most recent run in mcp-review-project and confirms that it was deleted."
}
],
"negative": [
{
"description": "Unrelated question about the weather",
"prompt": "What is the weather in Paris tomorrow?"
},
{
"description": "General coding task with no test results involved",
"prompt": "Write a Python function that reverses a string."
},
{
"description": "Request for a different CI product",
"prompt": "Restart my last Jenkins build."
}
]
},
"demo_recording_url": "https://s3.amazonaws.com/currents.dev/currents-chatgpt-app-demo.mp4"
},
"publication": {
"release_notes": "First release of the Currents plugin: debug failing and flaky tests, collect proof of work for pull requests and manage CI runs from ChatGPT and Codex."
},
"apps": "./.app.json"
}
}
}
SHA-256: cec4314cf33a8268618aa0a9dc5f1d269173e444104c0e640e679ed9c7530352