Troubleshooting

The problems people actually hit, with the fix for each. If yours is not here, the issue tracker is read daily.

Install and first run

• The download stops just short of finishing and never completes. Your browser is holding the file, not losing it: it decides whether to trust a download partly by how many people have taken it before, and every DevThrottle release is a brand-new file. Click the download icon near the top right of your browser - it will be showing a small warning badge. The short panel that opens says the installer is not commonly downloaded, but there is no Keep button in it: click Downloads at the top of that panel to open your full downloads list. There the file offers Keep and Delete as plain buttons - click Keep, and since the file has already downloaded in full it finishes at once. The publisher shown is Center Consulting Inc. On a machine managed by an employer, policy can remove the Keep option altogether - there is no way round that from our side, so ask whoever manages the machine.
• Windows SmartScreen shows a prompt on the installer. The installer is code-signed; SmartScreen reputation for a fresh release build can lag a few days behind the signature. Check the publisher on the prompt, then More info - Run anyway. A hard block (no run option) is not expected - report it.
• An agent will not start: command not found. The first-run wizard offers to install Claude Code for you; for other agents, install the agent's CLI yourself, confirm it runs in a plain terminal, then start the session again.

The Director and sessions

• A session shows Working but nothing is happening. Open the card - the terminal is always the ground truth. If the agent is genuinely stuck, Interrupt it and re-prompt; status detection is tuned per agent but the terminal never lies.
• Agents died when the machine rebooted. Sessions run on the machine; a reboot ends them. What you get back is the Director, the history, and recovery behavior - re-start the sessions from their cards.

Phone and Cockpit

• The phone cannot reach the Gateway. Reachability is the usual cause: the phone must be able to reach the Gateway machine (same Wi-Fi, or your VPN / overlay network from outside). Confirm the Cockpit opens from a browser on the same network first, then re-try the phone. See pairing.
• A device was revoked by mistake. Revocation is not reversible in place - re-approve the device through the normal activation flow and it returns as a fresh row in Devices.

Voice

• Dictation gets technical words wrong. That is what the custom dictionary is for - add the term once and every device picks it up.
• Voice stopped working. Dictation, spoken replies, and the wingman come with Pro - check your subscription state on your account dashboard and the Director's status rail for connection health.
• Your own API calls return 402. The prepaid credit balance for direct catalog-model calls ran out; the request was not run. Dictation, spoken replies, and the wingman are unaffected - they are included in Pro and never draw on credits.