Explore a trace
Give an agent a trace API link, and let it read a Playwright trace in small steps instead of loading the whole file. Get images of the trace for people: filmstrip, animation, frames and the page at th
This page works for traces from CI tests and from sessions an agent recorded. A Playwright trace records everything a test or a browser session did: every action, the page after each action, every network request, and a recording of the screen. A screenshot shows what the page looked like. The trace shows why.
A trace file is a zip of several megabytes, too large for an agent to read at once, and people need the Playwright trace viewer to open it. The Currents trace API solves both:
An agent reads the trace one small part at a time. It starts with a summary of the actions and the failure, then asks only for the page, request or screen that the summary points to.
People get images from the same API: a filmstrip, an animation, the screen at the failure, or the page as it looked then. Put them in a pull request or an issue. See Post evidence to GitHub, Slack and Linear.
The trace can come from Playwright Test, Playwright MCP, Playwright CLI, or Vitest browser mode with the Playwright provider (browser.trace: 'on', which writes to __traces__ next to each test file). Attach a local trace to a session to get a link for it. Anyone with the link can open it without a Currents login.
Get a trace API link
A failed test in CI
The Fix link of the test or run: an explore trace link next to each trace
As long as the Fix link
A failed test, and an agent connected to Currents
The failure context the agent gets from the Currents MCP server: the same explore trace link
12 hours
A CI run you shared
The Shared Run page and its Markdown version: a link for each attempt's trace
As long as the Shared Run
A pull request with a failed run
The GitHub run comment: a trace API link for each failed test
As long as the comment's Fix link
A session
The session page: Explore with agent on a trace. The session's Markdown version lists the link too.
As long as the Shared Session
Any test or session trace, from an agent
Ask an agent connected to the Currents MCP server for a trace API link
24 hours, or up to 7 days
For what each kind of link opens and who can open it, see Share links.
On a session page, Explore with agent on a trace copies a prompt with the trace API link, opens the trace summary, or opens the prompt in your coding tool:

Ask the agent
Paste the Fix link of a failed test, then:
For a session where an API response looks wrong:
To show the failure to people:
Example: a checkout that freezes
A session recorded a checkout where the discount code save10 leaves the Apply button stuck. The agent got the trace API link from the session page with Explore with agent. Times are milliseconds from the start of the trace.
The summary,
/digest, lists the actions. No action failed, but the page threw aTypeError33 ms after the click on Apply. About 450 tokens.The network requests,
/requests: all 3 returned 200 before the click, so the server is not the cause. About 300 tokens.The page text right after the error,
/snapshots/2464?format=text: the input holdssave10in lowercase, the button readsApplying…, and the total is still$229.50. About 100 tokens.The screen at the end,
/frames/4024: the button is still stuck. An image of about 750 tokens.
The agent used about 1,600 tokens. Every file in the trace together is about 20,000 tokens.
What the agent reads
The agent asks the trace API for one part at a time: the summary, the page text, the accessibility tree, the HTML, the network requests and their bodies, or the files in the trace. Trace API lists each route, with real output from a failed test.
An agent in a terminal does this with curl. It reads each answer and picks the next call from it, until it can answer. Here it reads the trace of the checkout example above:
Available formats
The trace API returns each part of the trace in more than one format: Markdown and JSON for agents, images and pages for people. Below are three you are likely to post in a pull request or an issue. Add the path in each example to the trace API link to get the same output.
Trace API lists every route and option, with real output for each: the summary, the screen at any time, the page as text, accessibility tree or HTML, network requests and their bodies, the files in the trace, and the trace zip.
Filmstrip
/filmstrip?end=failure&layout=row&width=480 returns the frames up to the failure in one WebP image, and outlines the last one in red. That is the frame /frames/failure returns: the last frame before the failure, which can be seconds earlier while an assertion waits. From a failed test that expected a total of $206.55 and got $183.60:

/filmstrip?end=failure&layout=row&width=480: the failed test up to the failureThe page at the failure
/snapshots/failure?format=html returns the page when the test failed, with the styles from the trace. The trace API removes the scripts, so buttons and links do nothing. The same failed test, opened in a browser:

/snapshots/failure?format=html: the page when the test failed, opened in a browserAnimation
/animation?format=gif&width=640 returns the recording as a GIF, 640 pixels wide. A test that runs for a few seconds has only a few frames, so this one comes from the checkout session above:

/animation?format=gif&width=640: the checkout session as a GIFGitHub shows these images in Markdown. Linear and Slack do not. See Post evidence to GitHub, Slack and Linear.
Last updated
Was this helpful?