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/Gateway/What the Gateway does

Gateway

What the Gateway does

4 min read

The Gateway is the always-on hub of DevThrottle. It is the background service that actually runs your coding agents and keeps them alive and reachable - so you can close the Director window, walk away, and come back to the board exactly where you left it. Everything runs on your own machine; your code never leaves it.

The gateway is the always-on hub

Think of one computer as your DevThrottle hub. It keeps your agents running and answers every other device that wants to see the board. Your phone, a browser on another laptop, the Cockpit - they do not run agents themselves, they connect to the gateway and steer the agents it is already running.

One machine acts as the gateway - the always-on hub. It runs the Director board and your coding agents; your phone, browser, and other computers all connect through it.

Windows-only for now

The machine that hosts the gateway has to run Windows today. That is the one hard requirement. A Mac can still run agents as a workstation and connect to a gateway hosted elsewhere - but it cannot be the gateway itself yet. If you want the full experience - agents that keep running in the background, reachable from your phone and browser - the hub needs to be a Windows PC that stays on.

Cross-platform gateway support is on the roadmap. For now, pick the Windows machine you leave on the most - a desktop or an always-on laptop - and make that your gateway.

What runs on the gateway

Your agents. Each coding-agent session runs here and keeps going whether or not the Director window is open.
The board's state. The gateway is the source of truth for which agents are working, waiting on you, or done.
Scheduled runs. A built-in scheduler can launch unattended agent runs on a cron schedule.
The Control API. A local REST API lets tools drive sessions programmatically through the Control API.

How your other devices connect

Because the gateway stays on, you do not have to be at its keyboard. Open the same board in a browser on any machine, or in your pocket on mobile. An agent gets blocked while you are away - you answer it from your phone and keep the work moving. All of that reaches back to the one Windows gateway that is running the agents.

Where to go next

Ready to set it up? Install DevThrottle on your Windows machine and it becomes your gateway on first run. To see how the gateway fits with the rest of the pieces, read the core concepts.