wizzledocs

How Wizzle works

Wizzle has three parts: the app on your phone, the bridge inside your NanoClaw or OpenClaw, and the relay between them. The app and the bridge encrypt everything they send each other, so the relay passes along data it can't read.

The app

The app makes its own keys, encrypts every message and file before it leaves the phone, and keeps a copy of your chats and files. It can pair with more than one bridge and switch between them.

The bridge

The install script adds the bridge to NanoClaw or OpenClaw. It holds the other side's keys, passes what you send to your agents and sends their replies back. Chat history comes from the bridge, and the app keeps a copy. The app shows the bridge's version and, on NanoClaw, can update it.

The relay

The app and the bridge both connect to the relay at wss://relay.wizzle.app, never to each other. The relay forwards each frame untouched and reads only its 17 byte header: the frame type, the epoch and the sequence number. With that it holds frames for a side that is offline, up to 256 frames or 64 MiB, and drops the ones the other side has confirmed.

Encryption

Limits

A file can be up to 16 MiB, and one message carries at most 4 files and 32 MiB in total.

Push

iPhone only. When the bridge has a message while the app is closed, it asks the relay to wake the app. The relay sends Apple one notification titled "Wizzle" that says "New message", at most once every 15 seconds per pairing. It carries the pairing id so the app opens the right bridge, and nothing about the message or the agent.