thread-keeper

Name: thread-keeper
Author: po4erk91

by po4erk91version 0.13.1i★ 18iRuns on your computer

Registry nameio.github.po4erk91/thread-keeper

How to install

What it does

Multi-agent shared brain across Claude, Codex, Antigravity, Gemini, Copilot, and VS Code.

Connects Runs on your computer
Account or key No key needed
Category Developer tools

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

ClaudeWeb · app · phoneChatGPTWebClaude CodeTerminalCursorCode editorVS CodeCode editorOtherOther apps

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Install Python (uv)
One time only; it works for every server that needs Python (uv)
Open the Python (uv) download page ↗
Done
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Done

Paste these settings and save the file

{
  "mcpServers": {
    "thread-keeper": {
      "command": "uvx",
      "args": [
        "threadkeeper"
      ]
    }
  }
}

Done

Quit Claude and open it again
Done
Try it
Use thread-keeper and tell me what you can do for me, then show me one thing
✓ If Claude says it is using thread-keeper or shows a thread-keeper tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect thread-keeper yet

thread-keeper runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect thread-keeper

Steps for Claude →Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Steps for Claude Code →Install Python (uv) on your computer first (one time)
Steps for Cursor →Install Python (uv) on your computer first (one time)
Steps for VS Code →Install Python (uv) on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Sentry✓ ChatGPT
Compiler Explorer✓ ChatGPT
GitDiagram✓ ChatGPT

Works with Claude Code, with some setup first

Install Python (uv) on your computer first (one time)

Install Python (uv)
One time only; it works for every server that needs Python (uv)
Open the Python (uv) download page ↗
Done
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Done

Paste this command and press Enter

claude mcp add --scope user thread-keeper -- uvx threadkeeper

Done

Type /mcp in Claude Code
You should see thread-keeper listed as connected
Done
Try it
Use thread-keeper and tell me what you can do for me, then show me one thing
✓ If Claude Code says it is using thread-keeper or shows a thread-keeper tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Python (uv) on your computer first (one time)

Install Python (uv)
One time only; it works for every server that needs Python (uv)
Open the Python (uv) download page ↗
Done
Click this button to open Cursor
Open in Cursor
Cursor asks you to confirm; click Install
Done
Open the AI chat in Cursor in Agent mode
Done
Try it
Use thread-keeper and tell me what you can do for me, then show me one thing
✓ If Cursor says it is using thread-keeper or shows a thread-keeper tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Python (uv) on your computer first (one time)

Install Python (uv)
One time only; it works for every server that needs Python (uv)
Open the Python (uv) download page ↗
Done
Click this button to open VS Code
Open in VS Code
VS Code asks you to confirm; click Install
Done
Open the AI chat in VS Code in Agent mode
Done
Try it
Use thread-keeper and tell me what you can do for me, then show me one thing
✓ If VS Code says it is using thread-keeper or shows a thread-keeper tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use thread-keeper💬 Discussion →

For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user thread-keeper -- uvx threadkeeper

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "thread-keeper": {
      "command": "uvx",
      "args": [
        "threadkeeper"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "thread-keeper": {
      "command": "uvx",
      "args": [
        "threadkeeper"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "thread-keeper": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "threadkeeper"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub stars i: 18
Downloads per weeki: 260/wk
Licence i: MIT
Connection: Runs on your computer
Transport: stdio
Latest versioni: 0.13.1
Categoryi: Developer tools
Published to registryi: Jun 15, 2026
Code last changedi: Nov 14, 2026
Maker: po4erk91
Packages: pypi: threadkeeper
Repo: po4erk91/thread-keeper
Registry status: Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account po4erk91, which owns the repo
✓ Pass
Still maintained
Code last changed today
✓ Pass
Has a licence
Uses MIT
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

User reviews

No reviews yet

Compared with others in Developer toolsi

More stars than 92% of the other 5886 servers in this category
Published to the registry more recently than 16% of the other 5886 servers in this category
Basic checks equal to or better than 100% of the other 5886 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is thread-keeper safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed today, and the latest version (0.13.1) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: REA, GitHub, Serena MCP: the IDE for your agent

Others in the same category

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 457.7KUpdated 2 days ago

Runs on your computer

Install

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.4KUpdated 11 days ago

Computer or cloud

Install

Serena MCP: the IDE for your agent

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

by oraiosWidely used↓ 35.2K/wk★ 31.4KUpdated 6 months ago

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

thread-keeper

Multi-agent shared brain across Claude Code/Desktop, Codex, Antigravity CLI (`agy`), Copilot, and VS Code. Cross-session memory, self-improving skill loops, and inter-agent signaling — one local MCP server turns parallel agent instances into a coordinated multi-agent system instead of N isolated chats.

Every connected client (Claude Code, Claude Desktop, Codex CLI + desktop, Antigravity CLI, Copilot, every MCP-aware VS Code extension) shares one SQLite store, one set of threads, one user model, and one learning loop that improves the skill library autonomously over time.

The brief format is dense — structural tags, opaque IDs, ~6 KB per session-start injection. Optimized for agent consumption, not human reading.

Why

Every agent CLI starts cold. Context dies at session boundaries. Skills you taught Claude don't transfer to Codex. Threads you closed in yesterday's Antigravity chat are invisible to today's Copilot. Parallel agent instances running the same task don't know about each other and duplicate work or step on each other's writes.

thread-keeper is the substrate underneath. Three things that together make it more than a memory store:

Collective memory — threads, notes, verbatim quotes, dialectic claims about you. Survives session, restart, CLI swap. One agent records, every other agent (any CLI) reads. The brief injected at session start gives a new agent everything the previous one knew.
Multi-agent coordination — spawn primitive launches child agents in parallel, each gets a self_cid + sees the same memory. broadcast / whisper / inbox / wait / ask / respond let concurrent sessions signal each other across CLIs. Parent / children / sibling agents become a coordinated swarm, not isolated chats.
Self-improving skill library — autonomous background loops (auto-review on thread close, shadow-review daemon, extract harvester, candidate-reviewer, weekly Curator, and a thread-janitor that auto-closes idle threads so abandoned work reaches the harvest path — closing is reversible, a note reopens a closed thread) materialize class-level skills as the agents work. Adapted to multi-CLI: SKILL.md is the primary write target and gets mirrored to every known/configured skills root simultaneously (~/.claude/skills/, ~/.codex/skills/, ~/.gemini/config/skills/ for Antigravity, existing ~/.agents/skills/, extra roots from THREADKEEPER_EXTRA_SKILLS_DIRS, and ~/.threadkeeper/skills/), with lessons.md as a fallback for CLIs without a native skills loader. A managed skill write reports success only after every mirror has the expected file set and hashes; ERR mirror_partial_failure keeps the canonical copy and names only the affected consumer plus relative file. Retry safely with skill_manage(action="reconcile", name=" ").

Foreground MCP servers also run a daily self-update check by default. Source checkouts fast-forward their tracked git branch and reinstall the editable package; PyPI/pipx/venv installs run pip install --upgrade in the current interpreter environment only after the latest PyPI release files have matching Integrity API provenance from the expected GitHub Trusted Publisher. Dirty or diverged git checkouts are skipped rather than overwritten. Restarts are gated on install/setup success plus a subprocess import smoke check, so a broken or unverified update is recorded but the current server keeps running. Interpreters without pip (uv-created or pipx venvs) install through uv pip install --python when uv is available. Upstream PyPI publishing is intentionally gated: green merge-to-main builds are auto-tagged, but every upload pauses for a human approval on the protected pypi GitHub Environment (a maintainer-signed annotated v* tag remains the manual override path), as described in docs/RELEASING.md.

They also run a twice-weekly installed-skill updater by default. It keeps all configured CLI skill roots in sync, adopts newer local copies installed into a non-primary root, and updates GitHub-backed skills when a tracked upstream source changes.

Quickstart

The shortest path — PyPI + pipx (recommended):

pipx install 'threadkeeper[semantic]' && thread-keeper-setup

thread-keeper-setup detects every CLI you have installed (Claude Code / Claude Desktop / Codex CLI + desktop / Antigravity CLI agy / Copilot / VS Code), registers the MCP server in each one's config, copies hooks to ~/.threadkeeper/hooks/, and writes a managed instructions block into each CLI's per-user instructions file (CLAUDE.md / AGENTS.md / copilot-instructions.md — Claude Desktop and VS Code have no global instructions file, so that step is skipped for them). The generated MCP entry pins imports to this configured installation, so an agent launched inside another thread-keeper checkout cannot load that checkout's unmerged code against the live memory database.

Restart your CLI of choice. Hook-capable clients inject a brief on the first message; hookless clients such as Codex and Antigravity CLI either follow the managed instructions block and call brief() / context() before answering, or — on hosts that support MCP resources — pull the brief as the read-only memory://brief resource the host attaches automatically (see MCP primitives).

The MCP initialization response also carries concise, static lifecycle guidance: load the brief/context, open/note/close substantive threads, prefer read-only resources for host-attached context, and use dry-run plus confirmation before destructive maintenance. Hooks and the managed files remain reinforcement for clients that do not surface server instructions.

Portable plugin install

Hosts that load Agent Plugins 1.0 skills and stdio MCP servers can use the thread-keeper-agent-plugin-vX.Y.Z.zip asset from GitHub Releases. Install uv so uvx is on the host's PATH, extract the archive, then use the host's plugin loader on that directory. The plugin starts the matching ThreadKeeper release and provides a bootstrap skill with the same lifecycle guidance as setup.

You can also export the plugin from an installed release without changing any host configuration:

thread-keeper-setup --export-plugin ./thread-keeper-plugin

Plugin support depends on the host and version; an MCP or Skills loader alone does not imply Agent Plugins support. For hosts without that support, use pipx/uv plus thread-keeper-setup as above. Adapter hooks and learned-skill mirroring remain available. See installation, upgrades and removal for the differences, including how to avoid duplicate registrations.

Alternative installs

If you don't have pipx and don't want to install it:

# uv (Rust-fast Python tool runner) — no clone, single binary on PATH

uv tool install 'threadkeeper[semantic]' && thread-keeper-setup

Plain pip into a venv

python3 -m venv ~/.threadkeeper-venv ~/.threadkeeper-venv/bin/pip install 'threadkeeper[semantic]' ~/.threadkeeper-venv/bin/thread-keeper-setup

For development (editable install from a git checkout) or to track the bleeding edge:

# One-liner installer — clones to ~/thread-keeper, makes a venv,

editable-installs, wires every detected CLI. Idempotent — re-run to

update (it git-pulls + reinstalls).

curl -fsSL https://raw.githubusercontent.com/po4erk91/thread-keeper/main/install.sh | bash -s -- --semantic

Or fully manual

git clone https://github.com/po4erk91/thread-keeper ~/thread-keeper cd ~/thread-keeper && python3 -m venv .venv .venv/bin/pip install -e '.[semantic]' .venv/bin/thread-keeper-setup

To preview without writing anything:

thread-keeper-setup --dry-run

Multi-CLI integration

CLI	MCP config	Instructions file	Hooks	Transcripts ingested
Claude Code	`~/.claude.json` `mcpServers`	`~/.claude/CLAUDE.md`	`~/.claude/settings.json` `hooks`	`~/.claude/projects/*/.jsonl`
Claude Desktop	`~/Library/Application Support/Claude/claude_desktop_config.json` `mcpServers` (macOS); `%APPDATA%\Claude\…` (Win); `~/.config/Claude/…` (Linux)	none (GUI-only)	not supported by the app	none — chats live in Electron IndexedDB
Codex (CLI + desktop)	`~/.codex/config.toml` `[mcp_servers]` (shared between CLI and `Codex.app`)	`~/.codex/AGENTS.md`	not supported	`~/.codex/sessions/*/rollout-.jsonl`
Antigravity CLI (`agy`)	`~/.gemini/config/mcp_config.json` `mcpServers`	`~/.gemini/config/AGENTS.md`	not wired yet	`~/.gemini/antigravity-cli/conversations/*.db` (sqlite/protobuf, read-only: user prompts and final answers)
Copilot	`~/.copilot/mcp-config.json` `mcpServers`	`~/.copilot/copilot-instructions.md`	`~/.copilot/hooks.json`	`~/.copilot/session-store.db` (sqlite)
VS Code	`~/Library/Application Support/Code/User/mcp.json` `servers` (macOS); `%APPDATA%\Code\User\mcp.json` (Win); `~/.config/Code/User/mcp.json` (Linux)	none (per-workspace only)	not supported	none — extensions own their history

Every CLI that produces parseable transcripts feeds the same dialog_messages table with a source tag, so dialog_search() finds matches regardless of where the conversation happened. Claude Desktop and the VS Code adapter are the exceptions — MCP registration only; their chats don't reach the table for now (Electron IndexedDB on the Claude Desktop side; per-extension stores on the VS Code side). Antigravity keeps one SQLite file per conversation with protobuf step payloads; thread-keeper opens it read-only (never creating WAL sidecars next to it) and keeps only user prompts and final model answers, skipping tool calls and thinking.

VS Code's user-level mcp.json is the central host that every MCP-aware VS Code extension consumes — GitHub Copilot Chat, the Anthropic Claude IDE plugin, the OpenAI Codex IDE plugin, Continue, Cline, … — so a single registration there reaches all of them at once.

Adding a new CLI = one file under threadkeeper/adapters/ implementing the CLIAdapter contract. See CONTRIBUTING.md.

Python MCP SDK surface

thread-keeper requires MCP Python SDK 2.3 or later (mcp>=2.3.0,<3). Its stable Skills and durable Tasks extensions use the MCP 2026-07-28 extension surface, while tools, resources, prompts, annotations, structured content, elicitation, and stdio continue to use the same MCPServer instance.

MCP primitives (tools, resources, prompts, Apps, elicitation)

MCP has three server primitives. thread-keeper uses all three, mapped to the read/act split, plus MCP elicitation for host-native confirmations:

Primitive	Control	What thread-keeper exposes	When to use
Tools	model-controlled (may act)	the full surface — `brief`, `note`, `spawn`, `search`, `curator_review`, `wikilink_health`, …	the agent decides to call them
Resources	application-controlled, read-only	`memory://brief`, `memory://context`, `memory://dashboard`, `memory://agent-status`	the host attaches/pulls them automatically; capable hosts may subscribe
Prompts

Only the beginning is shown; read the rest in the repo

thread-keeper

What it does

Install

Install Python (uv)

Open the Claude desktop app’s settings file

Paste these settings and save the file

Quit Claude and open it again

Try it

What you can do instead

Install Python (uv)

Open Terminal

Paste this command and press Enter

Type /mcp in Claude Code

Try it

Install Python (uv)

Click this button to open Cursor

Open the AI chat in Cursor in Agent mode

Try it

Install Python (uv)

Click this button to open VS Code

Open the AI chat in VS Code in Agent mode

Try it

Installed on your computer

At a glance

Which apps can use it

Related guides

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Discussion

User reviews

Compared with others in Developer toolsi

Common questions

Others in the same category

REA

GitHub

Serena MCP: the IDE for your agent

README from the maker

thread-keeper

Why

Quickstart

Portable plugin install

Alternative installs

Plain pip into a venv

editable-installs, wires every detected CLI. Idempotent — re-run to

update (it git-pulls + reinstalls).

Or fully manual

Multi-CLI integration

Python MCP SDK surface

MCP primitives (tools, resources, prompts, Apps, elicitation)