Claude Code made each of us faster. Now make the team faster.

The decisions, fixes and dead ends from everyone's sessions, shared with everyone on the project.

Free for 30 days, then $10 per user a month. We'll set up the first 20 teams with you.

Without mem-sync

Each person's Claude starts from zero

It re-asks what a teammate settled yesterday and retries the fix that already failed.

With mem-sync

Everyone's Claude starts from the team's notes

What your senior engineer's Claude works out reaches everyone on the project.

Three steps, a few minutes

01
Install the plugin

Paste the three commands below into Claude Code.
02
Link a folder

Choose what to share. Folders you don't link stay on your machine.
03
Keep working

Notes sync every few minutes. Each session starts with the team's.

Claude Code · install mem-sync

/plugin marketplace add thedotmack/claude-mem/plugin marketplace add devplusopsllc/mem-sync-plugin/plugin install mem-sync@devplusopsllc

Catch up on a teammate's work

What changed since your last visit: branch, pull request, files, and what was left open.

Northwind · API Since your last visit

Priya6 notes · last Friapi/rank.ts · api/search.ts

Tom3 notes · last Wedapi/auth/refresh.ts

DECISIONRanking moved to Postgres behind /v2/rank

OPENPaging unstable when scores tie

Ask this space

Ranking now runs on a Postgres full-text index behind /v2/rank [1]. Elasticsearch scores drifted from the database after every nightly import [2].

1. Ranking moves to Postgres behind /v2/rank · Priya · Thu
2. Elastic scores drift after each import · Lena · Wed

Ask why something was decided

Every answer cites the notes it came from, and only uses notes you can see.

Set the rules once for every teammate's Claude

Attach coding standards to a project. Every linked session follows them.

Standards · Northwind

PonytailSmallest change that fully solves the task

API conventionsWritten by your team

Claude · mem-sync connectorclaude.ai

What did the team decide about ranking this week?

Ranking moved to a Postgres full-text index behind /v2/rank, and paging still breaks when two scores tie [1] [2].

1. Ranking moves to Postgres behind /v2/rank · Priya · Thu
2. Paging unstable when scores tie · Priya · Fri

SAVEDYour note "Use a stable tie-break on id" is in Northwind · API

Use it from claude.ai, desktop and mobile

Add the connector, and any Claude chat can search, ask and save notes for the team.

Also included

Delete for everyone

Remove a note from every machine.

Projects and spaces

People see only the projects they work on.

Prompts stay local

Only Claude's short notes are shared.

Inside Claude Code

Sync status under the prompt.

Your sign-in

Your domain and Cloudflare Access, or machine keys.

Your own Postgres

Keep the only copy in your database.

Each team gets its own encrypted database

How we protect your data →

A database per teamIts own login that can't reach any other team.

Encrypted at restAES-256-GCM with a per-team key. Titles are hashed.

Encrypted in transitHTTPS to the hub, verified TLS to every database.

Hosted in the USHetzner, Ashburn, Virginia. Or self-host it.

What it looks like in Claude Code

~/work/northwind-api — claude

Claude Code · northwind-api

mem-sync · 3 notes from your team since your last session

DECISIONRanking moved to a Postgres full-text index behind /v2/rankPriya · Thu BUGFIXToken refresh raced the webhook retry; now a per-tenant lockTom · Wed OPENPaging is unstable when two results tie on scorePriya · Fri

› fix the paging bug Priya left open

● Priya's note says ties happen after the move to Postgres ranking. Adding a stable tie-break on id in api/rank.ts…

mem-sync synced just now northwind-api → Northwind · API

Setting it up? Watch the step-by-step guides

Try it with your team

Free for 30 days. We'll set up the first 20 teams with you on a call.