Commons Memory

Shared memory, work claims and handoffs so parallel AI coding sessions stop colliding.

LLM Mart 0 views 36 listing impressions

Run several Claude Code sessions at once without them redoing or overwriting each other's work.

Each session (say, one per git worktree) checks in with Commons before it starts a task. If another session already has it, it hears so and backs off. Finished work, decisions and handoffs are shared, so the next session builds on them instead of starting over. Everything lives in one local SQLite file: no API keys, no account, no telemetry.

/plugin marketplace add Neoo-Blue/commons-memory
/plugin install commons@commons-memory

Needs uv. Each folder is one agent (claude-code@<folder>), so run parallel sessions in separate worktrees or checkouts with different folder names.

Two sessions, two worktrees, same task:

claude-code@payments-fix   start_work("fix the payments retry", paths=["pay.py"])
                           -> ok: it's yours, others are warned off
claude-code@billing-ui     start_work("fix the payments retry", paths=["pay.py"])
                           -> busy: claude-code@payments-fix has it since 02:33.
                              msg_send them to split it, or wait for their finish_work.

It works alongside claude-mem and Claude Code's own memory: those help one session remember, Commons keeps several sessions from colliding. The plugin lists 19 tools (memory and coordination only). Credential and vault tools are not listed and nothing asks for a key; they stay reachable through call() only if you set up a vault yourself. How it stays safe: docs/threat-model.md.

Beyond one machine: the hub

The same Commons runs as a small self-hosted hub, so sessions on different machines, and other AIs (Codex, Cursor, Gemini CLI, ChatGPT, Grok), share one view of who is doing what.

Commons is a self-hosted memory and coordination hub that every AI connects to over MCP. It works with Claude, ChatGPT, Grok, Cursor, Codex, Gemini and your own agents. They share memory, pick up each other's unfinished work, message and wake each other, learn how you like things done, and split big jobs into reviewed, debated, budgeted subtasks. One SQLite file (or Postgres) holds it all. A dashboard shows who is doing what and what it costs.

Commons dashboard

curl -fsSL https://raw.githubusercontent.com/Neoo-Blue/commons-memory/main/install.sh | sh
irm https://raw.githubusercontent.com/Neoo-Blue/commons-memory/main/install.ps1 | iex     # Windows

That one line is the whole setup: it installs Commons, starts the hub and dashboard now and at every login, and connects every AI CLI it finds on the machine (key, MCP, instructions, hooks, instant wake). Nothing else to do; the dashboard is at http://127.0.0.1:8766 whenever you want to look. commons up repeats it after you install another AI.

Docker: see docs/docker.md. Prefer to read it first? curl -fsSLO https://raw.githubusercontent.com/Neoo-Blue/commons-memory/main/install.sh && less install.sh && sh install.sh. No-script alternatives: uvx --from git+https://github.com/Neoo-Blue/commons-memory commons init (run without installing) · uv tool install "commons-memory[http] @ git+https://github.com/Neoo-Blue/commons-memory" · pipx install "commons-memory[http] @ git+https://github.com/Neoo-Blue/commons-memory"

Contents

Quickstart · Feature tour · Architecture · Connect any AI · Screenshots · Multi-agent · Security · Networking · Configuration · Troubleshooting · FAQ · Comparison · Roadmap · Changelog

From the project's README.