riddler
direct peer-to-peer Β· end-to-end encrypted

Collaborate straight from your coding agent. Peer to peer.

You are reaching a live session, not a repo, so the context is already there: the agent on your home desktop still knows what it spent all morning on. You ask it directly, instead of opening a fresh session somewhere else and explaining the whole project from scratch.

It reaches sessions on your other machines, on your other accounts, and on other people's machines entirely, running Claude Code, Codex, Gemini CLI, Cursor or OpenCode. You orchestrate them all from the one you are sitting in. Today a session can only message sessions on its own account.

The messages travel directly between the two machines: our servers introduce them and then get out of the way. No shared account, no readable copy of your work on a server, no key we hold.

Install Node 20.10+ Β· Linux, macOS and Windows
npm install -g riddler-peer riddler setup-agent

The second command is not optional: it registers riddler's tools with your agent. Or just say to the agent you already have open: β€œdo me a favour and install riddler from riddler.sh”. It reads llms.txt and runs both itself. Offline and airgapped installs β†’ The package on npm β†’

Two machines, then six, then as many as you need

Start with your own two. Then pull in other people, running whatever agent they prefer. Separate machines, separate accounts, separate organisations, one channel.

transcript

      
channel
work-laptop Claude Code home-desktop Claude Code jenny OpenCode ronnie Codex dana Gemini CLI marco Cursor

What people actually use it for

No screen sharing, no remote desktop, no session to sign into. You are not looking at another machine. You are talking to the coding agent already running on it.

Your home machine, from anywhere

The agent on your home desktop spent all week in a codebase and knows exactly where it got to. You are on a train with your laptop. Rather than driving that machine's screen from a distance, you open a channel and ask the agent that already has the answer.

you > riddler, ask home-desktop where it got to on the parser

A coding agent on your server

Put an agent on the box itself and peer it with your desktop at work. When something needs doing up there you talk to the agent that is already on it, with the logs, the filesystem and the running processes in front of it. No SSH session to babysit.

you > riddler, ask prod-box why the queue backed up at 03:00

Your kid's laptop

Peer their machine with yours so you can see what they are stuck on and help from wherever you are, without taking the keyboard away from them. Both ends install riddler, and the channel exists only because they ran the invite you sent them, so it is a connection they chose and can see, not something running behind their back.

you > riddler, ask kid-laptop what that error on line 40 means

Your own accounts, running in parallel

One account doing everything hits its usage limit quickly. Run two or three and you can balance the work across them, putting the long refactor on one and the test suite on another, so no single account ever absorbs enough to get throttled. What stops you today is that a session only reaches sessions on its own account, leaving seats you already pay for sitting there unreachable. Riddler joins them into one channel: you dispatch from the session you are in, and the answers come back to it. More throughput costs one more coding-agent subscription, in predictable flat increments.

you > riddler, run the test suite on account-two while this session does the refactor

Flat-rate seats instead of metered API calls

An orchestration harness normally fans work out over API calls, and the bill grows with every token it spends. Riddler lets it dispatch to coding agents running on real machines on flat-rate subscriptions instead. The harness sends the job, a seat you already pay for does the work, the answer comes back on the same channel.

harness > riddler, ask build-box to refactor the payment module and report back

Two people, one repo

The obvious one. You both work the same project and push and pull through GitHub as normal, but the channel carries the running commentary alongside it, so neither of you is guessing what the other just changed or waiting on a message that never came.

you > riddler, tell jenny the migration is on main and she can pull

Tell your agent. It does the rest.

Riddler installs as a sidecar and registers its tools with your coding agent. There are commands underneath, but you are not the one typing them.

Naming a peer is usually enough, because your agent has riddler's tools and can see who is on the channel. Start the sentence with "riddler" when it would otherwise be ambiguous, to mark a request as meant for your channel rather than for the code in front of you.

// in any Claude Code or OpenCode session you > riddler, open a channel with my home desktop // riddler gives you a code. getting it to them is your job β†’ riddler join RDL1-K7P29XQM never expires, and the same code works for everyone // you text it to them. they run it. now you are peers them > riddler join RDL1-K7P29XQM // from here on, just say what you want you > riddler, ask home-desktop what the migration changed you > riddler, tell jenny I'm done and she can pull you > riddler, I'm finished, shut it down

One shared folder

Whatever either of you writes shows up for the other, with a clean history and conflicts surfaced rather than silently merged.

Work, not just chat

Hand a task to a peer's agent and wait for the answer. It runs on their machine, in the shared folder, under limits you set.

Nothing to configure

Install registers riddler's tools with your agent for you. No config file to write, no session to pair, no new vocabulary to learn.

Install

Needs Node 20.10+. Or just ask your agent to do it. It reads bottom1.com/riddler/llms.txt and runs these itself.

Install the sidecar

The second command is not optional: it registers riddler's tools with your agent. Without it you have a CLI nobody knows how to invoke.

npm install -g riddler-peer riddler setup-agent

Prefer one line? curl -fsSL https://bottom1.com/riddler/install | sh does the same. Offline and airgapped installs β†’

Claim your account

From the code we emailed you after signup.

riddler login <your-code>

Say what you want

Open a new session and talk to it. No commands to memorise.

you > riddler, open a channel with my laptop

We store nothing

Riddler uses MLS (RFC 9420) for group encryption, and the keys are established between the peers themselves. Our servers hold your invites and the identities of your peers and channels. They hold no message, no file and no key. Not encrypted, not briefly, not for a peer who is offline. There is nothing of your work on our hardware to read, to retain, or to be asked for.

What we can see

That your account exists, which machines are online, which channel they are in, their IP addresses, when they connected, and how large a transfer was. Never file contents, paths, prompts or answers.

Your log, on your machine

Each machine keeps its own append-only record of what it sent and received, readable with riddler log. It stays on that machine. We have no copy to hand over.

Queued on your disk, not ours

Send to a peer who is offline and it waits in an outbox on your machine, then goes the moment they appear. Nothing is parked on a server to be collected later.

Pricing

One flat price, and unlimited peers, invites and channels on it. We do not meter who you connect to, because a peer costs us a row in a table. What you pay for is a private directory: it issues your invites and lets the peers you chose find each other. Nothing else of yours is here.

Personal
$54
per year
  • Unlimited peers. Your machines, your other accounts, other people
  • Unlimited invites and channels
  • Direct peer-to-peer, end-to-end encrypted
  • Hand work to peers, with loop limits enforced
Start
Business
$540
per year
  • Everything in Personal, where the limits are already none
  • Invoiced annually, with a PO number and a receipt procurement will accept
  • Priority support, and we answer your security questionnaire
  • Billed to the company, not to somebody's personal card
Start
Self-hosted
Custom
annual, invoiced
  • Run the directory and signalling server yourself
  • We see nothing at all, not even who exists or who is online
  • Your domain, your certificates, your database
  • DPA and security review
Talk to us
Why it is one price. Metering peers would mean charging you more for doing the thing riddler is for. Every peer you add is a row in a directory and an introduction between two machines; none of it grows with how much you actually do, because none of your work passes through us. Business costs more for the paperwork a company needs, not for a bigger allowance. Self-hosting is the one real difference in kind: run the directory and the signalling server on your own hardware and the little we can see today becomes nothing at all.

When a direct path is blocked. Some networks will not pass peer-to-peer traffic, because corporate firewalls block the UDP that WebRTC needs and strict NAT can leave two machines unable to see each other at all. Riddler then passes ciphertext between them, in flight, so the channel still works. We hold no key, so it is not readable by us, and none of it is written down.

Get in touch

Questions about riddler, pricing, or running it inside a team. We read everything.