Teamshare

teamshare

Shared team context for coding agents. One engineer tells their agent "share with the team that X"; every teammate's agent surfaces it at the start of their next session.

What it is

A dev team where everyone uses Claude Code has no shared agent memory. When one engineer learns something the whole team needs — "auth middleware is being refactored, don't touch `src/auth` until Friday" — it travels by Slack and gets lost. teamshare fixes this: the engineer tells their agent to share it, and every teammate's agent surfaces it at the start of its next session — "Adnan shared team context — want to see it?" Answering yes *or* no counts as a read receipt. Anyone who connects joins the team's shared memory.

It's two pieces: `teamshare-server`, a small self-hosted MCP server backed by one SQLite file, and thin client adapters — a Claude Code plugin, and one dependency-free connect script for every other assistant, runnable with plain `node` and no install step. The server speaks plain MCP over HTTP, so any MCP-capable agent can join.

Install the server

One person on the team runs the server, once:

pnpm install
pnpm -r build
node packages/server/dist/cli.js serve

Every command in this README is shown as `node packages/server/dist/cli.js `, run from a checkout of this repo — that's what's verified below. The package's bin is named `teamshare` (`packages/server/package.json`), so if you've installed or linked it globally, drop the `node .../cli.js` prefix and just run `teamshare `.

First run prints the team token **exactly once**:

teamshare server listening on port 8787
database: /Users/you/.teamshare/teamshare.db

Team token (share with teammates — for Claude Code they install the plugin and are
prompted for it; for other assistants, run `teamshare connect`):

  ts_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

WARNING: serve plain HTTP only on a trusted network. Put TLS in front for anything else.

Cop