Download the current DMG
Use the latest release above, open the DMG, and move VoiceClaw Realtime Companion to Applications.
VoiceClaw Realtime Companion
Your private bridge to work on your Mac.
Pair iPhone by QR, connect Codex, OpenClaw, and Hermes, then keep route readiness, running tasks, and returned files in view.
Latest notarized releaseLatest release
What it connects
Your phone starts the work. Your Mac carries it.
Codex
Send durable work through Codex app-server without modifying your Codex installation, then follow the task state from VoiceClaw.
OpenClaw
Select an agent, resume recent work, and reach the OpenClaw installation you already run on your own Mac.
Hermes
Route substantive work through the Hermes CLI environment installed on the Mac.
Tasks & Files
See route status and manage explicitly returned files in the bounded Artifact Inbox.
Private pairing
Open Companion. Scan once. Verify the route.
The current QR can carry the Mac bridge address and the setup you choose to include. VoiceClaw checks the live destination after import, while device-only GPT Realtime remains available even if an optional computer route needs attention.
QR preview redacts keysLive bridge verificationRoute-specific readiness
Install and pair
Four deliberate steps.
Current Companion builds target Apple silicon Macs running macOS 13 Ventura or later.
Install and start the bridge
Companion creates its local configuration, user LaunchAgent, and selected Tailscale Serve mapping.
Prepare Mac access
Use the Access screen to review Login Items, Local Network, Microphone, Files and Folders, and any agent folders you intend to use.
Pair and run the ready check
Scan the Pair Phone QR, select a route on iPhone, and confirm that the specific bridge and agent destination report ready.
Readiness without guesswork
Know what works before you talk.
Companion and the iPhone ready check separate core live voice from optional computer routes. A missing Hermes install, a changed QR, or a route-specific permission does not present the whole product as broken.
Open troubleshooting
Local ownership
A bridge you can inspect and revoke.
Private by default
The bridge listens locally on 127.0.0.1 and is forwarded by Tailscale Serve to devices on your tailnet.
User-owned auth
Supported credentials remain in device secure storage or Mac Keychain. You choose what the pairing payload includes.
Explicit files
Task inputs and returned artifacts use separate bounded stores with authenticated metadata and clear removal behavior.
Signed updates
Companion checks GitHub Releases for signed updates and supports the notarized DMG workflow shown above.
Companion FAQ
What the bridge does and does not do.
The Companion repository includes detailed installation, privacy, and route notes.
Read the repository guideDo I need Companion for GPT Realtime?
No. Device-only GPT Realtime can work without a Mac. Companion is for Codex, OpenClaw, Hermes, Mac files, and other computer-backed routes.
What does Install and Start change?
It creates the local bridge configuration, installs a per-user LaunchAgent, starts the bridge, and configures the selected Tailscale Serve mapping. Companion explains each change before it runs.
Does Companion make my Mac public?
Not by default. The local bridge listens on 127.0.0.1 and is published privately through Tailscale Serve. A public HTTPS tunnel is optional, advanced, and only used when you configure it.
Where do returned files go?
Supported route outputs appear in the Companion Artifact Inbox. The inbox is bounded, authenticated, and manually managed; files are not silently evicted.
Setup help
Pairing or route check not passing?
Send the visible state and the route you are trying to use. Do not send API keys, QR payloads, tokens, or private bridge URLs.