Is DevThrottle an AI agent?

No. DevThrottle does not write code and is not an agent - it is the control room for the agents you already run. It lines up Claude Code, Codex, and your other tools on one board so you can see what each is doing at a glance and answer them by voice. You bring the agents and their subscriptions, and running them through DevThrottle costs nothing.

The app is free forever. The only thing for sale is prepaid credits, which pay for hosted AI features like transcription at a published rate card. The free version is not a trial and never expires.

Which coding agents does it work with?

It works with the AI coding agents you already use - Claude Code, Codex, Aider, Gemini, and others - across different tools at the same time. You keep your existing agent and subscription; DevThrottle runs and watches them all on one board.

Docs/Reference/Telemetry

Reference

What DevThrottle reports home

3 min read

This page is the honest inventory of what DevThrottle itself sends home, what it keeps on your machine, and the one switch that controls it. It is deliberately specific - no hand-waving in either direction.

Two events that always flow

Having an account means two small events reach devthrottle.com, always by way of your own Gateway (Directors never call the cloud directly):

Sign-in - when you log in: the source (the app), the app version, and an install id.
Director startup - when a Director launches: its id, the machine name, and the app version.

These are the heartbeat that tells us how many people actually use DevThrottle - the whole reason accounts exist. They carry nothing about your work, and they cannot be switched off while signed in. Your sign-in token itself is never sent along with them and never logged.

The optional usage telemetry

Richer usage telemetry is a stream of anonymous events, and each event is exactly two things: an event name and a timestamp. Which feature was used, when. Never what you used it on.

It is on by default, disclosed at the Gateway's first launch (the consent screen with the checkbox "Share anonymous usage information to help improve DevThrottle"), and controlled afterwards from the Cockpit's Usage Telemetry page - one fleet-wide switch on your Gateway that applies to every Director immediately, no restart.

Screenshot coming soonThe Cockpit Usage Telemetry page with the fleet-wide on/off control and the explanation of what the events contain

The Cockpit Usage Telemetry page with the fleet-wide on/off control and the explanation of what the events contain

What stays on your machine

Car Mode timings - the performance numbers behind Car Mode (how long a turn took to transcribe, think, speak) are stored in a file on your Gateway machine and viewed locally. They record character counts, never the text of what was said or heard, and they are not reported to the cloud.
Diagnostic logs, transcripts, and session data live where your Gateway lives.

What DevThrottle telemetry never contains

No code, no file contents, no repository names.
No prompts and no agent conversations.
No credentials, keys, or tokens.
No text of anything you said - voice surfaces log counts and timings only.

Note

Telemetry is about what DevThrottle sends us. Your coding agents and any hosted AI you choose to use have their own data flows - your agent sends code to its AI provider to do its job, and hosted transcription uploads audio to be transcribed. Those are covered where those features are documented, for example hosted vs bring-your-own key.