vibe-replay

Turn Claude, Cursor, Codex, OpenCode, Hermes, and Pi sessions into shareable, interactive replays.

The problem

AI agents write code in long, complex sessions — dozens of tool calls, hundreds of file edits, thousands of lines of reasoning. When the session ends, all that context disappears. Your PR diff shows what changed, but reviewers can't see why. Teammates can't learn from your prompting. You can't even replay your own session next week.

The fix

One command. One self-contained HTML file. Every prompt, every thought, every tool call — animated and interactive.

npx vibe-replay

Also available as a Claude Code plugin — your agent generates replays automatically during PR creation.

Watch a live demo →

What You Get

All your sessions, one place

Launch with npx vibe-replay -d and see every Claude, Cursor, Codex, OpenCode, Hermes, and Pi session across all projects — with a daily activity snapshot, activity heatmaps, cost totals, and project analytics. Search sessions, filter by git repo, tool, MCP server/tool, skill, or context compaction, expand any session to see its own tool/MCP breakdown, and generate any replay in one click.

Remote SSH sources

The dashboard can also include JSONL sessions from any OpenSSH-compatible host. Add targets from the dashboard's Settings tab, or directly in ~/.vibe-replay/config.json:

{
  "remoteSources": [
    {
      "id": "remote-dev",
      "label": "Remote dev",
      "sshHost": "devbox",
      "providers": ["codex", "claude-code", "pi"]
    }
  ]
}

The Settings form validates source ids, provider selections, and connection timeouts, and can run a bounded SSH probe before you refresh the catalog. It uses your existing OpenSSH keys, aliases, and ProxyJump configuration; credentials are never stored by vibe-replay.

sshHost can be a normal hostname or an alias from ~/.ssh/config, so existing keys, agents, ProxyJump, and ProxyCommand configuration continue to work. No private key or password belongs in this file. Remote Codex, Claude Code, and Pi JSONL files are copied into a per-target local cache and parsed by the same providers as local sessions; source cards show the configured location label. A transcript that is still being written is kept at its last stable cached version instead of making the whole SSH source unavailable. Codex titles match /resume: explicit names from session_index.jsonl take precedence over the read-only state_5.sqlite title. The live database and WAL are never copied. Hosts with Python sqlite3 or the sqlite3 CLI unavailable still use cached metadata. Sessions whose source is missing, unreadable, or contains no meaningful human prompt remain visible with an explicit status and cannot be generated into an empty replay. Remote repository identity is retained for local filtering but omitted from shareable replay data. Remote Live mode is intentionally unavailable. Remote sessions stay in local insights and are excluded from optional cloud insight sync.

Watch the full replay

Pick a session and step through every prompt, thinking block, tool call, and code diff with animated playback. Three view modes — All, Compact, and Custom.

Deep insights for every session

Auto-generated analytics: token burn & cost over time, context window usage, cache read share, tool call distribution, model breakdown, and per-turn breakdowns.

The Insights Coverage section separates scan completion from metric availability and shows provider-level precision for invocations, MCP calls, tokens, cache reads/writes, and compactions. “Uncached / miss” is a derived prompt metric (uncached input + cache writes); providers do not share one universal cache-miss counter. Cursor snapshot totals are marked estimated, and Cursor compactions are lower bounds because its local store can retain only the latest summary.

Your AI coding wrapped

GitHub-style activity heatmap, streaks, weekly trends, top projects, model usage, and cost tracking across all your sessions. See how your coding patterns evolve over time.

Claude Code Plugin

vibe-replay is also available as a Claude Code plugin. Once installed, your agent learns how to generate replays autonomously — it can find the current session, produce GitHub-ready artifacts, and embed them in PRs, all without you running any CLI commands.

What the plugin gives your agent

• Auto-discover sessions — finds the current session's JSONL file via $CLAUDE_SESSION_ID
• Search past sessions — uses vibe-replay sessions to find Claude, Cursor, Codex, OpenCode, Hermes, and Pi sessions by project, provider, or fuzzy query
• Generate PR artifacts — markdown summary + animated GIF + SVG, ready for PR descriptions
• Generate HTML replays — self-contained interactive replay files
• PR workflow integration — agent automatically embeds replay context when you create PRs

Install (recommended)

Open Claude Code, run /plugin, then search vibe-replay in the Discover tab and install.

Or install via CLI:

/plugin marketplace add tuo-lei/vibe-replay
/plugin install vibe-replay@vibe-replay

Agent Skills install (Cursor, Codex, and others)

vibe-replay also ships a portable SKILL.md under skills/replay/, so agents that support the Agent Skills standard can install the same replay workflow without the Claude plugin marketplace.

npx skills add tuo-lei/vibe-replay --skill replay -g

This installs the replay skill globally through the Agent Skills CLI. Cursor discovers global skills from ~/.agents/skills/ and ~/.cursor/skills/, so this is the recommended install path for Cursor users.

Manual install (single file)

If you prefer not to install through a marketplace or the Agent Skills CLI:

mkdir -p ~/.claude/skills/replay
curl -o ~/.claude/skills/replay/SKILL.md \
  https://raw.githubusercontent.com/tuo-lei/vibe-replay/main/skills/replay/SKILL.md

Usage examples

# Slash command — generate a replay of the current session
/vibe-replay:replay

# Natural language — agent auto-triggers during PR creation
"Create a PR with session replay"
"Create a PR for this change, include an animated GIF of the session"

# Direct replay
"Generate an interactive replay of this session and open it"

Features

• Zero config — one command, no setup, no account. Works instantly with existing sessions
• Cross-platform — runs on macOS, Linux, and Windows
• Single HTML file — self-contained, works offline, and makes no automatic external requests. Remote image attachments load only after an explicit click
• Claude, Cursor, Codex, OpenCode, Hermes, and Pi — all providers auto-discovered, including multi-file and resumed sessions
• Remote SSH sources — optionally combine remote Codex, Claude Code, and Pi JSONL sessions with local sessions using standard OpenSSH configuration
• Local dashboard — browse and search every session, filter by git repo, tool, MCP server/tool, skill, or context compaction, expand a session for its own tool/MCP/skill counts, with activity heatmaps, per-project analytics, and a personal-insights view (including which tools and MCP servers you lean on) across all your coding
• Share & export — GitHub Gist, animated SVG, GIF, markdown summary, or cloud upload. Secret redaction built in
• Sub-agent visualization — see delegated tool calls and sub-agent trees rendered inline
• Comments — leave notes on any scene. Comments persist in the HTML and travel with the replay
• Live mode — vibe-replay live streams a running Claude Code or Codex session into the viewer, pinned to the latest turn as it lands on disk

Supported Providers

How It Works

AI session files  →  vibe-replay  →  self-contained HTML
(Claude/Cursor,      (discover,       (animated viewer,
 Codex/OpenCode,      parse,           insights panel,
 Hermes/Pi)           redact,          offline-ready,
                      transform)       shareable)

The CLI auto-discovers sessions on your machine, parses conversation data from all sources, and packages everything into a pre-built React viewer — one HTML file that works anywhere.

After generation:

• Open in Editor — annotate scenes, get AI feedback, export to multiple formats
• AI Studio — configure Pi once from the global Settings page or the reusable Manage Providers dialog in AI Studio, then analyze, translate, or professionalize sessions with OpenAI, ChatGPT/Codex subscription, OpenRouter, or OpenCode Zen. No Claude, OpenCode, or other headless CLI is required. You can also add an OpenAI-compatible proxy (including LiteLLM) in the editor; AI Studio discovers models from its /models endpoint and sends Chat Completions requests to the configured local or remote API root.
• Ask Replay — ask read-only questions about local sessions, replay scenes, usage, and insights from the Dashboard or Editor. Answers include citations and explicit navigation actions; SSH-backed data stays hidden unless you enable it in Settings. The setting is browser-local and can be changed at any time.
• Quick preview — open in browser instantly
• Publish to Gist — shareable link on vibe-replay.com
• Export for GitHub — markdown + animated SVG for PRs

Use Cases

• Vibe coding review — replay your AI-assisted coding sessions to spot prompting patterns and improve your workflow
• Team knowledge sharing — show teammates how you built something, not just the final diff
• PR context — attach a replay link to PRs so reviewers understand the reasoning behind changes
• Teaching & onboarding — create replayable walkthroughs of real coding sessions for documentation or training
• Cost tracking — see exactly how many tokens each session burns, track costs across projects

Security & Privacy

• Self-contained HTML — generated replay files embed viewer assets inline and make no automatic external requests when opened from disk. Remote image URLs are blocked until you explicitly choose to load an individual image. (Gist/cloud-backed replays fetch data from GitHub or the vibe-replay API on load.)
• Secret redaction — API keys, tokens, PEM keys, and sensitive paths are automatically detected and redacted before generation
• Local by default — vibe-replay reads session files from your machine and generates a local HTML file. Data only leaves your machine when you explicitly publish (Gist or cloud upload), or if you log in — in which case aggregated local session insights (counts, durations, costs — no conversation content) sync daily to the cloud. Remote SSH session aggregates stay local.
• Local AI setup — AI Studio and Ask Replay use the embedded Pi provider and agent runtime. Credentials stay outside replay files and cloud uploads; AI requests only run after a configured provider and usable model are selected. When Pi's settings.json defines a default provider/model, Vibe Replay honors it only when the provider identity (provider id or configured endpoint) and exact model are both verified; it never silently chooses the first catalog entry. Provider keys and OAuth refresh tokens are stored in ~/.vibe-replay/ai-auth.json with restricted permissions (VIBE_REPLAY_AI_AUTH can override the path). Custom endpoint metadata is stored separately in ~/.vibe-replay/ai-providers.json with the same local-only permissions; the endpoint file never contains the custom API key. Enter a base URL such as http://127.0.0.1:58788/v1 in Settings or the AI Studio provider dialog, not /models or /chat/completions. HTTP is restricted to loopback endpoints; use HTTPS for a remote gateway. The selected provider/model is remembered automatically as a browser-local preference; model lists are searchable rather than hardcoded.

Development

git clone https://github.com/tuo-lei/vibe-replay.git
cd vibe-replay
pnpm install
pnpm dev              # Viewer (Vite HMR) + CLI (auto-restart) — full HMR
pnpm dev:website      # Website (Astro HMR) + Viewer (Vite HMR)

The dev launchers reserve their selected ports for the lifetime of the launcher, so multiple worktrees can start at the same time without selecting the same port during startup. To choose a fixed pair explicitly, use VIBE_API_PORT and VIBE_VIEWER_PORT:

VIBE_API_PORT=13457 VIBE_VIEWER_PORT=5174 pnpm dev
VIBE_VIEWER_PORT=5175 VIBE_WEBSITE_PORT=4322 pnpm dev:website

The requested ports must be free and different within the same launcher. If only one port is overridden, automatic selection skips that port as well.

CLI usage requires Node.js >= 22.19.0. The website package uses Astro 6 and requires Node.js >= 22.12.0. When nvm is available, website scripts will try nvm use from website/.nvmrc automatically. If a global package-manager shim selects an older Node for child commands, verify corepack pnpm exec node -v and use corepack pnpm ... after selecting a compatible Node version; see CONTRIBUTING.md.

See CONTRIBUTING.md for architecture details and development workflow.

Contributing with a coding agent? Project instructions live in AGENTS.md, which Claude Code, Codex, Cursor, Pi, and opencode all read. See Working with a coding agent.

License

MIT