What Can an AI Agent Record? 12 Screen Recordings (2026)

Vorec Team · 2026-10-26 · About 9 min read

An AI coding agent can record almost anything you can click through in a browser: a demo of the app it just built, a how-to on a website like Google Sheets or Notion, a bug reproduction, a QA run, an onboarding tour, a Shopify admin walkthrough, and more. The agent plans the clicks, drives a real browser, and a desktop recorder captures the screen. This page lists 12 recordings you can ask for, with an example prompt for each, what an agent should not record, and which agents and models work. Facts about Vorec, which publishes this page, come from its CLI documentation and its Claude Code plugin as of 26 October 2026.

The short answer

An AI agent such as Claude Code, Codex, Cursor or Gemini CLI can record any flow it can drive in a browser. It writes a short manifest of steps (click, type, select, hover, scroll, wait, navigate, narrate), runs it, and a recorder app captures the window as an MP4. With Vorec, that recording happens locally on your Mac: nothing uploads and no credits are spent until you review the take and approve it. Then AI writes and voices narration matched to each tracked action, and you get an editor with zoom, cursor effects and freeze-sync timing, plus an optional written step-by-step guide. Good fits include product demos, website how-tos, onboarding tours, bug reproductions, QA runs, release videos, support answers, lessons, sales tours, Shopify admin guides, public website tours and translated versions. Recording needs macOS and the Vorec Recorder app. The model does not matter; any agent that runs terminal commands works.

12 things you can have an agent record

Each prompt below is something you type to your agent. Vorec's plugin sorts every request into one of four recording types (task tutorial, website tour, bug reproduction or UX review), which decides what the agent optimizes for: a clean successful path, purposeful scrolling, a faithfully preserved error, or observations without account-changing actions.

1. A product demo of the app it just built

"Record a demo of the new billing page on localhost."

When the agent can see your codebase, it works in Connected mode: it reads your components for selectors, validation rules and success states instead of guessing. You get an MP4 of the real running app, ready for narration. More detail in our guide to Claude Code demo videos.

2. A how-to on any website

"Record how to create a pivot table in Google Sheets."

For sites where the agent has no source code (Google Sheets, Canva, Notion, any SaaS), it uses Explore mode: it opens the live page, reads the accessibility tree and walks the full flow in a dry run before writing a single step. You get a task tutorial that ends on a verified success state.

3. An onboarding or first-run tour

"Walk a new user through signup and creating their first project."

The plugin resets state before recording so the video starts from a first-time-user view, and the agent fills forms with valid demo data. Narration describes what each field is for rather than reading out the made-up values.

4. A bug reproduction

"Record the steps that trigger the checkout error."

Here the goal flips: preserve the bug, don't hide it. Before recording, the agent pins down the initial state, exact steps, expected result, actual result and the visible error. You get a clip a developer can watch instead of reading a vague ticket. See video bug reports for dev teams.

5. A QA or regression run on staging

"Record the full signup flow on staging so I can review it."

Point the agent at your staging URL and it records the run end to end. The plugin's end-state checks make the agent read the screen before stopping, treat a disabled button as a validation signal, and fail loudly rather than quietly.

6. A release or changelog video

"Show what's new in this release: the export panel and the new filters."

The agent records each new feature in order, and `narrate` steps add explanation time where a screen needs context.

7. A support answer for a ticket

"Record how a customer changes their invoice email."

Short, single-task clips answer repeat tickets better than a paragraph of steps. Because Vorec can also produce a written step-by-step guide from the same capture, you can paste the text into the reply and link the video. More on one recording, two outputs.

8. A course or lesson clip

"Record how to set up a Notion database, step by step."

Lessons benefit from the plugin's pacing rules: narration length sets video length, and the agent groups clicks by intent so each segment teaches one idea.

9. A sales or investor tour

"Record a 90-second tour of the dashboard for investors."

A website tour picks three to five meaningful sections, scrolls to each with a visual goal, and avoids unnecessary form submissions. The plugin's own benchmark puts the sweet spot at one to three minutes.

10. A Shopify admin how-to

"Show how to create a product in our Shopify app."

Shopify embedded apps get their own Shopify Admin mode: the agent opens the app through admin.shopify.com, never through the raw tunnel or localhost URL, uses a dedicated browser profile, and records the full window so you can crop the Admin shell in the editor. If a Google login appears, the agent stops and asks you to sign in yourself.

11. A competitor or website tour for research

"Review the public pricing page on example.com and walk through the plans."

This is the UX review type: observations and friction points, with stop conditions for auth, payment and destructive actions, and no account-changing steps. Stick to public pages and respect the site's terms of use.

12. Localized versions in other languages

"Translate the narration of this project into Spanish."

After a project exists, the agent can read the English segments, write translations and push them back through the CLI, so you don't re-record the screen. Translation is available on eligible Vorec plans. See localizing tutorial videos without re-recording.

What an agent should NOT record

Keep these off the list:

• Live calls or meetings with other people unless everyone on them has consented. Agent recording is built for flows you drive, not for capturing other people.
• Pages behind someone else's login. Record your own accounts, your own apps, or public pages. The Vorec plugin never asks for passwords; when login is needed, you sign in yourself in a visible browser window and the agent reuses that saved session.
• Real passwords, card numbers or personal data. Use demo data and test accounts. Anything typed on screen ends up in the video.
• Google sign-in done by the agent. The plugin's rule is explicit: never automate Google login, spoof the user agent or inject cookies. You log in manually, then the agent resumes.
• CAPTCHAs or bot checks. Don't ask an agent to get past them. If one appears, finish that step yourself or record a different flow.
• Anything against a site's terms. If a website forbids automated access, don't point an agent at it.
• Real-world side effects you didn't intend. Discovery on live sites is meant to happen without placing orders, sending messages or deleting data.

Which agents and models work

Vorec doesn't depend on the model. Anything that can run `npx @vorec/cli@latest ...` in a terminal can plan the flow, record it and hand you the MP4. Model names below were confirmed from vendor pages on 26 October 2026.

For Codex specifically, the walkthrough in record app demos with Codex covers setup. Other approaches are compared in can an AI coding agent record your app demo.

How it works in 5 steps

1. Check. The agent runs `npx @vorec/cli@latest check` to confirm the Vorec Recorder app is running and signed in, Screen Recording permission is granted, `cliclick` is installed for a visible cursor, and your account has credits and project slots.
2. Write the manifest. After discovering the flow, the agent writes a `vorec.json` with the URL, viewport and actions. Each action has a short description (the timeline label) and a context line describing what is on screen, which is what the narration is built from.
3. Run locally. `npx @vorec/cli@latest run vorec.json` launches the browser, tells the recorder to capture that window, performs the steps and saves an MP4 plus an action sidecar to your disk. No upload, no credits.
4. Review the MP4. You watch the take. If it's wrong, the agent fixes the manifest and records again, still at no cost.
5. Analyze. Only after you approve, `npx @vorec/cli@latest analyze <mp4>` uploads it. Vorec writes and voices narration synced to each tracked action and returns an editor link where you can adjust zoom, cursor, captions and timing before export.

Quick answers

What can I record with an AI agent?

Any flow an agent can click through in a browser: product demos, how-tos on third-party websites, onboarding tours, bug reproductions, QA runs, release videos, support answers, lessons, sales tours, Shopify admin guides, public website tours, and translated versions of existing projects.

Can Claude Code record a video?

Yes. Install the `record-tutorial` plugin from the vorec-plugins marketplace and ask Claude Code to record a flow. The Vorec Recorder app does the capture; Claude Code plans and drives it.

Can Codex record a video?

Yes. Codex runs the same `@vorec/cli` commands. Add the Vorec snippet to your `AGENTS.md` so Codex knows the workflow.

Does it need a Mac?

Recording through an agent does: the Vorec Recorder is a macOS app. If you already have a screen recording made another way, uploading it to Vorec for narration works from any operating system in a browser.

What does it cost?

Recording locally with `run` spends nothing. Credits are used only when you `analyze` an approved take. Vorec has a free trial with no credit card required (current allowances on the pricing page), then Starter at $9 a month ($86 a year), Pro at $24 a month ($230 a year) or Business at $59 a month ($566 a year).

Ask your agent to record your first flow. Install the Vorec Recorder for macOS, add the Claude Code plugin or the CLI to your agent, and start a free trial with no credit card required (current allowances on the pricing page) needed. Get started with Vorec.

← Back to blog