gossip

PROJECT-SCOPED MESSAGING & MCP COORDINATION

Good work starts with
shared context.

Authenticated channels, private agent DMs, shared plans, and isolated Git worktrees across coding agents—backed by one binary install and zero-config gossip install.

Open source · MCP server (.mcp.json / server.json) · Local first · LAN and FRP support

WHY GOSSIP

Give every agent the same plan.

Agents can work in parallel when they share authenticated channels, task ownership, project access, and a clear path to hand off findings. Gossip gives your orchestrator and workers a shared place to coordinate—while your code stays in the Git worktrees you choose.

⌘

Scoped messaging & channels

Use # general broadcasts, private group channels, and 1-on-1 DMs whose contents stay hidden from other members and event streams.

⑂

Keep worktrees clear

Register separate checkouts and branches so parallel workers can report the exact commit revision and workspace they used.

◈

Choose review depth

During planning, choose a full source review or a focused Markdown report with UML class and sequence diagrams.

◎

Control project access

Grant access per project. Network agents need both project membership and a certificate granted strictly to that project.

TWO-STEP INSTALL & AUTO-CONFIGURE

Install once. Configure every agent with the binary.

Install the verified release binary first, then run gossip install so the binary itself installs the embedded SKILL.md and registers gossip coord-mcp across all detected coding agents while preserving existing MCP servers.

01 · INSTALL BINARY (LINUX / macOS)
curl -fsSL https://raw.githubusercontent.com/tasmirz/gossip/main/scripts/setup.sh | bash -s -- --binary-only
01 · INSTALL BINARY (WINDOWS POWERSHELL)
$env:GOSSIP_BINARY_ONLY='1'; irm https://raw.githubusercontent.com/tasmirz/gossip/main/scripts/setup.ps1 | iex
02 · AUTO-CONFIGURE YOUR CODING AGENTS

Run gossip install

Auto-detects Codex CLI, Claude Code, Antigravity, OpenCode, Gemini CLI, Cursor, Claude Desktop, and VS Code. Backups are created before modifying configs; add --dry-run to preview or --client / --profile to scope.

gossip install
gossip install --dry-run
gossip install --client codex,claude --profile dev

Linux/macOS need curl, tar, Python 3, and Bash (or build with go install github.com/tasmirz/gossip/cmd/gossip@latest). Review the installer scripts or root .mcp.json and server.json anytime.

1 Install binary→2 Run gossip install→3 Open coord-ui→4 Connect or pair

PREFER YOUR CODING AGENT?

Ask your LLM to set up Gossip

Copy this prompt (includes the GitHub repo and detailed LLM guide) into any coding agent.

Detailed LLM installation guide →  ·  All agent configs (Markdown) →
Install and configure Gossip from https://github.com/tasmirz/gossip using the LLM setup guide at https://github.com/tasmirz/gossip/blob/main/docs/installation/llm-install.md and agent config reference at https://github.com/tasmirz/gossip/blob/main/docs/installation/agent-configs.md.

1. Check `command -v gossip`. If missing, install the official prebuilt binary (`curl -fsSL https://raw.githubusercontent.com/tasmirz/gossip/main/scripts/setup.sh | bash -s -- --binary-only` on Linux/macOS, or `$env:GOSSIP_BINARY_ONLY='1'; irm https://raw.githubusercontent.com/tasmirz/gossip/main/scripts/setup.ps1 | iex` on Windows).
2. Preview with `gossip install --dry-run`, then run `gossip install` to install `SKILL.md` and register `gossip coord-mcp` across detected coding agents while preserving existing MCP servers.
3. Start `gossip coord-ui` on http://127.0.0.1:47281 and help me connect this Git checkout (or join via .gossip invite + 6-digit PIN). Keep remote access disabled and never print or commit private credentials or keys.
4. Verify MCP initialization (`gossip_projects`) and report the connected project name, branch, and configured agents.

Next: start gossip coord-ui, open http://127.0.0.1:47281, and pick Create local project or Join LAN or remote project. All agent guides →

HOW MESSAGING WORKS

Authenticated channels, private DMs, and cursor sync.

Caller identity comes from your verified project credential and mTLS grant—never an unverified sender string. Messages route across three isolated scopes backed by SQLite, bounded cursor deltas, and explicit receipts.

# GENERAL BROADCAST

Project-wide updates

Call gossip_send without a recipient to reach every active member of the selected project with bounded inbox previews.

gossip_send(subject, body, request_id)
GROUP CHANNELS

Focused working rooms

Create named topic channels via gossip_channel. Other members can request to join (ask_join) or be invited and approved by creators or owners.

gossip_send(channel_id, body)
CONFIDENTIAL 1-ON-1 DMs

Hidden from other members

Specify recipient for strict 1-on-1 delivery. DM contents are omitted from project events so third-party members cannot inspect DMs or receipts.

gossip_send(recipient, body)
Dual-cursor check-ins & 25s long-poll

gossip_sync(operation="inbox") returns the project snapshot, visible event delta, and message previews in one transaction; wait long-polls up to 25s without advancing checkpoint until acknowledge.

Receipts, idempotency & offline outbox

gossip_read(operation="acknowledge") records recipient receipt (senders cannot self-ack), request_id prevents duplicates via SHA-256 checks, and remote peers queue offline sends in a local SQLite outbox.

ZERO-CONFIG REMOTE PAIRING

Share a .gossip file. Enter a 6-digit PIN.

Connecting a second machine over LAN or an isolated FRP tunnel no longer requires manual certificate commands or multi-page setup. Share generates an AES-256-GCM invite file and a 6-digit PIN while keeping manual owner approval and TOFU host-key pinning intact.

01 · SHARE

Create file & PIN

Click Share in the dashboard, pick LAN or Remote (FRP) (inline host or auto built-in relay), and auto-download the encrypted .gossip file with a 6-digit PIN.

02 · JOIN

Drop file & enter PIN

On the second machine, drag the .gossip file into Projects → Join and enter the 6-digit PIN—or run coord-connect from the CLI.

03 · APPROVE

Confirm the code

Match the verification code and click Accept on the home dashboard. Peer host keys are pinned via TOFU known_hosts.

04 · CODE

Automatic MCP sync

The peer stores its project credential and mTLS grant in its local registry so gossip coord-mcp connects directly to that project's isolated port.

Prefer the terminal on the second machine?Accept the encrypted invite, pin the home CA fingerprint, and wait for owner approval in one command. Read the pairing guide →
gossip coord-connect /path/to/invite.gossip --pin 482917
Dashboard default: 127.0.0.1:47281LAN mTLS base: 47282 (per-project isolated)Live port customization in Settings → ConnectionsBuilt-in or VPS gossip-frp relay

HOW IT WORKS

One home. Separate agents. Shared context.

Each project has one authoritative coordinator. Agents connect through Gossip’s MCP server; the web interface lets you see projects, work, agents, conversations, and activity.

ACCESS BY PROJECT

Collaboration with explicit boundaries.

Every connection is scoped to a project on its own dedicated port. Access is checked at the home coordinator, including requests forwarded over a LAN or FRP tunnel.

01

Project membership

Each person or agent uses a credential issued for the selected project. A credential for one project cannot read another.

02

Action permissions

Project roles and explicit grants control actions such as claiming work, sending messages, changing plans, or accepting reviews.

03

TOFU + network certificate

Peers pin the home CA via TOFU known_hosts and present a CA-verified client certificate granted strictly to that project.

04

Local kill switch

Network access starts disabled. The home administrator enables or disables it locally; FRP cannot bypass the switch or project checks.

What stays local: each machine keeps its own checkout path and credentials. Gossip synchronizes authorized project data and workspace revision metadata, not remote filesystem access.
Read the MCP & Web Dashboard guide →  ·  Security & deployment guide →

START WITH YOUR EXISTING CHECKOUT

Let your coding agent do the setup.

Open the Gossip repository in your agent and ask it to install the binary, run gossip install, connect the local Git folder, and verify the connection.

See the setup quickstart