Record with your agent

Your coding agent can record a browser test itself. It drives your running app, checks each step against the page, and proves the saved test passes.

What the agent does

The agent does not need the studio and nobody has to click Record. It opens a browser on your machine, runs the steps of the flow one batch at a time, reads the page after each batch, and finishes with a replay. The result is the same kind of test you record by hand: a plain Playwright file in your repository, with a video.

The requirements are the same as for recording by hand. See Before you start.

Connect the recorder

For Claude Code, one command does it:

verifaied setup claude

It registers the recorder as an MCP server named verifaied-recorder. For another agent, run verifaied setup codex, verifaied setup cursor or verifaied setup antigravity and follow the steps it prints. The command your agent has to launch is:

verifaied test mcp

If the recorder's tools answer that it is not ready, do what the answer says, such as logging in, then reconnect the server in your agent.

The recorder's tools

ToolWhat it does
list_testsLists the browser tests the branch already has, with each one's status and pre-steps, so the agent reuses an existing login instead of recording another.
start_recordingOpens a recording browser on your running app and returns the page. Takes the test's name, a start path or URL, and pre for tests to replay first. The browser is hidden by default; headed opens a window so you can watch.
run_stepsRuns up to 10 steps in order against the live page and stops at the first one that fails. A step is an action, an assert, a script or a pause. Any step can carry a caption, and an assert can carry hold_seconds.
read_pageReads the page again as it is now, for when it changed without a step being run.
delete_stepRemoves one step from the flow being recorded.
finish_recordingSaves the test to your repository, replays it with video, and returns the file's path, whether the replay passed and a link to the test's page.
cancel_recordingEnds the recording without saving. A first recording is removed; a re-recording leaves the saved test as it was.

Ask for a test

Say which flow you want, what to check and what the test is called. For example:

Record a browser test called "Settings/Create an API token".
Replay "Auth/Log in" first, then open /settings, create a token
named "scratch" and check that it appears in the list. Finish the
recording and tell me whether the replay passed.

The verifAIed skill teaches your agent to use the recorder for this. See Agent skill and instructions.

What you see

  • The recording draws live on the web, step by step, like one you make yourself.
  • The replay that follows is labelled Agent wherever runs are listed.
  • The agent writes the caption for each step and the hold after each check.
  • The recorder makes one recording at a time. The agent has to finish or cancel one before it starts the next.