Pair the mobile app
Everyone · Set up access
Before you rely on mobile
The mobile client is the least mature part of Buzz, but it is maturing quickly: it ships on its own release train, receives dedicated fixes each cycle, and the v0.5.15–v0.5.18 window alone touched over 200 mobile files. Community invites can be sent from the phone, and voice huddles now work there. It has been demonstrated working end to end, but it is still in active development and not everything is stable. Do not make it the only way you can reach a workspace.
Steps at a glance
1. Decide whether mobile is part of your working setup
The draw of mobile is supervision, not production: checking in on agent work, answering an agent's question, steering something that has gone sideways — from away from the desk. That is a real benefit during a long-running project.
Delegation works even when the desk is off: messages you send from the phone are held by the relay and picked up by your agents when the machine that runs them wakes. The relay is store-and-forward — humans see your message immediately; agents act on it when their substrate returns.
2. Install the mobile app
Install the Buzz app from the app store for your device. Availability differs by platform and has changed over time — check the official download page for what is currently published for iOS and Android.
3. Open the pairing screen on desktop
In the desktop app, open the pairing screen to display a QR code. Where pairing lives can vary between versions — look in Settings if it is not obvious.
4. Scan the code
Scan the QR code from the mobile app. This links the device to your existing identity — you are not creating a second identity, you are giving another device the ability to act as you.
When the phone is the side sending an identity — desktop recovery from a signed-in phone — the phone now asks for device authentication first: Face ID, biometrics, or the device passcode. That authorization covers the active pairing session and a short pairing window only, and expires; if it lapses before the identity payload is sent, the phone asks again. Nothing changed for ordinary app opening, for importing an identity onto the phone, or for community removal.
Because of that, treat the phone as key material: lock screen on, and check whether your build offers a way to unpair or revoke a lost device before you depend on the phone. The same property works in your favour: a paired phone is a recovery device, able to restore access to your identity if the desktop is lost (since v0.5.6) — and since v0.5.15 that recovery path is gated behind the phone's own device authentication rather than behind possession of an unlocked phone alone.
5. Confirm what works and what does not
Check which surfaces are actually usable on mobile in the current build — channels, forum, search and profile are the ones under development. Voice huddles joined the list: a phone can now take part in a huddle (foreground only, no transcript, no recording, no background calling), which means a phone participant can be in an agent huddle but cannot run one, since the transcript is what agents hear. Anything you rely on daily should be tested before you depend on it in front of an external stakeholder.
Verified against Buzz v0.5.20 · Updated 2 Sep 2026