Public AI coding replays

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

Watch real AI coding sessions from Claude Code, Claude Desktop, Claude Cowork, Cursor, Codex, OpenCode, Hermes, Pi, and Grok Bot — full prompts, tool calls, file diffs, and thinking blocks 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 every prompt, tool call, file edit, and AI thinking step from a Claude Code, Claude Desktop, Claude Cowork, Cursor, Codex, OpenCode, Hermes, 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 — all auto-discovered from local files, no extra instrumentation. Try Grok Bot with npx vibe-replay@latest -p grok-bot. vibe-replay reads JSONL for Claude Code and SQLite/JSONL for Cursor, and every provider renders with full prompt history, tool calls, diffs, and thinking blocks.

Are replays self-contained?

Every replay is a single static HTML file with all assets inlined — no external requests, no tracking. Open it offline, host it on any static server, or attach it to a PR.