Rate limited. Model died. Context compacted. You switched tools. The code is still in git—the working state is not.
Local CLI and MCP server for checkpoints and handoff packets. Resume after a crash. Move context across tools, repos, or agents—no cloud account.
npm install -g @3notch/cli
@3notch/cli, run notch onboard in this repo, enable continuation checkpoints for Claude Code if needed. Use packets for cross-tool or cross-repo handoffs.
No account. Runs on your machine.
Git has the files. It does not have the objective you were mid-way through, the decisions you already made, or the landmines you already stepped on.
Vendors optimize for their own product. Claude will not make it easy to hand a live session to Codex. Codex will not make it easy to hand one to Cursor. That is not a bug in any one tool—it is the market structure.
3Notch is a neutral, local format for the state that falls between commits: what you were doing, what finished, what is blocked, and what is next. You decide what gets written. Nothing scrapes your chats in the background.
Turn on continuation checkpoints for Claude Code. When the session fails for reasons that are not your fault, 3Notch can leave a checkpoint the next session can offer you.
New session. Blank agent. You reconstruct the plan from commits, chat scraps, and whatever you still remember. That reconstruction is slow and incomplete—and you pay for it every time the model flakes.
agent How can I help you today? you ok so we were working on the auth you middleware refactor and we'd already you finished the token validation but the you session management piece still needs... you actually wait, let me check what we you committed vs what was in progress... ~20 minutes to get back to where you were.
A fallback packet is already on disk: objective, tasks, git state. The next session can surface it once in chat. Nothing loads into the agent until you confirm.
3notch checkpoint available: auth-middleware-refactor objective: refactor auth middleware completed: token validation, route guards blocked: session store migration next: implement Redis session adapter agent Found a continuation for this stream. agent Want me to load it and continue from Redis? you yes, load it ✓ Loading packet after your confirmation.
Claude Code hooks can write a continuation checkpoint from task state and git—including model-down failures, not only rate limits. Next session can offer it once.
$ notch packet list auth-refactor checkpoint next: Redis session adapter ✓ ready to review
Outgoing agent writes a handoff packet. Incoming agent imports it. No vendor bridge required—Markdown and optional artifacts on disk.
$ notch packet show <id> completed: 4 of 6 tasks blocked: API schema change next: update client types
Hash-verified artifacts for the other machine or repo. Move the archive with scp, git, AirDrop, or whatever you already trust.
$ notch packet pack <id> auth-refactor.notchpkt 3 files · sha256 verified ✓ your transport
Two repos share a mailbox root. Send a packed project packet, forward the text delivery notice (chat, Slack, Claude messaging), then pull, import, and ack.
$ notch send pkt.notchpkt --to local:review notice: pull delivery_… $ notch inbox pull … --import $ notch inbox ack …
You stay in control. Checkpoints are offered, not force-loaded. Packets do not auto-commit or leave the machine unless you move them. Local addresses are routing labels, not authenticated identity.
Packets are files under .notch/. You can open them, diff them, and keep them out of git when they should stay private.
auth-refactor/ ├─ packet.md │ stream: auth-refactor │ completed: token validation │ next: Redis session adapter ├─ manifest.json sha256 verified └─ artifacts/ ├─ session-store.ts └─ migration.sql ✓ Readable now. Portable anywhere.
Create a packet with the objective, completed work, blockers, and next steps—plus files if the other side needs them. Import it in the other tool, or pack a .notchpkt and move it yourself. npm install -g @3notch/cli
With Claude Code continuation checkpoints enabled, 3Notch can write a fallback on rate limits, model-down failures (overload, server error, and related cases), and compaction. The next session may offer that checkpoint once; you approve before anything is loaded.
Use the durable inbox: both stores register the same mailbox root, you send a packed project packet, forward the plain-text delivery notice through any channel you already use, then pull/import/ack on the receiver. Local addresses are labels, not auth.
Yes. MCP for clients that support it; pack/import for everything else. Packets are Markdown on disk, not a proprietary memory store.
No. Memory tools grow one vendor's context window. 3Notch moves selected working state across sessions and tools as files. No embeddings, no hosted index.
MIT. No SaaS tier, no account, no telemetry. Install from npm and run locally.
Install once. Use checkpoints when a session dies. Use packets when work has to move.
@3notch/cli, run notch onboard here, enable continuation checkpoints for Claude Code if needed. Use packets for cross-tool or cross-repo handoffs. Read the package README before changing MCP config.