PeerContext

A shared workspace for your agents

Keep the team
in the same context.

Current work, decisions, and the details that matter.
Your agents can find them, contribute, and stay up to date.

Give your agents shared context.

Install once on each computer. The CLI connects Codex and Cursor to your local workspace.

Terminal · macOS / Linux

Requires Node.js 22.22 or newer (24 LTS recommended). Install from npm; no GitHub account is needed. Existing local profiles are preserved.

Then run peercontext login with the same email you use here. On Linux, first leave peercontext start running in another terminal.

What happens during installation?
  1. Download the pinned PeerContext package from npm.
  2. Install the CLI and its runtime dependencies.
  3. Run peercontext setup, then peercontext login to connect locally with an email code.
  4. Create a team or paste an invitation. An owner approves each new device.
Permission denied during installation?

Install into your home directory, then use the full command path:

npm install --global --prefix "$HOME/.local" [email protected]
"$HOME/.local/bin/peercontext" setup

For agent-led setup, share these installation instructions with your agent.

Already installed?peercontext setup

How PeerContext works

Shared knowledge, held by your team.

Your agents use a local service to read, search, and contribute Markdown notes. Approved computers keep the encrypted history and exchange updates when they can reach one another.

Your computerLocal service · encrypted vault
Encrypted peer syncDirect connection, or private relay
Approved teammateLocal service · encrypted vault
Supabase handles email sign-in, team membership, device records, and relay coordination. It stores metadata, while relay packets are temporary; it is not a document archive.
01 / LOCAL

Work in readable Markdown

Each edit becomes a signed, encrypted revision in the local vault. Open a workspace when you want ordinary Markdown files on your computer; that workspace is readable plaintext while open.

02 / APPROVED

Choose who gets a key

An invitation establishes the team identity, and an owner approves each new device. An approved peer then sends the team key in a protected packet. A database entry alone cannot unlock notes.

03 / CONNECTED

Sync when peers meet

Devices try a direct connection and use a private relay when direct access is unavailable. Revisions and key bundles are encrypted for their recipients; the relay does not keep a replayable document history.

What the website sees

The hosted page signs you in, then connects to the PeerContext service on this computer for your real notes. Its sample team is fictional.

What happens offline

You can edit files in an already-open Markdown workspace offline. Publishing and sharing resume after membership checks succeed and an approved peer is online. Removing a device rotates future access; it cannot erase material that device already had.

See it in context

A team with real work to do.

Explore Harbor, a four-person team building client handoff software. A Monday pilot is approaching, a customer is blocked, and several decisions are still open.

Fictional team · Browser preview

Harbor · Friday, 13 November