Companion surfaces
Use Mezair's phone, watch, menu bar or Raycast controls to check on work while the desktop app is in the background. Depending on the companion, you can approve or decline a step, reply, interrupt, launch a workflow or reopen the work on your Mac.
They are not a replacement for the desktop workspace. Full diffs, terminal work, browser checks, and handover review still belong on the desktop.
Supported surfaces
| Surface | Use it for |
|---|---|
| Mobile companion | Pair by QR code or enroll against your account, switch hosts and workspaces, dial enrolled devices directly, inspect the work queue and workspace health, resolve approvals, browse threads and work items, send chat input, and launch quick actions. |
| Raycast extension | Check workspace state, resolve approvals, send active-session input, launch predefined workflows, and focus the desktop app. Has an account-connected mode for reaching enrolled devices. |
| macOS menu bar | See pending approvals, focus Mezair, launch companion workflows, and stop active sessions. |
| Home Screen widgets | Pin live workflow health, approval counts, running sessions, repo counts, and one-tap command launches. |
| Apple Watch | Resolve small approval decisions, send quick replies, continue, stop, summarize, or interrupt. |
| CarPlay | Shows the Mezair Drive queue and offers a small set of safe actions such as pausing work, continuing low-risk checks, preparing a handover, or capturing a note. |
| Siri | Captures a workspace note or invokes a supported short companion action through the mobile app. |
Pairing and hosts
Desktop starts a local companion server only after you enable it. A pairing ticket is short-lived and contains the server address and one-time ticket in a QR code. The companion can store more than one host and prefers reachable LAN or Tailscale addresses over loopback.
Settings lists paired devices with their client type and last-seen state. Revoke a device when it is lost, replaced, or no longer needs access. Raycast uses a separately issued companion token.
Account-connected mode
Local pairing is not the only route in. The mobile companion can enroll against your Sync & Mesh account and then dial enrolled devices directly, useful when the desktop is reachable through the backend but not on the same network. The Raycast extension has an account-connected mode for the same kind of reach.
In account mode, the native mobile app uses LAN-first Mesh routes, in beta through 30 November 2026. It tries the host's LAN address first and moves a live session to a better route only after the replacement has authenticated and caught up, without resending commands. The QR-paired companion connection described above keeps its own address preference.
Enrollment produces the same device-scoped, revocable credential as desktop enrollment; enrolled companions appear in the account device roster alongside desktops. The enrollment mechanics are in Devices; the account side is configured in Sync and Mesh settings.
Approval limits
Companion approval requests show the command or file change, repository, workspace, reason, and risk metadata that Desktop supplied. Some requests require desktop review and should not offer a remote approval shortcut.
Destructive or unclear actions belong on Desktop, where the full thread, diff, and terminal context are visible. A small screen is good at answering "continue this known check." It is bad at reviewing a shell command that can delete half a monorepo.
Access and approvals
Companion access is local, authenticated, and revocable. Treat tokens and pairing tickets as workflow credentials, not decoration. Network reachability still depends on the selected advertised address and the host machine's firewall.
Use companions for short commands. Open Desktop when you need to inspect a repository, read terminal output or review the consequences of an action before approving it.