No voice input or output
Confirm microphone permission, visible mute state, selected speaker output, and the current voice route. End and restart the live session after changing audio permissions.
Support
Get the route back to ready.
Start with the in-app Setup Guide and Ready Check. If the visible state still does not explain the problem, send the route, device, and exact status to support.
First check
The Setup Guide stays current.
Completed items remain complete. Optional or unresolved items stay visible without blocking a device-only GPT Realtime session. Run Ready Check again after changing authentication, bridge, agent, or permission settings.
- Confirm GPT Realtime and microphone readiness.
- Refresh Companion, agent, and Watch state.
- Open the exact setting for an unresolved permission.
Troubleshooting
Start with what you can see.
Companion is unreachable
Open Companion Diagnostics. Confirm the local bridge, Tailscale Serve mapping, and current phone URL. Re-pair after any bridge port or setup payload change.
Codex, OpenClaw, or Hermes fails
Check the specific route state. Verify Codex app-server, the OpenClaw folder containing openclaw.json, or hermes --help in the same Mac user environment.
Watch cannot reach a Mac route
Use iPhone relay when nearby. Away from iPhone, computer routes require an intentionally configured HTTPS bridge; direct Watch GPT Realtime has separate readiness.
Setup paths
Prepare only what you plan to use.
Device-only voice
Install the iPhone app, connect supported ChatGPT or OpenAI access, allow the microphone, and start GPT Realtime. A Mac is not required.
Computer routes
Install the latest Companion, prepare Tailscale, start the private bridge, pair by QR, and run the route-specific ready check.
Apple Watch
Install or open the Watch app, sync current settings from iPhone, and check whether the intended route uses direct connectivity, iPhone relay, or your configured bridge.
Files and actions
Enable only the iPhone or Mac permissions the action needs. Select files explicitly, and review returned artifacts from the Work or Companion file surface.
Common questions
Route-specific answers.
These checks reflect the current Companion and onboarding flow.
Why is GPT Realtime not starting?
Confirm microphone access, then check that ChatGPT Plan OAuth or an explicit OpenAI API key is available for the route you selected. If Companion-minted authentication changed, pair the iPhone again.
Why can iPhone not reach Companion?
Confirm Companion is running, Tailscale is signed in on both devices, both are on the same tailnet, and the current Tailscale Serve mapping passes Companion Diagnostics. If the bridge port changed, scan the current QR again.
Why is an OpenClaw agent missing?
In Companion, point OpenClaw Install Path at the folder that directly contains openclaw.json, usually ~/.openclaw. Then run the route check again.
Why does Hermes fail even though it is installed?
Run hermes --help in Terminal. Companion uses the Mac command-line environment. If Hermes works only through custom shell setup, configure HERMES_BIN for the bridge environment.
Why can Apple Watch talk to GPT but not reach my Mac?
Direct GPT Realtime can use the Watch network connection. Mac routes require iPhone relay when the phone is nearby or a deliberately configured HTTPS route when it is not. Watch does not join your private Tailscale network by itself.
What should I include in a support email?
Include the device, app or Companion version, selected route, the visible status message, and what happened immediately before the issue. Redact API keys, QR payloads, tokens, private hostnames, and bridge URLs.
Contact support
Still not ready?
Email support@voiceclawrealtime.com. Include versions, device, selected route, visible status, and reproduction steps. Never include secrets or pairing payloads.
Downloads and policies
Official destinations.
iPhone and Watch
Mac Companion
Privacy