jot

io.github.ArpitK24Published by GitHub account ArpitK24v0.2.0Updated Nov 6, 2026

Shared, local-first memory for every AI agent, stored as Markdown and versioned in git.

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Local-first shared memory for AI agents: saves, recalls, updates and deletes Markdown notes stored on disk and versioned in git.

What you can do
  • Save a preference, decision, fact or note, with duplicate detection that points to an existing similar memory instead of saving again
  • Search memory for what is relevant to the current task, ranked by BM25 with boosts for tags and recent updates
  • Rewrite a memory that changed, or delete one
  • List the newest memories, filtered by kind or tags
  • Share one store across agents, with optional per-project memory alongside global memory
When to use it
Useful when you work with several MCP-capable agents and want preferences and decisions told to one to carry over to the others, or when you want agent memory kept as readable files on your own disk rather than in a cloud service.
Requirements
Runs as a local process on the desktop. Install a prebuilt binary for macOS, Linux or Windows (or build with Go 1.23+), then run jot init to create the store; jot setup can write config for Claude Code, Cursor, Codex, Antigravity and Claude Desktop after asking. Store lives in ~/.jot unless JOT_HOME is set. No account or API key.
Before you install
The assistant can write, rewrite and delete memories, and jot setup modifies other tools' config files (undo with jot setup --undo). Memories are plain Markdown in a git repository on disk, so anything saved there is readable by anyone with file access and may be committed to version control; avoid storing secrets.

Installation

In SourceWeft

  1. Open jot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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+:

sh
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:

sh
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/<repo>/.jot/                 optional project memory (jot init --project)

A memory file:

markdown
---id: 20261103-134832-fb9ekind: preferencetags: [js, tooling]source: claude-codecreated: 2026-11-03T13:48:32Zupdated: 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

ToolWhat it does
rememberSave one preference, decision, fact or note. If a similar memory exists, it saves nothing and points to that one instead
recallSearch memory for what's relevant to the task
updateRewrite a memory that changed
forgetDelete a memory
listNewest memories, filtered by kind or tags

CLI

jot init [--project]     jot search <query>     jot show <id>     jot logjot add [-k -t -p] text  jot ls [-k -t]         jot edit <id>     jot wherejot serve                jot rm <id>            jot versionjot setup [--undo]       jot dupes              jot merge <keep> <drop>

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

Source: README.md at commit 5b621ba

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

2
  1. v0.2.0LatestNov 6, 2026
  2. v0.1.1Nov 4, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts