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/The board (Director)/Source control and history

Director

Source control and history

3 min read

Agents edit real files in a real repository, so the board keeps the answer to "what did it actually change?" one tab away. Two surfaces cover it: the Source Control tab shows the state of the session's git repository, and the History tab shows the conversation that produced it.

The changes badge

Each session card carries an amber "N chg" badge - a live count of uncommitted changes in that session's repository. It is the earliest honest signal of progress: an agent that claims to be done with zero changed files, or one that has quietly touched forty files, both deserve a look before you move on.

The Source Control tab

Screenshot coming soonThe Source Control tab showing the branch bar with ahead and behind badges, and the Staged Changes and Changes file trees

The Source Control tab showing the branch bar with ahead and behind badges, and the Staged Changes and Changes file trees

Select a session and open Source Control. At the top, the branch bar shows the current branch and how it relates to the rest of the world: an Ahead badge for commits not yet pushed, Behind for commits not yet pulled, a behind main badge when the branch is drifting from the main line, and a note when the branch has no upstream yet. Below it, two collapsible file trees - Staged Changes and Changes - list what the agent has modified, each with a count. When the working tree is clean it says so: "No changes detected".

Note

The Source Control tab is a review surface, not a git client. When you are happy with the changes, commit them the way you always do - ask the agent to commit, or use your own git tools. Open in VS Code and Open in Explorer on the card menu drop you into the repository directly.

Conversation history

The History tab is the session's transcript - every message between you and the agent, with Show filters for Tool calls, Results, and Thinking so you can read just the conversation or audit exactly which actions the agent took and what came back.

Tip

When a diff surprises you, read History with only Tool calls turned on. The list of file edits and commands, in order, is usually the fastest way to see where the agent went off the path you intended.

Past sessions

Closed sessions are not gone. The Resume Session tab in the New Session dialog lists past Claude Code conversations - each with a summary, its message count, and how long ago it ran - and reopens one with its context intact. See starting and steering agents.