session-recap

Name: session-recap
Author: BruceXcluding

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

注册名称io.github.BruceXcluding/session-recap

安装

概览

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

Recap AI coding sessions (Claude Code, Codex, dsh, OpenCode): intent, decisions, open threads.

PopNx MCP 的三大支柱

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

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

它能帮你做什么

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

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

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

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

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

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

{
  "mcpServers": {
    "session-recap": {
      "command": "npx",
      "args": [
        "-y",
        "session-recap",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add session-recap -- npx -y session-recap mcp

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "session-recap": {
      "command": "npx",
      "args": [
        "-y",
        "session-recap",
        "mcp"
      ]
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "session-recap": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "session-recap",
        "mcp"
      ]
    }
  }
}

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

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

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

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

它能做什么

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

基础检查i

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

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

与“其他”中的其他服务器比较i

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

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

常见问题

session-recap 安全吗？

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

它需要哪些密钥或代码？

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

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

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

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.6.1）于昨天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, TF Rooms

替代选择

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

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

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

TF Rooms

作者：tfrooms.com

Live room availability, rates and stay quotes for 12 New Leaf motels in Twin Falls, Idaho.

在云端运行今天更新

安装

作者的 README

打开 README

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

session-recap

English | 中文

Remember what every AI coding session was for.

intent · key decisions · what changed · open threads · where to resume, for sessions of any length, from any agent, through MCP, a local viewer or a plugin

Projects grow, and so does the number of sessions in each one, often across several agents. After a few weeks a session is a 100 MB transcript you no longer remember: why you started it, what you decided, what was left half done.

session-recap reads a session's whole transcript and writes a short, structured recap. Use it from any MCP client (Codex, Cursor, Zed, Cline, Gemini CLI, OpenCode, Claude Code…), in a local viewer for every agent's sessions, from the command line, or through native plugins for Claude Code, dsh and Codex.

Section	What it answers
Intent	What was I ultimately trying to achieve?
Key ideas and decisions	What did we choose, and why? Which alternatives were rejected?
What changed	Files, features, documents, commits, PRs
Open threads	What is unfinished, unverified or still a question
Where to resume	The most sensible next step today

Every recap also has a Map: the phases the work went through (pivots marked) down to "you are here", the key decisions with what was turned down, and lists of what shipped, what is open and what was dropped. Recaps are written in the language you mostly write in.

Quick start

npm install -g session-recap

session-recap mcp-config # prints the MCP entry for your client session-recap serve # opens the local viewer

Then, in your agent: *"Recap this session"*, *"What was my last session in this project about?"*, *"总结一下这个会话"*.

No API key needed. Through MCP, the agent you are talking to writes the recap with its own model; session-recap only reads and condenses the transcript. A model of session-recap's own is optional (for the CLI and the viewer's Write recap button).

Or run it without installing: npx session-recap …. session-recap has no dependencies and runs no install scripts. The development version: npm install -g github:BruceXcluding/session-recap --allow-git=all (npm 12 blocks installs from GitHub without the flag).

Requirements: Node.js 20+, python3 (macOS ships one), and for dsh sessions the zstd command or Python 3.14+.

Ways to use it

	Best for	How
MCP server	any MCP client	`session-recap mcp-config` , see below
Local viewer	browsing every agent's sessions, Recap and Map	`session-recap serve`
Claude Code plugin	a Recap / Map pane beside the chat	`/plugin install session-recap --marketplace BruceXcluding/session-recap`
dsh plugin	`/recap` and the `session_recap` tool in dsh	packages/dsh
Codex plugin	the MCP server, packaged for Codex	plugins/codex
Command line	scripts, quick looks, other formats	`session-recap`, `session-recap list`

MCP server

session-recap mcp-config prints the entry for claude, codex, cursor, gemini (and Qwen Code), opencode, zed, vscode or cline, with absolute paths so an IDE started from the dock finds it. For example:

session-recap mcp-config codex >> ~/.codex/config.toml

claude mcp add --scope user session-recap -- session-recap mcp

Tools:

Tool	What it does
`list_sessions`	Sessions of every agent, filtered by title words, project folder or agent
`recap_session`	The recap of the current session (or one named): a stored one if the session has not changed; else written by session-recap's model if one is configured; else the condensed, secret-free transcript and instructions for the calling agent to write it
`save_recap`	Stores the recap the agent wrote, so it is reused, and updated from the new part next time

recap_session also takes format: standup, handoff or pr instead of the recap.

Local viewer

session-recap serve opens http://127.0.0.1:4711 with every agent's sessions by project folder, grouped by time, filtered by agent; each session's Recap and Map; and, with a model configured, Write recap and Update recap. It reads the recaps written by the Claude Code plugin, the CLI and MCP clients alike. It answers only on loopback, to the browser tab it opened.

Claude Code plugin

/session-recap recaps the session you are in; /session-recap browse lists projects and sessions; /session-recap opens a project or a session by name. The pane shows Recap and Map, uses the session's own model (or one picked under Model), and shows your Claude Code sessions first, with All agents one tap away.

Command line

Command	What it does
`session-recap [words]`	Recaps the session whose title holds the words; with none, the newest one in this folder
`session-recap list [words]`	Lists sessions (the calling agent's; `--all` for every agent)
`session-recap --format standup`	A standup note instead (`handoff`, `pr`)
`session-recap --dry-run`	Shows the size that would be sent, and how many secrets were removed, without calling a model
`session-recap models`	Lists your provider's models
`session-recap config set model`	Saves settings (`partModel`, `api`, `baseUrl`; the key with `config set apiKey -` from stdin)

The CLI's own model: SESSION_RECAP_API (anthropic or openai), SESSION_RECAP_BASE_URL, SESSION_RECAP_API_KEY, SESSION_RECAP_MODEL, or ANTHROPIC_*, DEEPSEEK_API_KEY, OPENAI_API_KEY.

Supported agents

Agent	Sessions read from
Claude Code	`~/.claude/projects/`
Codex	`~/.codex/sessions/`, `archived_sessions/` (review threads left out)
dsh (deepseek-harness)	`~/.dsh/sessions/` (zstd; subagent sessions left out)
OpenCode	`~/.local/share/opencode/opencode.db`

Want another? Adding an agent is one reader and one test, or ask for it.

Privacy

Local. Sessions are read on your machine. Text leaves it only in the model call a recap needs: your agent's (MCP, plugins) or the one you configured (CLI, viewer). No telemetry.
Secrets removed first. Keys, tokens, private keys, credentials in URLs and PASSWORD=…-style assignments are replaced with [REDACTED: ] before any text reaches a model. --dry-run shows how many. It is pattern matching, so it cannot know every format: see SECURITY.md.
What is sent is a condensed transcript: your prompts, each turn's final reply, commits and PRs, the files edited. Tool output and intermediate replies are left out.

Token use

Listing never calls a model. On a real 179 MB Claude Code session (220 prompts), a first recap sends about 195k characters (~96k tokens); when the session continues, an update reads only the new prompts. Long sessions are condensed in parts of ≤75k characters, each part's notes cached, and a cheaper model can condense the parts (partModel).

How it works

saved sessions (Claude Code · Codex · dsh · OpenCode)

│ hooks/digest.py one reader per agent → turns (prompt, actions, final reply, edits) → secrets removed │ core/recap.mjs parts → notes (parallel, cached) → one call writes the recap and its map, or updates it │ MCP server · viewer · CLI · Claude Code pane · dsh tool and /recap (one cache: ~/.cache/session-recap)

Output is versioned: see docs/data-format.md and schema/recap-v1.schema.json to build your own viewer or exporter.

Contributing

Agents, recap formats, translations and viewers are all welcome. Start with CONTRIBUTING.md; adding an agent and adding a format (one entry in core/formats.mjs) are the easiest first contributions.

License

MIT

session-recap

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

TF Rooms

作者的 README

session-recap

Quick start

Ways to use it

MCP server

Local viewer

Claude Code plugin

Command line

Supported agents

Privacy

Token use

How it works

Contributing

License