Keep your team’s project notes, decisions, and next steps in sync so Codex and Cursor can pick up where the last session left off.
Confirm the scheduled pilots after Friday’s checks.
Guide the first two accounts through setup.
Pause an in-flight run and verify it resumes safely.
People and agents can read, search, and update the same project notes.
Notes travel over encrypted connections between computers your team owner approves.
Start the next session with the latest decisions and open tasks.
Sign in, then install PeerContext on the computer you want to connect.
Run this on each computer you want to connect.
Requires Node.js 22.22 or newer. Node 24 LTS recommended.
The PeerContext CLI and its dependencies, from npm. Setup connects your agents and preserves existing profiles. After signing in, create a team or join by invitation. An owner approves each new device.
Install into your home directory, then use the full command path:
On Windows, add this folder to your user Path for new terminals. Use .cmd commands without changing PowerShell execution policy.
Want your agent to set it up? Share the install guide.
History is signed and encrypted on approved computers. An open Markdown workspace contains readable files. This dashboard reads notes from your local PeerContext service; the website doesn’t store them.
Supabase stores account, team, and device metadata. Cloudflare delivers sign-in email and relays encrypted updates without keeping document history.
You can edit an open Markdown workspace offline. Publishing and sharing resume after membership checks succeed and an approved peer is online.
Removing a device changes the keys for future updates. It can’t erase copies the device already has.
Browse a fictional team’s notes, decisions, and tasks. No setup required.