Session Forge
概览
作者提供的说明(英文原文)
Persistent memory and session intelligence for AI coding assistants. Zero config.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新↓ 75/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 搜索与 AI 记忆
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 注册中心没有列出需要填写的密钥。
你需要
- npm已安装 Node.js(用于 npx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"session-forge": {
"command": "npx",
"args": [
"-y",
"session-forge"
]
}
}
}在终端中运行这条命令
claude mcp add session-forge -- npx -y session-forge或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"session-forge": {
"command": "npx",
"args": [
"-y",
"session-forge"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"session-forge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"session-forge"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 420247jake 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5688 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5688 个服务器的 5% 更新
- 基础检查结果等于或优于此分类中其他 5688 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Session Forge 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(2.0.3)于8个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
session-forge
Never start from zero. Persistent session intelligence for AI coding assistants.
Session-forge gives your AI coding assistant memory that survives across sessions. It tracks decisions, dead ends, user preferences, and session state — so every conversation builds on the last one instead of starting from scratch.
Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client.
What it does
- Session crash recovery — checkpoint your work, pick up where you left off
- Decision logging — record why you chose X over Y, search it later
- Dead end tracking — never repeat the same debugging mistake twice
- User profile — AI remembers your name, preferences, and projects
- Session journal — capture the journey, not just the task
- Full context recall — bootstrap a new session with everything in one call
- Data management — prune old entries, export all data, view stats
Quick start
Claude Code
claude mcp add session-forge -- npx session-forge
Cursor / Windsurf
Add to your MCP settings:
{
"mcpServers": { "session-forge": { "command": "npx", "args": ["-y", "session-forge"] } } }
That's it. No database, no Docker, no config files.
The 15 tools
Sessions
| Tool | Description | Required |
|---|---|---|
session_checkpoint | Save work-in-progress state for crash recovery | task, intent, next_steps |
session_restore | Check for interrupted work from a previous session | — |
session_complete | Archive session and mark complete | — |
Profile
| Tool | Description | Required |
|---|---|---|
profile_get | Get the current user profile | — |
profile_update | Update name, preferences, projects, or notes | — |
Journal
| Tool | Description | Required |
|---|---|---|
journal_entry | Record session summary with breakthroughs and frustrations | summary |
journal_recall | Retrieve recent session journals | — |
Decisions
| Tool | Description | Required |
|---|---|---|
decision_record | Log a significant decision with alternatives and reasoning | choice, reasoning |
decision_search | Search past decisions by keyword (supports limit param) | query |
Dead Ends
| Tool | Description | Required |
|---|---|---|
dead_end_record | Log a failed approach and the lesson learned | attempted, why_failed |
dead_end_search | Search past dead ends to avoid repeating mistakes (supports limit param) | query |
Context
| Tool | Description | Required |
|---|---|---|
full_context_recall | Get everything — profile, journals, decisions, dead ends. Supports optional project filter. | — |
Data Management
| Tool | Description | Required |
|---|---|---|
data_manage | Prune old entries, export all data, clear stores, or view stats | action |
data_list | Browse stored entries with numbered summaries. Supports search filter. | store |
data_delete | Delete a specific entry by index from data_list output | store, entry_index |
`data_manage` actions:
stats— entry counts and schema versions for all storesexport— dump all data as JSONprune— remove entries older than N days (default: 90)clear— wipe a specific store (journal, decisions, dead_ends, profile, or all)
`data_list` + `data_delete` workflow:
data_listwith store="decisions" — see numbered list of all decisionsdata_listwith store="decisions", query="minecraft" — filter by keyworddata_deletewith store="decisions", entry_index=3 — remove entry #3 from the list
Why session-forge?
| session-forge | Basic memory MCPs | Enterprise tools | |
|---|---|---|---|
| Setup | npx session-forge | Varies | Docker + databases |
| Dead end tracking | Yes | No | No |
| Decision logging | Yes | No | Some |
| Session crash recovery | Yes | Some | Yes |
| Data management | Yes | No | Some |
| User profile | Yes | Some | No |
| Dependencies | 2 (SDK + zod) | Varies | 5-10+ |
| Infrastructure | Zero (plain JSON) | SQLite/ONNX/Vector DB | PostgreSQL + Redis |
| Tools | 15 focused | 4-9 | 37+ |
Configuration
Environment variables
| Variable | Default | Description |
|---|---|---|
SESSION_FORGE_DIR | ~/.session-forge or %APPDATA%\session-forge | Override data storage location |
SESSION_FORGE_STALE_HOURS | 24 | Hours before an inactive session is auto-archived |
Storage
All data is stored locally as plain JSON files:
| Platform | Location |
|---|---|
| Linux / macOS | ~/.session-forge/ |
| Windows | %APPDATA%\session-forge\ |
Override with the SESSION_FORGE_DIR environment variable:
SESSION_FORGE_DIR=/custom/path npx session-forge
Files:
~/.session-forge/
profile.json # User preferences and projects journal.json # Session summaries (last 100) decisions.json # Decision log (last 200) dead-ends.json # Failed approaches (last 100) sessions/ active.json # Current checkpoint history/ # Archived sessions
Data files include a schema_version field for future migration support.
CLAUDE.md template
Add this to your project's CLAUDE.md to teach the AI when to call each tool:
## Session Flow
Fresh session
- Call
full_context_recall— get profile, journals, decisions, dead ends - Call
session_restore— check for interrupted work
During work
decision_record— when making a significant architectural choicedead_end_record— when something fails and we learn whysession_checkpoint— every 10-15 tool calls during long sessions
Session end
- Call
journal_entry— record what happened - Call
session_complete— archive the checkpoint
Changelog
v2.0.1
- Added disclaimer: session-forge is NOT affiliated with SessionForge LLC (sessionforge.dev)
v2.0.0
- Knowledge Graph — link decisions and dead ends together with
related_dead_endsandled_to_decisionfields - Scored Search — fuzzy matching, tag filtering, AND/OR search modes, relevance scoring (replaces basic string matching)
- Usage Stats — tracks dead ends avoided, searches performed, sessions recovered
- MEMORY.md Sync —
full_context_recallcan read your MEMORY.md and suggest decisions/dead ends that should be saved to memory - Enhanced Checkpoints — now tracks
errors_encountered,key_findings,decisions_made,dead_ends_hit - New storage modules:
links.js,search.js,stats.js,migrate.js - Schema bumped to v2
v1.2.0
- Added
data_listtool — browse stored entries with numbered summaries, optional search filter - Added
data_deletetool — surgically remove individual entries by index - Users can now see exactly what's stored and delete anything they want
v1.1.0
- Added
data_managetool (stats, export, prune by age, clear per-store) - Added
projectfilter tofull_context_recall - Added
limitparam todecision_searchanddead_end_search - Added error logging to JSON reads (was silently swallowing parse failures)
- Added configurable stale session timeout via
SESSION_FORGE_STALE_HOURS - Added
schema_versionto data files for future migration support - Fixed version mismatch between code and package.json
v1.0.2
- Initial public release
License
MIT
Important Notice
session-forge is NOT affiliated with SessionForge LLC (sessionforge.dev).
session-forge was first published on npm on February 7, 2026 — before SessionForge LLC appeared. We have no connection to their product or company.
Here's why this matters: session-forge stores all your data locally on your machine as plain JSON files. Nothing leaves your computer. No accounts, no servers, no third parties.
Any service asking you to route your AI session data, coding habits, and terminal access through their servers should make you ask: who has access to that data, and what are they doing with it?
Your workflow, your decisions, your code — that's yours. It should stay on your machine, under your control. That's how session-forge was built and that's how it will stay.
Built by Jacob Terrell