Review the evidence, not the diff.

Agents open more pull requests than your team can read. Currents links the evidence from every Playwright run to each one. Your agents fix what they broke. You decide what merges.

feat(checkout): one-tap pay with a saved card #482

agent wants to merge 8 commits intomainopened 02:14

41 files · 1,596 lines · about 4 hours to read

41 files changed, with 1,284 lines added and 312 removed.

Viewed 2 of 41 files

About 4 hours to go at 400 lines an hour

Currents Tests1,204 passed · 0 flaky · 6m 12s

RequiredPassed
Before · Run #1Run #1 · Card declined, with its video and trace
After · Run #2Run #2 · Order confirmed, with its screenshot

checkout › pays with a saved card

Last 30 days

29 of the last 30 runs passed. The one failure was Run #1 at 02:15, before the fix.

agent commented at 02:31

The saved card was charged before its token loaded. Fixed in pay.ts.

The fix is three lines in src/checkout/pay.ts: two added, one removed.

Touches payments, so it waits for a human read.

Review required · 11 files, about 45 minutes

  • Cursor
  • Red Hat
  • Autodesk
  • Snowflake
  • n8n
  • ServiceNow
  • LangChain
  • US EPA
  • Palo Alto Networks
  • Canadian Red Cross

Code got cheap. Knowing it works didn't.

Stripe merges over 1,300 pull requests a week with no human-written code. A year after companies adopt coding agents, pull requests per engineer are up 36%, and review takes 56% longer.

One dot for each of the 1,300 pull requests Stripe merges in a week. The first row, 53 of them, is what one reviewer can read line by line in a 40-hour week:40 hours × 400 lines an hour ÷ 300 lines a pull request ≈ 53

The work of checking code didn't go away. It moved.

An agent checking its own work isn't verification

The checking can't move to the agent that wrote the code. An agent can make a red test pass without fixing anything. To tell a real failure from a flaky one, it needs a record it didn't write.

Agent alone

  • It sees one local run and a CI log, so it guesses.
  • It adds a wait or loosens an assertion until the test passes.
  • The check goes green. The bug stays.

Agent + CI evidence

  • It reads the test's history across runs: 29 of the last 30 passed, none flaky.
  • It reads the error and the trace that CI recorded.
  • That's evidence the agent didn't write, so it fixes the code and leaves the test alone.

From reading code to reading evidence

Verification engineering is the practice of proving that a change works with evidence from tests that run in CI, instead of a person reading every line. Before agents, that reading was the bottleneck. With agents, the bottleneck is CI running the tests and someone reading the evidence. People keep both ends: deciding what to build and deciding what merges.

Sumit Saurabh explains why the work moved and how Currents handles it.

Before agents

  1. Decide what to build
  2. A person writes the code
  3. The old bottleneckA person reads every line
  4. Merge

With agents

  1. You decide what to build
  2. An agent writes the code
  3. The new bottleneckCI runs the tests, someone reads the evidence
  4. You decide what merges

Fails? The agent fixes it and pushes again.

From red build to proven fix

The agent's pull request #482 fails CI. It checks whether the failure is real, fixes it and puts the proof on the pull request.

  1. CI fails on the agent's pull request

    One test fails on Run #1: checkout › pays with a saved card. The Currents check is required, so merging is blocked.

  2. The agent checks history, then reads the trace

    The test hasn't flaked in 30 days, so the failure is real. The agent reads the error and the trace over MCP and the Trace API: about 1,600 tokens for that one trace instead of about 20,000.

  3. It fixes three lines and re-runs

    The saved card was charged before its token loaded. The agent adds the missing await in src/checkout/pay.ts and re-runs the test: 1 passed.

  4. It posts the before and after on the pull request

    Run #1's declined card sits beside Run #2's confirmed order. Reviewers open both without a Currents login, until the link expires.

    Put evidence on every agent PR

    14-day free trial. No credit card required.

You decide what merges

11of #482's 41 files are yours to read

Payments, the migration and the tests. About 45 minutes instead of 4 hours.

The other 30 merge on 1,204 passing tests.

You set which files people read and what the rest must pass. Each rule lives in one place.

  • People read what's risky

    The paths you name wait for a review from their owners.

    Set in CODEOWNERS and branch protection · GitHub

  • Red can't merge

    A failing Currents check blocks the merge button, for agents and people alike.

    Set in Branch protection · GitHub

  • Flaky tests don't decide

    A quarantined test still runs and its failure doesn't fail the run. Give a rule an expiry date, and Currents alerts Slack or email before it lapses.

    Set in Currents Actions

  • Agents get what you approve

    An agent's access is capped by the role of the person who connects it, and you can revoke it.

    Set in Connected Applications · Currents

For your agents

The Playwright Best Practices skill teaches agents locators, web-first assertions and debugging flaky tests. Installs from GitHub, no Currents account needed.

Playwright Best Practices skill

For your security review

  • SOC 2 Type II
  • SAML SSO and SCIM · Business
  • Data redaction · Enterprise
  • Your own storage or on-premises · Enterprise
Security and trust

Connected to every step, from push to merge

Each run's evidence lands where the next person or agent already works.

Runs in the CI you have: GitHub Actions, GitLab, CircleCI, Jenkins and more. CI setup docs (opens in a new tab)

Ship more pull requests. Read fewer diffs.

  • FundGuard

    Time to a verdict

    From about 80 min to 40min

    FundGuard's pipeline, halved by Currents Orchestration. Its CI bill fell 70%.

    Read the FundGuard story
  • n8n

    Trust in tests

    From about 2 to 3% to 0.3%

    n8n's flaky rate, before and after its move to Playwright with Currents.

    Read the n8n story
  • Trace API

    Evidence an agent can use

    From about 20,000 tokens to 1,600tokens

    One failing trace, pasted whole versus read through the Trace API.

    See the launch example
“It’s easy to go in, see what’s trending as flaky, line it up with traces, and understand when and why it was introduced.”
Declan Carroll / Senior Quality Engineer at n8n

Three steps to merging on evidence

Minutes from signup to your first recorded run.

  1. Record every run

    Start a trial, then add the reporter and your project's keys to CI.

    Start a 14-day free trialRead the setup guide
    Prompt for your agent
    Set up this repository to report test results to Currents. Read https://docs.currents.dev/getting-started/setup-with-an-agent.md and follow it.
  2. Gate the merge

    Install the GitHub App and make the Currents check required. GitLab and Bitbucket too.

    GitHub App docs
    Pull request
  3. Connect your agent

    Add the Currents MCP server and sign in. Your agent reads failures, history and traces.

    Connect Cursor, Codex or ChatGPT
    Terminal
    claude mcp add --transport http --scope user currents https://mcp.currents.dev/mcp

Questions teams ask

You shouldn't have to read every line