Session Forge

io.github.420247jake由 GitHub 账号 420247jake 发布v2.0.3更新于 Oct 24, 2026

Persistent memory and session intelligence for AI coding assistants. Zero config.

已验证STDIO仅桌面知识与记忆开发者工具

概览

AI 生成的概览

一个本地 MCP 服务器,为 AI 编程助手提供跨会话的持久记忆:检查点、决策、死胡同、用户档案和日志。

可以做什么
保存、恢复和完成会话检查点,用于崩溃恢复和中断后继续,并可一次调用召回全部上下文,支持按项目过滤。读取和更新用户档案,包括姓名、偏好、项目和备注。记录并搜索会话日志、带备选方案和理由的重要决策,以及失败尝试及其教训。浏览、过滤、删除、清理、导出或清空已存数据,并查看各存储的统计信息。
适用场景
适合在 Claude Code、Cursor、Windsurf 或其他 MCP 客户端中进行长时间编程工作时使用,让助手把决策、偏好和过去的错误从一个会话带到下一个会话,或在中断后继续工作。
运行要求
通过 stdio 在本地运行,通常用 npx 从 npm 包 session-forge 启动,因此需要 Node.js,首次安装还需要网络访问。无需账号、API 密钥或数据库。数据以纯 JSON 文件存放在用户主目录或应用数据目录;可选环境变量 SESSION_FORGE_DIR 和 SESSION_FORGE_STALE_HOURS 可更改存储位置和会话过期阈值。
安装前请注意
该服务器会写入包含档案、决策、日志和会话状态的本地持久文件,且工具可以删除条目、清理旧数据或清空整个存储,批准前请确认这类破坏性操作。按 README 所述数据保留在本机;README 也说明该项目与一家同名公司没有关联。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Session Forge,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

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

bash
claude mcp add session-forge -- npx session-forge

Cursor / Windsurf

Add to your MCP settings:

json
{  "mcpServers": {    "session-forge": {      "command": "npx",      "args": ["-y", "session-forge"]    }  }}

That's it. No database, no Docker, no config files.


The 15 tools

Sessions

ToolDescriptionRequired
session_checkpointSave work-in-progress state for crash recoverytask, intent, next_steps
session_restoreCheck for interrupted work from a previous session—
session_completeArchive session and mark complete—

Profile

ToolDescriptionRequired
profile_getGet the current user profile—
profile_updateUpdate name, preferences, projects, or notes—

Journal

ToolDescriptionRequired
journal_entryRecord session summary with breakthroughs and frustrationssummary
journal_recallRetrieve recent session journals—

Decisions

ToolDescriptionRequired
decision_recordLog a significant decision with alternatives and reasoningchoice, reasoning
decision_searchSearch past decisions by keyword (supports limit param)query

Dead Ends

ToolDescriptionRequired
dead_end_recordLog a failed approach and the lesson learnedattempted, why_failed
dead_end_searchSearch past dead ends to avoid repeating mistakes (supports limit param)query

Context

ToolDescriptionRequired
full_context_recallGet everything — profile, journals, decisions, dead ends. Supports optional project filter.—

Data Management

ToolDescriptionRequired
data_managePrune old entries, export all data, clear stores, or view statsaction
data_listBrowse stored entries with numbered summaries. Supports search filter.store
data_deleteDelete a specific entry by index from data_list outputstore, entry_index

data_manage actions:

  • stats — entry counts and schema versions for all stores
  • export — dump all data as JSON
  • prune — 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:

  1. data_list with store="decisions" — see numbered list of all decisions
  2. data_list with store="decisions", query="minecraft" — filter by keyword
  3. data_delete with store="decisions", entry_index=3 — remove entry #3 from the list

Why session-forge?

session-forgeBasic memory MCPsEnterprise tools
Setupnpx session-forgeVariesDocker + databases
Dead end trackingYesNoNo
Decision loggingYesNoSome
Session crash recoveryYesSomeYes
Data managementYesNoSome
User profileYesSomeNo
Dependencies2 (SDK + zod)Varies5-10+
InfrastructureZero (plain JSON)SQLite/ONNX/Vector DBPostgreSQL + Redis
Tools15 focused4-937+

Configuration

Environment variables

VariableDefaultDescription
SESSION_FORGE_DIR~/.session-forge or %APPDATA%\session-forgeOverride data storage location
SESSION_FORGE_STALE_HOURS24Hours before an inactive session is auto-archived

Storage

All data is stored locally as plain JSON files:

PlatformLocation
Linux / macOS~/.session-forge/
Windows%APPDATA%\session-forge\

Override with the SESSION_FORGE_DIR environment variable:

bash
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:

markdown
## Session Flow
### Fresh session1. Call `full_context_recall` — get profile, journals, decisions, dead ends2. Call `session_restore` — check for interrupted work
### During work- `decision_record` — when making a significant architectural choice- `dead_end_record` — when something fails and we learn why- `session_checkpoint` — every 10-15 tool calls during long sessions
### Session end1. Call `journal_entry` — record what happened2. 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_ends and led_to_decision fields
  • 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_recall can 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_list tool — browse stored entries with numbered summaries, optional search filter
  • Added data_delete tool — surgically remove individual entries by index
  • Users can now see exactly what's stored and delete anything they want

v1.1.0

  • Added data_manage tool (stats, export, prune by age, clear per-store)
  • Added project filter to full_context_recall
  • Added limit param to decision_search and dead_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_version to 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

来源:README.md,提交 704ada9

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v2.0.3最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分