for developers who build with Claude Code, Codex or Cursor

Watch what your AI built before you ship it.

When your AI finishes a change, it reports it to ReadyToEdit through the MCP: a short script of what changed and why, with a recording under each line. For a web app, it records the new flow in its own browser, with your OK; for anything else, you record it and point your AI at the file. You watch it as a Footage preview, and the line you do not follow is the one you ask about.

How it works

Your AI reports the change as a video.

  1. The change is recorded

    For a web app, your AI runs it and records the new flow in its own browser, with your OK, then uploads the file to ReadyToEdit through the MCP. For anything else, you record it and point your AI at the file.

  2. It writes the report as a script

    One line for each thing that changed: what it does now, why, and which file to open. The recording goes under the line it shows.

  3. You watch it as a Footage preview

    The lines play as one video. Pause on the part you do not follow and ask your AI about that line.

Start with show-what-you-built, one of the ReadyToEdit skills for Claude, Codex and Cursor. It all runs on Light, with about 10 footage hours of playback a month.

Claude Code, after a change

You: done? show me what you built

Recorded checkout-retry.mp4 · 0:48

Uploaded to ReadyToEdit

Assistant: Saved “Checkout retries a failed card” to ReadyToEdit, four lines. Line 2 plays checkout-retry.mp4 0:09–0:21: the card fails, the retry button appears, the second try goes through. The Footage preview is below.

You: why a button and not an automatic retry?

Assistant: Line 3 says it: an automatic retry could charge the card twice. The change is in checkout/retry.ts.

Works with Claude Code, Codex, Cursor and other assistants that sign in to an MCP server.
Fig. 1ExampleThe report, one chat after the change.

Footage preview

Four lines you can watch in a minute.

The report is a script: each line says one thing, and the recording plays under the line it shows. A line with nothing to show stays in the report, marked.

  1. 1A failed card now offers a second try.checkout-retry.mp4 0:00–0:09
  2. 2Here it is: the card fails, the button appears, the retry goes through.checkout-retry.mp4 0:09–0:21
  3. 3It waits for a press, because an automatic retry could charge twice.no clip on this line
  4. 4Open checkout/retry.ts to see the one place it changed.checkout-retry.mp4 0:36–0:48
Fig. 2ExampleThe report from Fig. 1, as the preview plays it.

Share it

One link, for whoever reviews the change.

The report opens without an account: the script, each line’s clip playing its own range, and the files. Paste it in the pull request, send it to a client, or keep it for yourself. When the change moves on, update the same link, or revoke it.

What it will not do

Known limitations.

  • Record your screen. For a web app, your AI records the new flow in its own browser, with your OK; for anything else, you record it and point your AI at the file.
  • Read your code. Your AI does, on your machine; ReadyToEdit receives the script and the recordings.
  • Watch or transcribe the recordings on Light. Your AI names the clip and range for each line, from the recording it made or what you tell it about yours.
  • Edit video. The preview plays your recordings in script order, as they are.
  • Review the code itself, or score the change.

Light

Your own AI, through the MCP

$20/month

Starts with a 14-day trial, no card.

About 10 footage hours of playback a month (2,250 credits), up to 3 projects.

Start your free trial

Creates your workspace and starts the trial.

Several recordings a week

Pro

Adds ReadyToEdit’s own AI

$149/month

About 120 half-hour recordings a month (25,000 credits), up to 3 projects.

Start your free trial

Starts with the Light trial. Choose Pro any day.

Team

Adds ReadyToEdit’s own AI

$299/month

About 288 half-hour recordings a month (60,000 credits), up to 10 projects.

Start your free trial

Starts with the Light trial. Choose Team any day.

Light is ReadyToEdit’s production workspace, with your own Claude, Codex or Cursor as the writer, connected through the ReadyToEdit MCP. Pro and Team add ReadyToEdit’s own AI.

After the trial, the workspace is read-only until a plan is chosen: everything in it stays, and links you sent keep working. Choose a plan in Settings, during the trial or after it, and cancel there at any time.

Questions

Does ReadyToEdit read my code?
No. Your AI reads it, on your machine. ReadyToEdit receives the script and the recordings it saves through the MCP, and nothing else from the repo.
Which assistants work?
Claude Code, Codex, Cursor and other assistants that sign in to an MCP server. The ReadyToEdit skills for Claude, Codex and Cursor give yours the steps, from recording the change to putting each clip on its line.
Does it need a Full plan?
No. Light covers it: the MCP, the script, Footage preview, the link and about 10 footage hours of playback a month. Your AI writes the report from what it built, and ReadyToEdit plays it back with the recording under each line.
Who can watch the report?
Anyone you send the link to, with no account: a teammate, a reviewer, a client. Update it in place when the change moves on, or revoke it.

Connect the MCP. Ask what it built.

Connect ReadyToEdit to Claude Code, Codex or Cursor, finish a change, and ask it to show you what it built. A new workspace starts a 14-day Light trial with no card.