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, and your code never leaves your computer. We host nothing of yours, so it costs us nothing when you use it. 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/DevThrottle API/Errors and limits

API

Errors and limits

2 min read

Errors come back OpenAI-shaped, so existing SDK error handling works unchanged:

Error body

{
  "error": {
    "message": "human-readable explanation",
    "type": "invalid_request_error | api_error | ...",
    "code": "machine_readable_code"
  }
}

Status codes

400 - invalid request, including an unknown model. DevThrottle never silently substitutes a different model; fix the id against GET /models.
401 - missing, malformed, or revoked API key. See authentication.
402 - insufficient credits. The request was not run; top up on Billing and retry.
5xx - something failed on the serving side. Failed requests are not debited: you pay for results you received, not attempts.

Rate limits

Per-account rate limits are being finalized and are not yet published. Today, write clients the way you would for any metered API: handle non-200s, back off on 5xx, and do not hot-loop retries. When limits are published they will appear here and on the rate card page.

Note

The one error worth designing for up front is 402: credits are prepaid, so a long-running unattended integration should either watch its balance via Usage or enable automatic top-up with a monthly limit.