3notch

3Notch

**Save the working state your AI tools won't.**

[Website](https://3notch.dev) · [Docs](https://3notch.dev/docs/) · [Quickstart](https://3notch.dev/docs/quickstart/) · [npm](https://www.npmjs.com/package/@3notch/cli)

[](https://github.com/coldlogicAI/3notch/actions/workflows/ci.yml) [](https://www.npmjs.com/package/@3notch/cli) [](https://nodejs.org) [](LICENSE) [](https://glama.ai/mcp/servers/coldlogicAI/3notch)

A Claude Code session dies mid-run — rate limit, crash, compaction, laptop sleep — or you're moving a task from Claude Code to Codex, Cursor, or ChatGPT. The code is still in git. The objective, decisions, and next steps often are not. The next session rebuilds that state from scratch.

3Notch is a **local CLI and MCP server** for:

• Continuation checkpoints — when Claude Code is configured, recover after rate limits, model-down failures, and compaction
• Portable packets — hand off selected work across tools, repos, and machines
• Durable inbox — async delivery between stores that share a mailbox root

No cloud service. No account. No telemetry. Records stay on disk as Markdown (and optional artifacts) under `.notch/`.

---

Why this layer exists

Every major vendor ships transcript persistence and memory files. None ship durable **working state**:

• Claude Code auto-saves transcripts and takes file checkpoints — but checkpoints are session-scoped undo, gone when the session ends.
• OpenAI's Agents SDK serializes RunState — at planned human-approval pauses, not arbitrary failures.
• Gemini and Grok per