Session Steward

Name: Session Steward
Author: mallikcheripally

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

注册名称io.github.mallikcheripally/session-steward

安装

概览

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

Review and safely clean local Codex and Claude Code sessions

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-steward": {
      "command": "npx",
      "args": [
        "-y",
        "session-steward",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add session-steward -- npx -y session-steward mcp

在 Cursor 中打开

或者自己复制设置

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

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

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

在 VS Code 中打开

或者自己复制设置

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

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

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

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

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

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

它能做什么

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

基础检查i

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

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

与“开发者工具”中的其他服务器比较i

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

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

常见问题

Session Steward 安全吗？

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

它需要哪些密钥或代码？

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

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

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

它还在维护吗？

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

哪些应用可以使用它？

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

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

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

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

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT4天前更新

安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT16天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

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

Session Steward

Session Steward is a local session manager for Codex and Claude Code. It helps you find old or large sessions across workspaces, decide what is worth keeping, and clean up the related records it recognizes. You can use it with browser UI or terminal CLI, or through MCP with ChatGPT or Claude.

Codex can delete a session, and Claude Code can purge a project. Built-in deletion works when you already know what should go. Session Steward helps when the hard part is reviewing many sessions across both tools.

Find inactive or large sessions across workspaces. Switch between Codex and Claude Code, then filter by archive status, name, or session ID.
Open a session before deciding. See a distilled timeline of recent messages, file changes, commands, and command results, plus recognized storage and token use.
Clean selected sessions using a plan you review first, with a local backup, verification afterward, and recovery when cleanup needs attention.

Try Session Steward locally

Try the browser app for one run without installing it globally:

Session Steward requires Node.js 24.15 or newer.

npx session-steward@latest

The browser app listens only on 127.0.0.1 and does not upload session contents.

For ongoing use, install it globally:

npm install --global session-steward

The global install provides four commands:

Command	Use it for
`session-steward`	Browser interface
`session-steward-cli`	Interactive terminal and JSON output
`session-steward-mcp`	MCP session management
`session-steward-scheduler`	Automatic session cleanup

Session Steward supports macOS, Linux, and Windows. Run session-steward to open the browser interface. Leave its terminal open while you use it; press Ctrl+C to stop it.

Find old and large Codex and Claude Code sessions

Session Steward reads the local session folders already used by Codex and Claude Code. It looks for ~/.codex and ~/.claude by default and lets you switch providers from the same interface.

You can:

filter by inactivity, exact workspace, active or archived status, name, or session ID;
see recognized session-owned storage by session and workspace, then sort by size;
browse session timeline of recent messages, file changes, commands, and command results;
inspect fresh input, cached input, cache writes, output, and recorded reasoning tokens;
mark a session or workspace Keep so manual and scheduled cleanup skip it.

A workspace Keep covers that folder, its descendants, and future sessions there. Keep affects Session Steward cleanup only. Codex or Claude Code can still remove their own data.

Why not just delete sessions one at a time?

The native delete commands are useful when you already know what should go. They do not cover the same cross-workspace review and cleanup job.

A session can have more than its transcript. Depending on the provider and storage version, it may also have history or registry entries, logs, checkpoints, and other linked records. Removing a JSONL file by hand can leave those records behind.

Session Steward starts from the session instead of a file path. It finds supported related records, shows them in one cleanup plan, and leaves storage it does not recognize alone. You can review several candidates together without treating every old session as safe to delete.

Use the browser, CLI, or MCP

Browser

Run:

session-steward

Choose Codex or Claude Code, filter or search the list, and open sessions you are unsure about. When you select sessions for cleanup, the browser shows the affected records before asking for confirmation.

Use session-steward --no-open to start without opening a browser automatically. Open the local address printed in the terminal.

Terminal CLI

Start the interactive terminal:

session-steward-cli

Use Claude Code instead of Codex, or return a limited JSON result for another tool:

session-steward-cli --provider claude-code

session-steward-cli --json --limit 10

Filter with options such as --inactive-days 60, --archive-status archived, or --workspace /path/to/project. Use --events for the timeline, --tokens for token use, and --sort size for the largest sessions first. Run session-steward-cli --help for every option.

MCP with ChatGPT, Codex, or Claude Code

Connect the local MCP server once:

codex mcp add session-steward -- session-steward-mcp

Or connect it to Claude Code:

claude mcp add --scope user session-steward -- session-steward-mcp

Registry installers can start the same server without a global install using npx session-steward@latest mcp.

You can then ask your client to find inactive sessions, compare recognized session storage between Codex and Claude Code, inspect a session, keep a workspace, clean exact sessions, restore a backup, or manage a cleanup schedule.

Session Steward marks cleanup, restore, and schedule management as destructive MCP actions so the client can apply its configured approval policy.

Automatic cleanup continues in the background after you close the client. Create and manage schedules through MCP or the browser. Before uninstalling Session Steward, stop the scheduler:

session-steward-scheduler --stop

For another MCP client, configure a local stdio server named session-steward with the command session-steward-mcp.

The MCP process uses Session Steward's saved provider folders or the defaults when none are saved. Its server command can set startup folders with --codex-home or --claude-home, and its manage_settings tool can change the saved folders. A one-time browser or CLI override does not carry into a later MCP process.

The MCP server runs locally, but session details can contain messages, commands, file names, and workspace paths. Your MCP client may send that information to its AI provider.

Review what will be deleted first

For a manual cleanup:

Select the sessions.
Close any selected sessions that may still be active.
Review the cleanup plan Session Steward builds.
Confirm the plan.
Session Steward creates a local recovery backup.
It removes only supported records in the reviewed plan.
It checks whether those records are gone.

Every interface revalidates the selected sessions before changing data. If Session Steward can detect that a selected session is active, preflight or cleanup stops. When detection is unavailable, it warns you to confirm that the selected sessions are closed.

Standard and thorough cleanup

Standard cleanup removes supported transcripts, history, registry entries, logs, and linked artifacts belonging to the selected sessions. It is the routine option.

Thorough cleanup also removes additional recognized session-owned data. For Codex, that can include supported Desktop references, memory outputs, and goal records. For Claude Code, it includes recognized file checkpoints.

Thorough cleanup is unavailable when the detected storage layout is not supported. Standard cleanup can still remove records that Session Steward can identify safely.

Backup and restore behavior

Recovery backups are stored under session-steward-backups/ inside the active provider folder.

If cleanup from the browser or interactive terminal needs attention, the backup is kept until you decide whether to restore it. The browser offers Restore, and the terminal reports the backup for the restore command. MCP and scheduled cleanup try to restore automatically.

After successful cleanup, Session Steward removes the recovery backup when it can. A restore first creates a temporary safety backup of the current files, then tries to remove both backups if the restore succeeds. If a restore or backup removal cannot complete, recovery data remains and Session Steward reports it.

What cleanup leaves alone

Sign-in data and saved API credentials
Configuration, plugins, caches, and custom prompt files
Project files, Git repositories, and worktrees
Sessions outside the reviewed cleanup plan
Conversations stored in your ChatGPT or Claude account
Claude Code worktrees, branches, repositories, remote sessions, SSH sessions, and Cowork data

Provider folders and platform support

The browser shows the active provider folder. Select Change to choose another existing folder and save it for later browser, terminal, and MCP sessions.

For a one-time browser override:

session-steward --codex-home /path/to/.codex

session-steward --claude-home /path/to/.claude

The CLI and MCP commands accept the same flags. An override applies only to that process and does not replace the saved folder.

Codex and Claude Code CLI sessions are supported on macOS, Linux, and Windows. Local Claude Desktop sessions are also supported on macOS and Windows. On Windows, the default provider folders are %USERPROFILE%\.codex and %USERPROFILE%\.claude; both standalone and Microsoft Store Claude Desktop data locations are detected.

Inside WSL, Session Steward uses the Linux home folder. Run it from Windows to manage sessions in your Windows profile.

Archiving a Claude Desktop session does not delete it. It remains available until it is explicitly included in cleanup. Session Steward does not remove Claude worktrees.

Update or uninstall

session-steward update

npm uninstall --global session-steward

If npm needs root access, the update command asks before retrying with sudo.

Uninstalling does not remove provider sessions, recovery backups, or saved folder preferences.

Troubleshooting

The browser did not open: Run session-steward --no-open, then open the local address printed in the terminal.
No sessions were found: Check the selected provider and displayed home folder. Use Change or pass a one-time home-folder override.
Thorough cleanup is unavailable: Unrecognized storage stays unchanged, while standard cleanup may still be available.
Your Node.js version is too old: Install Node.js 24.15 or newer and run Session Steward again.

Benchmarks

Current benchmarks on an arm64 Mac with Node.js 24.15.0:

Scenario	Scale	Time	Measured memory growth
Paginated session listing	50,003 sessions	26 ms	0.16 MB heap
Session size index	20,003 sessions	85 ms cold, 9.7 ms warm	30 MB peak RSS
Transcript-only discovery	5,003 sessions	662 ms	4.02 MB heap

Run the scale benchmarks with:

npm run benchmark:scale

npm run benchmark:overview npm run benchmark:size npm run benchmark:discovery npm run benchmark:transcripts

Results vary with hardware, disk speed, and session layout. Tests and benchmarks use temporary synthetic data and do not read or modify your local sessions.

Support

Use GitHub Issues to report a bug, request a provider, or share a storage format that Session Steward does not recognize. See the changelog for release history.

Session Steward is an independent project and is not affiliated with or endorsed by OpenAI or Anthropic.

只显示了开头部分；其余内容请在仓库中阅读

Session Steward

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“开发者工具”中的其他服务器比较i

常见问题

替代选择

GitHub

Desktop Commander

Cloudflare MCP

作者的 README

Session Steward

Try Session Steward locally

Find old and large Codex and Claude Code sessions

Why not just delete sessions one at a time?

Use the browser, CLI, or MCP

Browser

Terminal CLI

MCP with ChatGPT, Codex, or Claude Code

Review what will be deleted first

Standard and thorough cleanup

What cleanup leaves alone

Provider folders and platform support

Update or uninstall

Troubleshooting

Benchmarks

Support