jot

jot

Shared, local-first memory for every AI agent.

Tell Claude Code you use pnpm, and Cursor already knows it tomorrow. jot is one memory on your machine that every MCP-capable agent can read and write. It's stored as plain Markdown and versioned in git.

$ jot add -k preference -t js "Use pnpm, never npm"

remembered 20261103-134832-fb9e (global)

$ jot search "package manager" 20261103-134832-fb9e preference global Use pnpm, never npm #js

Why

• One memory, every agent. Claude Code, Cursor, Codex and any MCP client share it.
• Yours, on disk. Each memory is a readable .md file. No cloud, no account, no database.
• Git-versioned. Every change is a commit, so you get diffs, blame and undo for free.
• Zero dependencies. A single static Go binary using only the standard library.

Install

Download a binary for macOS, Linux or Windows from Releases, or build with Go 1.23+:

go install github.com/ArpitK24/jot/cmd/jot@latest

It's also listed on the official MCP Registry as io.github.ArpitK24/jot, with one-click .mcpb bundles on every release.

Then create your memory store:

jot init

Then connect your agents. jot setup finds Claude Code, Cursor, Codex, Antigravity and Claude Desktop, shows the exact lines it will add to each config, and asks once before writing:

$ jot setup

Claude Code will connect ~/.claude.json Cursor connected ~/.cursor/mcp.json Codex will connect ~/.codex/config.toml Antigravity not installed ~/.gemini/config/mcp_config.json Claude Desktop not installed ~/Library/Application Support/Claude/claude_desktop_config.json ... Connect 2 tools? [y/N]

Undo it with jot setup --undo. To configure a tool by hand, see docs/setup.md.

How it works

~/.jot/                      global memory (or $JOT_HOME)

20261103-134832-fb9e.md .git/ /.jot/ optional project memory (jot init --project)

A memory file:

---

id: 20261103-134832-fb9e kind: preference tags: [js, tooling] source: claude-code created: 2026-11-03T13:48:32Z updated: 2026-11-03T13:48:32Z

---

Use pnpm, never npm.

Recall uses BM25 ranking with boosts for tag matches and recent updates, across project memories and then global ones.

MCP tools

CLI

jot init [--project]     jot search <query>     jot show <id>     jot log

jot add [-k -t -p] text jot ls [-k -t] jot edit jot where jot serve jot rm jot version jot setup [--undo] jot dupes jot merge

Duplicates

Agents often save the same thing twice in different words. jot dupes lists likely pairs, and jot merge keeps the newer one, adds any sentence only the other one had, and removes it in one commit. Git still has the original.

$ jot dupes

66% 20261106-091200-a3f9 global claude-code Use pnpm for every JS project... 20261104-180511-7be0 global cursor Use pnpm for every JS project... jot merge 20261106-091200-a3f9 20261104-180511-7be0

Roadmap

• Merge near-duplicate memories instead of piling them up
• jot setup to connect installed agents in one step
• Expiry and review for stale facts
• Optional local embeddings (Ollama) for semantic recall
• jot sync through a git remote across machines
• TUI browser

License

MIT