Public AI coding replays

Claude Code, Claude Desktop, Claude Cowork, Cursor, Codex, OpenCode, Hermes, Muse, Pi & Grok Bot sessions shared by the community

Watch real AI coding sessions from Claude Code, Claude Desktop, Claude Cowork, Cursor, Codex, OpenCode, Hermes, Muse, Pi, and Grok Bot — prompts, tool calls, file diffs, and available thinking rendered as an interactive timeline. Each replay is a self-contained HTML file you can open offline, embed in a PR, or share as a link.

Want to share your own? Runnpx vibe-replayand publish from the editor, or usenpx vibe-replay sharefor a cloud link.

Loading replays...

Frequently asked questions

What are AI coding session replays?

Replays capture prompts, tool calls, file edits, and available thinking from a Claude Code, Claude Desktop, Claude Cowork, Cursor, Codex, OpenCode, Hermes, Muse, Pi, or Grok Bot session, then render them as an interactive timeline you can scrub through. Browse public replays here to see how others build with AI.

How do I share my own replay?

Run npx vibe-replay, open the replay in the editor, and choose Publish to Gist, or run npx vibe-replay share for an unlisted cloud link. You can also use npx vibe-replay --session --github for PR-ready markdown, GIF, and SVG artifacts. Public Gist replays appear here automatically.

Which agents can I replay?

Claude Code, Claude Desktop, Claude Cowork, Cursor, Codex, OpenCode, Hermes, Pi, and Grok Bot are auto-discovered from local files with no extra instrumentation; Muse support is on main and ships in the next npm release. Try Grok Bot with npx vibe-replay@latest -p grok-bot. vibe-replay reads each provider's local transcript format and renders the prompts, tool calls, diffs, and thinking that source actually records.

Are replays self-contained?

Every replay is a single static HTML file with viewer assets inlined and no automatic external requests. Remote images load only after you explicitly choose to load them. Open it offline, host it on any static server, or attach it to a PR.