Back to the collection
WorkflowPublic source

Replay Theater: review Claude Code edit attempts.

Install Replay Theater for Claude Code to review the last turn’s edit attempts, one diff at a time. Learn /replay controls and session-history limits.

By Claude Code DevRelReviewed 2026-10-14
● ● ●claude / replay-theater
▶ Replay step 2 / 5
− const greeting = "Hello"+ const greeting = "Welcome"+ return greeting
1 2 3 4 5 Next →
UI illustration

What it does

Replay Theater is a source-published playground sample that records Edit, Write and MultiEdit calls, then lets you inspect them after a turn. It observes those calls without blocking or changing them. Its timeline records attempts, including edits that fail or are denied.

  • Per-edit diff navigation
  • A /replay command
  • Inline and side-pane layouts

How to install Replay Theater

This listing follows the original claude-code-playground sample. Other marketplaces publish similarly named forks; use the commands for the source you have reviewed. The author requires Claude Code 2.1.287+ and a terminal, with no environment variables or configuration.

Run these shell commands to check the plugin and load it for one session. Validation is a plugin check, not a safety certification.

INSTALL / TERMINAL
git clone https://github.com/anthropics/claude-code-playground.git
cd claude-code-playground/claude-code/mods
claude plugin validate ./replay-theater
claude --plugin-dir ./replay-theater

For a persistent install, run these from the same mods directory:

INSTALL / TERMINAL
claude plugin marketplace add ./
claude plugin install replay-theater@claude-code-playground-mods --scope user

For loading problems, see the installation checklist. These instructions describe the author’s terminal setup; CC Mods has not tested Desktop compatibility.

Open the replay and move between edits

After a turn that calls file-edit tools, enter /replay. Alternatively, press ctrl+x then Tab to focus the hint above the prompt, and press r or activate its Replay button.

  • n moves to the next edit; p moves to the previous edit.
  • c or Escape closes the replay. The pane also has clickable navigation buttons.

Does replay prove that an edit succeeded?

No. Recording happens when a tool is called, so a failed or denied edit still appears. The mod does not undo edits or require approval. Our recommendation: compare the timeline with the actual files, git diff and relevant checks before accepting the result.

Why is the diff incomplete?

Each step shows at most 12 lines. Edit steps compare the supplied old and new strings, without file line numbers. Write steps read the previous file from disk; above 400 lines, they show removal and addition without matching lines. Use your normal diff viewer for the complete change.

Where did my previous replay go?

A new turn with edits replaces it; a turn without edits keeps it. Restarting Claude Code or reloading the plugin clears the in-memory history. The README says subagent edits are included in the main turn’s replay.

Why can the hint or pane be missing?

Another mod can occupy the shared band above the prompt. The sample uses an inline pane or a right-hand pane in fullscreen mode. The author labels the band fallback and MultiEdit path as untested, so neither is a compatibility guarantee.

Source-reviewed October 14, 2026 from the author README; no mod code was run by CC Mods. Browse workflow mods or compare Live Plan Progress for visibility while a task runs.

When this mod might be useful

Replay Theater may be useful after a multi-step coding task when the final diff does not explain the order in which changes were attempted. Stepping through captured edit events can help you reconstruct the session. Keep that event history separate from evidence that every edit succeeded or was committed.

Understanding this listing

Use this listing as a starting point for comparing the author’s documented behavior with your own workflow. The repository is the source of truth for installation, configuration, and later changes. The commands here reflect the setup available at the review date.

Before you try it

  • Requires Claude Code 2.1.287+ and a terminal; the author documents no environment variables or configuration.
  • Records tool-call attempts, including denied or failed edits. Check the actual files and Git diff to establish the resulting changes.
  • History is kept in memory for the current session and disappears on restart or plugin reload. A turn with no edits retains the previous replay.
  • Diffs are capped at 12 lines per step. Edit steps compare old_string/new_string rather than the whole file and do not show file line numbers.
  • The README marks MultiEdit handling and the AbovePrompt fallback as untested author paths. CC Mods has not executed the sample or tested Desktop compatibility.

More in workflow