Session Hub

See what your teammates did with their AI — and let your AI ask them. Share Claude Code and Cursor sessions across your team: peer‑to‑peer, end‑to‑end encrypted, with signed identities and an MCP server built in.

English · Español

Demo data. Interface in English and Spanish.

Why

Your backend teammate spent the morning with Claude Code changing an API. You, on the frontend, find out hours later — or never. Session Hub turns those AI conversations into shared, searchable team context:

"What did Carlos change in the backend today?" — ask your own AI, get the answer from his real sessions.

Related MCP server: Covalent Bond

Features

Quick start

cursor --install-extension session-hub.vsix     # or: code --install-extension session-hub.vsix

Download session-hub.vsix from the latest release. No Node.js install needed — the hub runs on the editor's own runtime.

1. Create a team in the Session Hub sidebar (first person only).

2. Invite — copies a one‑time SH2-… code (valid 48 h). Any member can invite.

3. Join — paste the code. The inviter's hub confirms you automatically when both are online.

4. Share a project and pick who can see it.

📘 Full guide for non‑technical users: docs/MANUAL.md

How it works

flowchart LR
  subgraph A["Carlos's machine"]
    AI1["AI · Cursor"] -->|MCP · 127.0.0.1| H1["Hub"]
  end
  subgraph B["Ana's machine"]
    AI2["AI · Claude Code"] -->|MCP · 127.0.0.1| H2["Hub"]
  end
  subgraph C["Pedro's machine"]
    AI3["AI · VS Code"] -->|MCP · 127.0.0.1| H3["Hub"]
  end
  H1 <-->|"encrypted · authenticated"| H2
  H2 <-->|"encrypted · authenticated"| H3
  H1 <-->|"encrypted · authenticated"| H3

• The API and MCP of each person listen only on 127.0.0.1; your AI talks only to your own hub.

• Each hub is its owner's orchestrator: it asks the other hubs in parallel, merges answers and labels whose they are. A slow teammate never blocks the rest (10 s timeout per call).

• Each hub answers only for its owner, with its owner's rules, and logs every read.

• Membership is a certificate chain rooted at the team founder: invite → member → admission. A leaked invite can't admit a second person.

Remote, step by step. Your own infrastructure (bootstrap nodes + a blind relay that only forwards encrypted bytes) starts with one command:

npm run infra -- --host 203.0.113.10     # prints the settings every teammate pastes
npm run infra -- --public                # relay only, on the public network

VPNs (WireGuard, Tailscale, corporate) are detected and advertised automatically. If a connection fails because of a network policy (UDP blocked, strict NAT, unreachable relay…), Session Hub tells you why and Copy connection report produces a ready‑to‑send message for IT.

Language: the interface follows the editor language (Spanish or English); force it with sessionHub.language.

MCP tools

All tools accept peer (name, fingerprint, "me" or "all"). Empty results explain why (nobody online vs. nothing shared).

Command line (no editor)

npm install
npm run setup -- --name Ana --role frontend /path/to/project=my-api
npm run setup -- team create "dev-team"     # or: npm run setup -- team join SH2-…
npm start
npm test

Security

Threat model and known limitations: SECURITY.md. Report vulnerabilities privately to carlosvisbal66@gmail.com.

Contributing

Pull requests welcome under the DCO (git commit -s) — no copyright assignment. See CHANGELOG.md.

License

Session Hub is free software under the GNU Affero General Public License v3.0 or later. © 2026 Carlos Visbal and the Session Hub authors (AUTHORS). If you modify it and let others use it over a network, you must offer them your source (AGPL §13) — the hub does this automatically at /source.

Not affiliated with Anysphere (Cursor) or Anthropic (Claude Code). See NOTICE.