Your AI session died. Six hours of decisions, constraints, and working state—gone. The next agent starts from scratch because nothing portable survived the switch.
3Notch saves the working state your AI tools won't. Local checkpoints that survive rate limits, context compaction, and model switches. Portable packets when context needs to move across tools, repos, or machines.
npm install -g @3notch/cli
Rate limited at 2 AM. Context window compacted mid-refactor. Switched models because the cap hit at the worst moment. Every time, you rebuild from zero—re-explaining the goal, the constraints, what you already tried.
Your commits, docs, and wiki hold durable knowledge. But the objective you were chasing, the decisions you'd made, the blockers you'd identified, what you'd already verified—that state dies with the session. No AI vendor will fix this. Anthropic won't ship "easily move your context to Codex." OpenAI won't ship "easily move to Claude."
A neutral, locally-owned format is the only place this problem gets solved.
When a session hits a rate limit or compacts, 3Notch saves the working state automatically. When you start a new session, it offers to pick up where you left off.
Your session crashes at 2 AM. You open a new one, re-explain the project, re-describe what you were building, re-list what's done and what isn't. Forty minutes later you're back where you were—if you remembered everything.
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... 40 minutes to get back to where you were.
3Notch saved a checkpoint when the last session ended. The new session finds it, shows you what it contains, and picks up with full context after you approve.
3notch Found checkpoint: auth-middleware-refactor objective: refactor auth middleware completed: token validation, route guards blocked: session store migration next: implement Redis session adapter agent Resume from this checkpoint? (y/n) you y ✓ Resuming. Picking up at Redis session adapter.
Doesn't matter why—3Notch already saved where you were. Your next session offers to pick up exactly where this one stopped.
$ notch packet list auth-refactor checkpoint next: Redis session adapter ✓ ready to resume
The outgoing agent writes a checkpoint: what's done, what's blocked, what's next. The incoming agent reads it and confirms before continuing.
$ notch packet show latest completed: 4 of 6 tasks blocked: API schema change next: update client types ✓ portable across tools
Package the relevant files, decisions, and next steps into a portable packet. The receiving tool picks it up with full context.
$ notch packet pack latest auth-refactor.notchpkt 3 files · sha256 verified ✓ move it however you want
You stay in control. A new session offers the checkpoint once and loads it only after you approve. Nothing commits, pushes, or travels automatically.
A 3Notch checkpoint is a Markdown file you can read, edit, and version like any other file in your repo. Selected files travel alongside it, hash-verified. Everything stays on your machine unless you move it yourself.
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.
3Notch creates portable checkpoints that capture your current objective, completed work, decisions, blockers, and next steps. When you switch from one AI tool to another—say Claude to Codex—the outgoing agent writes a checkpoint and the incoming agent reads it to resume with full context. One install command: npm install -g @3notch/cli
3Notch saves working state when a session hits a rate limit or compacts its context window. When you start a new session, 3Notch offers the latest checkpoint for review and loads it after you approve. You resume in seconds instead of spending 30–40 minutes re-explaining your project.
Yes. 3Notch is vendor-neutral and works with any AI coding tool. It includes a built-in MCP server for tools that support Model Context Protocol (Claude Code, Claude Desktop, Cursor), and portable .notchpkt archives that can be imported into any tool. Checkpoints are plain Markdown files readable by any agent.
Neither. Memory tools help a single AI tool remember more. 3Notch makes working context move between tools. Checkpoints are plain Markdown files with structured frontmatter—no database, no embeddings, no cloud service. You can read, edit, and version them like any other file in your repo.
Completely free, open-source software under the MIT license. No cloud service, no account, no telemetry, no paid tier. Everything runs locally on your machine.
One command to install. Works with Claude, Codex, Cursor, and whatever you switch to next.