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 分