Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Record without the Currents CLI

Record a session with the Currents MCP tools when the agent cannot run the currents command

Some agents cannot install npm packages, so they cannot run the Currents CLI. If the agent is connected to the Currents MCP server and has a shell, it can still save its screenshots, traces and logs as a session, and give you one link to them. An agent with no shell cannot upload files: it can only report the screenshots and page snapshots it has, and say that it did not record a session.

What you need

  • The agent connected to the Currents MCP server, with permission to write runs (runs:write) and to create share links (shares:write). You approve these permissions when you connect the agent. See Connect your agent.

  • A shell, to upload the files, for example with curl.

Ask the agent

Use the Currents browser-evidence skill. Record the checkout bug at
http://localhost:3000 as a Currents session and give me the link.

The skill has the steps: the agent creates the session through the MCP server, uploads its files from the shell, and creates the share link.

Claude Code with only the Currents MCP server and a shell, sped up:

A terminal: Claude Code calls currents-create-session with four files, uploads each file with curl, calls currents-create-share-link, and replies with the session and its share page link

What you get

The Markdown version lists the session, its commit and pull request, and a link to each file. For a trace, it has a short text summary with each action, page errors and console errors. Another agent can check the work from it without opening the files.

The Markdown version of a session: status, git details, each attachment with its link and caption, and links to the trace digest, frames, snapshots and failed requests

Last updated

Was this helpful?