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/Coding agents/Supported agents

Coding agents

Supported coding agents

3 min read

DevThrottle is vendor-neutral: it runs the coding agents you already use, side by side on one board, each in its own session on its own repository. You keep your own subscriptions and keys - running an agent through DevThrottle costs nothing.

First-class agents

Agents with a built-in driver, selectable directly in the New Session dialog:

Claude Code
OpenAI Codex
Cursor CLI
GitHub Copilot CLI
Google Gemini
opencode
xAI Grok
Pi

Any other CLI: the custom agent

The ninth driver is the escape hatch: point DevThrottle at any command-line program and it runs as a session like the rest - terminal on the board, cards, history. If a coding CLI exists, it can sit on the board today, even before it gets a first-class driver.

Tip

Choosing an agent to start with? The coding agents directory compares the field, and the Terminal-Bench scoreboard shows how they score on real command-line work. The agent knowledge base explains how that research is kept honest.

What "supported" means here

A first-class driver knows the agent's install, launch, and interaction quirks, so status detection (working / waiting on you / done) is tuned for it. The custom driver runs anything but reads state more generically.

Note

DevThrottle does not modify the agents. Each one runs exactly as it would in your own terminal - same commands, same flags, same output - with the board watching from outside. Your existing agent configuration keeps working.