Claude Replay

Name: Claude Replay
Author: constripacity

作者：constripacity版本 0.4.3i★ –i在你的电脑上运行

注册名称io.github.constripacity/claude-replay

安装

概览

作者提供的说明（英文原文）

Session checkpoint & recovery for Claude Code: resume, search, tag, and export recorded sessions.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： CLAUDE_REPLAY_DB

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "claude-replay": {
      "command": "uvx",
      "args": [
        "claude-replay",
        "mcp"
      ],
      "env": {
        "CLAUDE_REPLAY_DB": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add claude-replay --env CLAUDE_REPLAY_DB=your-value -- uvx claude-replay mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "claude-replay": {
      "command": "uvx",
      "args": [
        "claude-replay",
        "mcp"
      ],
      "env": {
        "CLAUDE_REPLAY_DB": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "claude-replay": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "claude-replay",
        "mcp"
      ],
      "env": {
        "CLAUDE_REPLAY_DB": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

CLAUDE_REPLAY_DB env
SQLite database path (default: ~/.claude-replay/sessions.db). Point HTTP and stdio instances at the same path to share recorded sessions.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 constripacity 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7251 个服务器的 0%
发布到注册中心的时间比此分类中其他 7251 个服务器的 31% 更新
基础检查结果等于或优于此分类中其他 7251 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Claude Replay 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.4.3）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT今天更新

安装

Codebase Memory

作者：DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT20天前更新

安装

Exa

作者：exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT上个月更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Claude Replay

The observability layer for Claude Code sessions — search, analytics, and visualization across every project.

Claude Code's --resume/--continue and /rewind recover *the session you're in*. Claude Replay does the part they don't: it hooks passively into every session, records what happened to a local SQLite store, and makes every past session — across every project — searchable, comparable, measurable, and exportable. Full-text search, per-session insight metrics, death-cause classification (*why* a session ended), session diffing, a web dashboard, and a terminal UI — none of which Claude Code has natively.

Claude Code session

| hooks (PreToolUse · PostToolUse · Stop) | v ~/.claude-replay/sessions.db ← events + checkpoints | +----+--------------------+ | | | MCP tools Dashboard TUI (resume) :8766 (browse)

Passive hooks write. MCP tools, the web dashboard, and the terminal UI read. Nothing leaves your machine.

How this complements native Claude Code

Claude Replay is additive — it layers on top of the built-ins, it doesn't replace them.

You want to…	Use
Resume / continue the current session	Native `claude --continue`, `--resume`
Undo file + conversation changes in a session	Native `/rewind`
Search every past session by content, tool, or outcome	Replay `search`
See why a session ended + per-session metrics	Replay `status` / `replay_insights`
Compare two runs side by side	Replay `diff`
Visualize a session timeline / browse all projects	Replay dashboard + TUI
Export a session as HTML / JSON / Markdown	Replay `export --format`

Think of native resume/rewind as *recovery*, and Replay as *observability* over your whole history.

Architecture

Passive hooks write to SQLite. MCP tools read from SQLite. Dashboard + TUI visualize SQLite. That's the whole system.

Layer	File	Role
Store	`claude_replay/store.py`	All DB access — sessions, events, checkpoints
Hooks	`claude_replay/hooks.py`	Record tool calls + auto-checkpoint, dispatched by `claude-replay hook`
Recovery	`claude_replay/resume.py`	Generate a resume brief from a session
Export	`claude_replay/export.py`	Render a session as a self-contained HTML trace
Server	`claude_replay/server.py`	Starlette app — MCP SSE + JSON API + static dashboard
TUI	`claude_replay/tui.py` + `tui_client.py`	Textual session browser over the JSON API
CLI	`claude_replay/cli.py`	Every subcommand

Port 8766 deliberately one above Claude Bridge's 8765, so the two siblings can run side by side without colliding.

Quickstart

1. Install

pip install claude-replay

Or from a clone if you'd like to hack on it:

git clone https://github.com/constripacity/Claude-Replay.git

cd Claude-Replay pip install -e .[dev] # editable install with test/lint deps pip install -e .[tui] # add the terminal UI deps (textual, httpx)

If pip install -e fails on your environment (a known hatchling editable-install quirk on some setups), install the deps directly instead:

pip install mcp starlette uvicorn anyio textual httpx.

2. Install the hooks

This wires Replay into Claude Code by merging three hooks into ~/.claude/settings.json. It's idempotent and leaves any other tools' hooks untouched.

claude-replay install

✓ Installed Claude Replay hooks into ~/.claude/settings.json

PreToolUse → claude-replay hook pre-tool PostToolUse → claude-replay hook post-tool Stop → claude-replay hook stop

From now on, every Claude Code session is recorded automatically. Remove the hooks any time with claude-replay uninstall (it removes only Replay's hooks).

Confirm it's actually wired up — the one check that matters:

claude-replay doctor

Claude Replay — doctor

✓ Hooks installed: PreToolUse / PostToolUse / Stop are in settings.json ✓ Hook command on PATH: claude-replay → …/claude-replay ✓ Database: ~/.claude-replay/sessions.db ✓ Sessions recorded: 3 sessions; most recent 5m ago

All good — Replay is installed and recording. ✓

If doctor warns that claude-replay isn't on PATH, the hooks can't run and nothing is recorded — put your install directory on PATH and re-run it.

3. Start the server (dashboard + MCP tools)

claude-replay serve                 # defaults: 127.0.0.1:8766

claude-replay serve --port 9000 # custom port claude-replay serve --host 0.0.0.0 # bind all interfaces

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Claude Replay — Session checkpoint & recovery server Version: 0.4.1 DB: ~/.claude-replay/sessions.db http://localhost:8766/ ← Dashboard http://localhost:8766/sse ← MCP config http://localhost:8766/api/state ← JSON state http://localhost:8766/status ← Health check ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

4. (Optional) Register the MCP tools with Claude Code

So a running Claude Code session can call replay_resume, replay_checkpoint, etc. directly. Two ways:

SSE (alongside the dashboard — needs claude-replay serve running):

claude mcp add --transport sse -s user claude-replay http://localhost:8766/sse

stdio (no server process — the client launches Replay on demand):

claude mcp add -s user claude-replay -- claude-replay mcp

or, without installing: uvx claude-replay mcp

Verify with claude mcp list claude-replay should show ✓ Connected. Inside an already-running session, type /mcp to re-handshake.

When a session dies

# What's the state of the last session?

claude-replay status

Print a paste-ready resume brief (most recent session, or pass an id)

claude-replay resume claude-replay resume

Browse every recorded session in the terminal

claude-replay tui # needs claude-replay serve running

Export a session as a self-contained HTML trace

claude-replay export # → ~/.claude-replay/exports/ .html

Paste the resume output into a fresh Claude Code session and it picks up where the dead one left off objective, what was done, what's next, and which files were touched.

MCP Tools

Every connected Claude Code session gets these ten tools:

Tool	Description
`replay_status`	Current session summary objective, status, how it ended, event/checkpoint counts, last activity
`replay_checkpoint`	Force a checkpoint of the current session now, with an optional note
`replay_resume`	Generate a structured resume brief for a session (default: most recent)
`replay_sessions`	List recent sessions with status, model, duration, checkpoint count
`replay_insights`	Per-session metrics: how it ended, duration, tool calls, error rate, files touched, top tools
`replay_stats`	Cross-session analytics: tool calls, error rate, why sessions end, tool mix, per-project rollups
`replay_search`	Full-text search across sessions with filters (tool, cause, date, project), ranked by match count
`replay_diff`	Compare two sessions: metric deltas + which files each touched
`replay_tag`	Name a session and add/remove tags for later retrieval
`replay_export`	Render a session as a self-contained trace (html / json / md) and return the path

CLI Reference

Command	What it does
`claude-replay install`	Merge Replay's hooks into `~/.claude/settings.json` (idempotent)
`claude-replay uninstall`	Remove only Replay's hooks
`claude-replay status`	Current/last session at a glance, with insight metrics
`claude-replay sessions [--limit N]`	List recent sessions (with names + tags)
`claude-replay search [--tool T] [--cause C] [--since 7d] [--project P]`	Full-text search with filters (omit query to browse by filter)
`claude-replay diff`	Compare two sessions side by side
`claude-replay resume [session_id]`	Print a resume brief (default: most recent)
`claude-replay export [session_id] [--output DIR] [--format html\	json\	md]`	Render a trace
`claude-replay tag [session_id] [--name N] [--add a,b] [--remove c] [--clear]`	Name or tag a session
`claude-replay prune [--older-than 30d] [--yes]`	Delete sessions with no recent activity (destructive)
`claude-replay serve [--host H] [--port P]`	Start the MCP + dashboard server (port 8766)
`claude-replay mcp`	Serve the MCP tools over stdio (for `uvx claude-replay mcp` / MCP clients)
`claude-replay tui [--url URL]`	Launch the terminal session browser
`claude-replay reset [--yes]`	Delete all recorded sessions (destructive)
`claude-replay hook`	Internal — invoked by Claude Code's hooks

Dashboard & TUI

Web dashboard (claude-replay serve, then open http://localhost:8766/) a vanilla-JS view that polls every 2 s: session list (with how-it-ended badge + tags), a live search box, per-session timeline, and one-click "Copy Resume Brief" / "Export HTML". No CDN, no build step.

Terminal UI (claude-replay tui) a Textual browser in the same dark theme. A session sidebar, a live event feed, and a detail inspector showing how the session ended, its tags, the latest checkpoint, and files touched. Keys:

↑↓ navigate   Tab switch panel   Space pause

r resume (copies the brief to your clipboard) e export HTML trace ? help q quit

The TUI talks to the server over HTTP start claude-replay serve first (defaults to http://127.0.0.1:8766; point elsewhere with --url).

Configuration

Env var	Default	Purpose
`CLAUDE_REPLAY_DB`	`~/.claude-replay/sessions.db`	SQLite store location
`CLAUDE_SESSION_ID` / `CLAUDE_CODE_SESSION_ID`	—	Session identity (Claude Code sets this in the hook payload); falls back to these env vars, then to a hash of the project dir
`CLAUDE_REPLAY_CORS_ORIGIN`	localhost only	Comma-separated extra CORS origins for the server
`CLAUDE_REPLAY_NO_DASHBOARD`	—	Set to disable the static dashboard mount (MCP/JSON only)

The hook path is offline-first by design: it makes no network calls and completes in well under 50 ms just the one SQLite write. Large tool payloads are truncated at 8 KB per event so the DB stays lean.

Development

pip install -e .[dev]               # or install deps directly (see install note)

python -m pytest # full suite ruff check .

Tests use an isolated tmp_path SQLite database (the fresh_db fixture) — they never touch your real ~/.claude-replay/sessions.db. See CONTRIBUTING.md for the scope and the coding rules.

License

MIT see LICENSE.

Sibling to Claude Bridge. Built under the Constripacity banner.

Claude Replay

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“搜索与 AI 记忆”中的其他服务器比较i

常见问题

替代选择

Context7

Codebase Memory

Exa

作者的 README

Claude Replay

How this complements native Claude Code

Architecture

Quickstart

1. Install

2. Install the hooks

3. Start the server (dashboard + MCP tools)

4. (Optional) Register the MCP tools with Claude Code

or, without installing: uvx claude-replay mcp

When a session dies

Print a paste-ready resume brief (most recent session, or pass an id)

Browse every recorded session in the terminal

Export a session as a self-contained HTML trace

MCP Tools

CLI Reference

Dashboard & TUI

Configuration

Development

License