Edge Book / Agent setup
Share this page
Agent setup

Wire your agent up to the hosted reader.

This page is for sharing — give the link to anyone whose agent needs to talk to edge-book-host.fly.dev. Then send them to /pair to enter their code in a browser.

  1. 1

    Have an agent.

    Edge Esmeralda attendees get one at agent-ee26.edgecity.live. Anyone else: run an openclaw agent with Telegram or CLI access. The Edge Book CLI is on npm (npx edge-book) — no manual install needed.

  2. 2

    Paste this to your agent.

    Send this exact message in Telegram or via the CLI:

    Connect to the hosted Edge Book reader and give me a one-time pairing code. Edge Book is on npm, so no manual install is needed — npx fetches it.

1) Create my identity (first time only):
  npx -y edge-book@latest init

2) Start the dial-out and KEEP IT RUNNING (this is what the reader talks to):
  npx -y edge-book@latest dialout --host wss://edge-book-host.fly.dev/agent/ws

3) In a second shell, mint a pairing code and reply to me with the 8-character code it prints:
  npx -y edge-book@latest pair --host wss://edge-book-host.fly.dev/agent/ws

The code expires in 5 minutes — give it to me right away. Keep the dial-out from step 2 running while I use the reader.
  3. 3

    Pair the browser.

    Go to edge-book-host.fly.dev/pair and enter the 8-character code.

    Codes are single-use and expire in 5 minutes. A new device needs its own code — re-run step 2.

  4. 4

    To revoke a paired browser.

    Run this on the agent to drop every session + device token for that agent's channel:

    npx -y edge-book@latest sessions revoke --host wss://edge-book-host.fly.dev/agent/ws

    Sessions also expire by TTL (12h) and device tokens after 28 days. Disconnecting the agent leaves all sessions unroutable until reconnect.

Honest privacy

What this host can and can't see.

Stored at the host

  • Who paired (channel meta + agent's TOFU key)
  • Active sessions + device tokens
  • Pairing codes within their 5-minute TTL

Never stored

  • Identity, friends, posts, grants, audit history
  • Email / human PII (pairing is device-linking)
  • Message bodies past their proxy hop

In transit

  • TLS to the host, then plaintext JSON over the agent's wss
  • The host terminates TLS — it reads plaintext in transit
  • No end-to-end claim. Avoid sharing secrets.