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. What it is weighing is the publisher, not the file: DevThrottle is signed by a young identity that has not yet shipped enough copies for the browser to know it, and that reputation is built by volume over time. 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. Same cause as above, and nothing is misconfigured: the installer is code-signed, and SmartScreen is weighing how well it knows the publisher rather than how new the file is. Check the publisher on the prompt reads Center Consulting Inc., then More info - Run anyway. It clears as the identity builds volume, so it is not a wait you can shorten from your side. 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. Read the session first - it says why. The badge on the session is decided for you and each one means something different:
  • Nothing to read aloud - the session is waiting on a prompt or a menu, not a text answer, so there is nothing to narrate. Not a fault.
  • Voice service down - the far end is not responding. It retries by itself; there is nothing for you to press.
  • Voice needs credit, Monthly limit reached, Finish setup - about your account or this machine, and each carries the button that fixes it.
  • Voice did not arrive, followed by how long it waited - after three minutes with no audio the session stops promising and says so. The Gateway keeps trying; read the turn instead.
  • Update DevThrottle - that session's computer is on a version that cannot send its conversation. See below.
• Voice is silent and the session shows no reason at all. Check your subscription state on your account dashboard and the Director's status rail for connection health.
• Your own API calls return 402. The refusal carries a code, and the code says which of several things happened - so read it before topping anything up. insufficient_credits means the prepaid balance for direct catalog-model calls is empty. monthly_limit_reached means you hit your own Monthly spending limit, which is a switch you set on the billing page and raise there - your credits are untouched. A call to your hosted Gateway can also answer hosted_subscription_required, which means the account has no live plan or trial; that response carries the address to act on. Dictation, spoken replies and the wingman are unaffected by all three - they are included in Pro and never draw on credits. API errors.

Chat and the conversation

• The chat screen is empty. It tells you which of several reasons it is, and they are not the same news: this session is not known here (the id may be wrong, or it belongs to another account); this agent keeps no readable conversation, so nothing will ever appear and that is not a fault; that computer has not checked in recently; that computer cannot send it; nothing has been sent yet, which clears itself within a minute; or the session is here and has simply not spoken yet. Read the sentence on the screen - it is the answer, not a placeholder.
• "This session's computer is running an older DevThrottle that does not send conversations." This is the one most people meet right now. Sending conversations arrived in v2.0.5, and it has to be installed on the machine the session runs on - not on the machine you are reading from. Update DevThrottle there and the chat fills in on its next check-in. The same fact appears on the voice screen as Update DevThrottle.
• A Pi session is showing an earlier session's conversation. Fixed in v2.0.6 - but a Pi session that was already open when the update installed keeps the old behaviour for the rest of its life. Close that session and open a new one. Changelog.