Product·Pairing

Sign in once.
Every device joins.

Email sign-in is pairing. Mac, iPhone, web, Windows, Linux—devices on the same Continuum account auto-join the mesh. Traffic is end-to-end encrypted. Advanced users still get MagicDNS and QR. Push arrives for turn complete and plan attention. Know which machines are controllers vs hosts—and revoke anything you don’t trust.

Download for Mac Read the docs
SettingsCodeUsage
devices
account meshyou@studio.dev
MacBook Prohost · controller
iPhonecontroller
web · chromecontroller
hetzner-arm64host
4 devices · one identitye2e · live
01 · Account mesh

Sign-in is the pairing ceremony.

You don’t juggle a separate “pair token” for every new laptop. Sign in with email on a device and it joins the same account mesh—sessions, devices, and push targets follow the identity.

Open a session on the Mac, pick it up on the phone, approve from the web. Same pool described on sessions.

one identity auto-join all controllers
Welcome
Continuum
magic link · oauthdevice enrolled on success
Settings
transport
transportE2E relay · XChaCha20-Poly1305
optionalTailscale · MagicDNS
advancedQR · clawdmeter:// URL
relay routes ciphertext · host decrypts
02 · Encrypted path

E2E by default. Tailnet when you want it.

Controllers reach hosts over an end-to-end encrypted relay. The relay never holds plaintext prompts or diffs. Prefer your own network? Use MagicDNS / Tailscale so traffic never leaves the tailnet.

Legacy and advanced flows still support QR pairing and explicit URLs for air-gapped or special setups. Deep security notes on security.

03 · Push

Turn complete. Plan needs you.

When a turn finishes or a plan needs attention, push finds the controllers on your account—not only the machine that started the run. Tap through into the live session.

Quiet hours and chimes on mobile stay under your control. The mesh decides who can receive; you decide when it’s noisy. Pair with widgets & chimes.

9:41𝗅𝗍𝖾 ▮▮▮
Continuum
São Paulo · plan ready
4 steps · Approve & run
Continuum
Lisbon · turn complete
$0.22 · 28k tok
Devices
roles
controllerssteer · approve · view
iPhone · web · Windows app
hostsrun agents · hold code
Mac daemon · continuum-agent
enroll hosts in Deviceslearn more
04 · Controllers vs hosts

Not every device runs the agent.

Controllers start, steer, approve, and review. Hosts execute—Mac Continuum daemon or continuum-agent on Linux/Windows hardware you enroll. A phone is almost always a controller; a Hetzner box is almost always a host.

Some Macs are both. That’s fine. The mesh shows the role so you never wonder why a tablet “can’t compile.”

05 · Revoke

Lose a laptop. Cut it off.

Every joined device is listed. Revoke drops it from the mesh—no more relay access, no more push, no more session control from that client. Rotate host pairing material when a machine leaves the company bag.

Revocation is part of the product, not a support ticket. Treat devices like sessions: easy to add, easy to end.

Devices
revoke
MacBook Pro · 2024this device
iPhone 16revoke
old-ipad · travelrevoke
chrome · cafe laptoprevoke
06 · Questions

The honest fine print.

Short answers here, long answers in the docs.

Account sign-in covers the common case. QR and MagicDNS remain for advanced, local-only, or recovery flows—especially when you’re wiring a host without a browser sign-in.

Yes. Controllers on the same account see the same session pool. Live turn state is shared; it’s one conversation on many screens.

Controllers can still sign in, but nothing runs until a host is available again—your Mac daemon or an enrolled continuum-agent box. Sessions don’t magically move to the cloud.

No. You can poll from open apps. Push is how plan attention and turn complete find you when Continuum is in the background.

07 · Begin

One account.
Your whole desk in your pocket.

Sign in on Mac, then open Continuum on your phone with the same email.

Download for Mac Read the docs

see also · sessions · devices · mobile · security