How can we help?

Email [email protected] for setup, billing, or privacy help. Earshot is provided by Millennial Apps, LLC.

Set up your Mac

You need a Mac with Node.js 22.14 or later and at least one supported coding CLI: Claude Code, Codex, Cursor, or Devin. Your coding provider account and usage charges are separate from Earshot voice credits.

1. Follow the installer instructions on the Earshot home page.
2. On that Mac, open http://127.0.0.1:8788 and choose your project folder and coding tools.
3. In Earshot on your iPhone or iPad, allow AI data sharing, then paste its connection code or scan its QR code.

Coding agent access

Live coding agents run with their CLI approval prompts disabled. They can run commands, change or delete files, and use credentials available to your Mac account without asking for each action.

Selecting a project or Git worktree does not confine an agent to that folder. macOS permissions still apply. Connect only computers you control, keep backups, and review the work.

This applies to agents launched by Earshot. Your other CLI sessions keep their own settings. Approval bypass is also called YOLO mode. Claude Code skips permission prompts, Codex bypasses approvals and its CLI sandbox, Cursor uses YOLO and workspace trust, and Devin uses Bypass mode for these sessions.

Earshot does not relay CLI approval requests to your phone. Stop a task from the app to cancel its running processes; completed file changes or remote actions are not undone. Worktree mode separates Git changes for review, while Working directory mode edits the selected checkout in place. Neither mode is a security sandbox.

Start and stop listening

Opening Earshot normally leaves voice off. Tap Start voice to begin. To start automatically from the iPhone Action Button, choose Shortcut in iPhone Settings → Action Button and select Start Earshot. Consent, pairing, and microphone permission are required first. Tap Stop voice to end the session. Voice can continue while the app is in the background.

Mac offline

Keep the paired Mac awake and online. Open its local setup page to confirm the coordinator is running and the relay address is correct. Reopen Earshot to reconnect. Reinstalling or updating keeps the saved pairing. After deliberate relay-data deletion, click Show connection code, then Create a new connection in Mac setup. Add that new code on the phone. A temporary outage does not require a new pairing.

Task notifications

Allow notifications when Earshot asks. You can change the setting later in iOS Settings → Notifications → Earshot. Focus modes and notification settings can delay or silence alerts. When voice is off, notifications tell you when a task completes, blocks, or fails; open the app to see its current state.

Voice credits and your own key

Voice uses hosted prepaid credits or an OpenAI API key you configure in Mac setup. Setup shows your balance and recent usage. Buy voice packs with Apple in-app purchases in supported storefronts worldwide. Apple displays your local currency price; packs add $10, $25, $50, or $110 to a USD-denominated voice balance. The largest pack includes $10 bonus credits, or 10% extra, and is priced near US $100 (see Apple’s localized price before buying). Credits do not expire and belong to this computer pairing. Each saved computer has its own balance. Request Apple purchase refunds through Apple. The Mac setup page provides billing and key management. If a payment is missing, email the receipt reference and approximate purchase time. Do not send payment card details, API keys, or your pairing QR code.

Low or exhausted voice credits

Tap your balance or Add credits in Earshot to open Apple purchase options. The app warns when available credits fall to $2 and explains when a temporary voice reserve is needed. Typed tasks remain available. After purchase confirmation, your balance refreshes and Start voice becomes available. Purchases are one-time; there is no automatic refill. If Apple is still approving a payment, wait for confirmation rather than buying it again. Use Sync purchases to retry a paid purchase whose credits have not arrived.

Some credits may be temporarily reserved for a voice session. Confirmed usage consumes that reserve and unused funds return after the session closes. Contact support if a reservation remains. Hosted voice usage is billed at 2.5× OpenAI token rates. Existing balances were increased by 25% when the rate changed from 2×, preserving their voice buying power. Your own-key sessions are billed directly by OpenAI.

Saved computers and recovery

Open the computer menu to add a connection code, switch computers, or swipe to delete a saved computer. Model and project choices are remembered for each computer. Save connection codes in a password manager; they grant computer and balance access. If you lose a code, support can help after verifying ownership. A receipt reference alone is not proof. One phone receives notifications per pairing; registering another replaces it. Notification taps switch to the originating saved computer.

Update or uninstall

Run the installer again to update, after stopping active tasks. The installer stages the replacement and preserves the old installation if setup fails. To stop the listener, run launchctl bootout gui/$(id -u)/com.realtimevoice.coordinator on the Mac. Remove ~/Library/LaunchAgents/com.realtimevoice.coordinator.plist to prevent it starting at login. Keep your connection code and app data until you have resolved unused credits; ask support before deleting data.

Delete data or disconnect

Forgetting a saved computer removes it from this iPhone or iPad and queues notification removal if offline. Its balance and Mac files remain. Delete pairing and relay data in Setup removes the relay pairing, voice usage records, device token, stored OpenAI key, and credit balance. Contact us about unused credits first. Files, worktrees, pull requests, and task history on your Mac are separate and remain on your Mac or Git host. See the privacy policy for details.

When you contact us

Include the Earshot version, iOS version, Mac version, and the steps that caused the problem. Redact private project content from screenshots. Never send pairing secrets or provider API keys.