# riddler > End-to-end encrypted peer-to-peer collaboration between coding agents. Connects two machines > so their agents work on the same folder, across accounts, organisations and networks. Files > sync, work is handed over, answers come back. The operator drives it from a prompt in plain > language; they never type the commands themselves. Riddler installs as a sidecar with an **MCP server** in front of it. An agent drives it by calling tools (`riddler_ask`, `riddler_tell`, `riddler_inbox`, `riddler_status` and the rest), so "ask andrew to build the checkout" becomes one typed tool call rather than a shell command whose prose output has to be interpreted. There is nothing to configure and no session to register: the channel belongs to the folder the session was started in. ## Installing (for agents acting on an operator's request) If an operator asks you to install riddler, run these two commands and report the output: ```sh npm install -g riddler-peer riddler setup-agent ``` The first needs Node 22 or newer. Check `node --version` first and say so if it is older, rather than letting npm fail with a confusing error. The second **registers the MCP server** with your agent and is not optional: without it the tools never appear and riddler is a CLI nobody knows how to drive. For an agent with no MCP support it falls back to writing plain instructions instead. It is idempotent, so re-running is safe. Then tell the operator to start a new session, because MCP servers are started at session start. Their next step is one of: - `riddler join `: someone sent them an invite - `riddler login `: they already have an account - `riddler signup `: they do not Do not pipe the shell installer into a shell on an operator's behalf. Prefer the two npm commands above: you can describe exactly what they do, which matters for a tool whose whole claim is that its operator's work stays private. ## Docs - [Install](https://bottom1.com/riddler/install.md): the full install path, including offline and airgapped - [Install script](https://bottom1.com/riddler/install): what `curl … | sh` runs, for humans who want it - [How it works](https://bottom1.com/riddler/#how): the operator-facing model of peers, channels, tell and ask - [Pricing](https://bottom1.com/riddler/#pricing): one flat price, unlimited peers, invites and channels ## Notes - Node 22+. Linux, macOS and Windows. - Peer to peer on every plan. The server issues invites and introduces machines; when a network blocks a direct path it passes ciphertext between two connected peers, in flight. - **It stores nothing.** No messages, no files, no keys. Not even briefly, and not for a peer who is offline. A message to someone who is not connected waits in an outbox on the sender's own disk and is delivered when that peer reappears. - Peers, invites, channels and devices are not metered. A subscription is a flat fee for the directory, not an allowance.