leesgit/passbaton

> **Session continuity for AI coding agents.** Your agent picks up where it left off — never re-explain your project again. Persistent memory for **Claude Code, OpenAI Codex CLI & Google Gemini CLI**, sharing one local db: auto context injection, compaction handover, semantic search, and error→solution recall. Zero config, zero API cost, 100% local.
**⚡ One install → context auto-loads every session · 🧩 survives compaction (0 re-explaining) · 🔒 100% local, $0 API**
> **Renamed (v2.0.0):** this project was previously claude-session-continuity-mcp. The old name suggested it was Claude-only — it never was. **Claude Code, Codex CLI, and Gemini CLI are all first-class and share one local memory.** Existing installs keep working: the old claude-hook-* commands still ship as aliases. See Migrating from v1.
The Problem
Every new session — whether you're in Claude Code, Codex CLI, or Gemini CLI:
**5 minutes of context-setting. Every. Single. Time.**
The Solution
**Fully automatic.** Lifecycle hooks handle everything without manual calls — on **Claude Code**, **OpenAI Codex CLI**, and **Google Gemini CLI**, sharing one local memory so context carries across all three:
**Zero manual work. Context follows you.**
---
Why this over other memory tools?
Most Claude memory tools rely on **explicit tool calls** ("remember this"), a **cloud API**, or a **background AI worker**. This one is deliberately different:
| | passbaton | Typical cloud/AI-memory MCP |
|---|---|---|
| **Setup** | npm i -g → hooks auto-install | Manual server + API key |
| **Trigger** | 5 automatic hooks (no commands) | You call a remember tool |
| **Storage** | 100% local SQLite | Cloud / external service |
| **API cost** | **$0** — local embeddings | Per-token / subscription |
| **Latency** | **Requires Node.js 22+.** The native better-sqlite3 dependency only ships
> prebuilt binaries for Node 22, 24, and 26 (the currently supported lines —
> Node 18 and 20 are both end-of-life). On older Node it falls back to compiling
> from source, which fails without build tools. Node 22 and up install cleanly
> with no compiler needed.
Recommended: Global Installation
**That's it!** The postinstall script automatically:
1. Registers MCP server in ~/.claude.json
2. Installs Claude Hooks in ~/.claude/settings.json
> **npm install-script policy (npm 11.16+ / v12).** passbaton needs install-time scripts:
> its own postinstall (registers hooks and the MCP server) and better-sqlite3's native
> build. npm 11 runs them with an install-scripts … not yet covered by allowScripts
> warning; with strict-allow-scripts=true the install fails; npm v12 is announced to skip
> unapproved install scripts by default — passbaton would then install **without hooks and
> without a working SQLite binding**. Approve them explicitly:
>
>
>
> If an install ran with scripts skipped (passbaton-hooks status reports
> better-sqlite3 does not load), run that same command again. Re-running
> passbaton-hooks install alone does **not** rebuild the SQLite binding.
Then check it and start Claude Code:
> **Installed Node.js just now?** If Claude Code was already open before Node.js was
> installed, fully quit the app that launched it (VS Code, your terminal app) and start it
> again, then start Claude Code. Opening a new tab or window in the same app can keep the
> old PATH. No reboot is needed for this.
>
> npm hides postinstall output by default, so if setup could not finish you may not see a
> message — passbaton-hooks status shows what is registered, and
> passbaton-hooks install (re)writes it.
> passbaton-hooks is a command installed by the passbaton package — there is no npm
> package with that name, so don't run it through npx passbaton-hooks. Without a global
> install, use npx passbaton install / npx passbaton status (same installer).
Troubleshooting: npm: command not found / node: not found in a hook
The app that launched Claude Code has a PATH without Node.js (typically because it was
opened before Node.js was installed). Hooks written by older versions call npm exec and
need npm on that PATH. Run passbaton-hooks install from a terminal that has Node.js
— it rewrites passbaton's hooks and MCP entry with absolute paths — then restart as above.
passbaton-hooks status tells you which entries still depend on PATH. Its check uses