Coming soon
Everything on this page is not built yet. It is here so you can see where DevThrottle is going, and tell us if we are pointing it at the wrong thing. There are no dates — we would rather show you the work than promise you a month.
In design now
Today the Director shows you one session at a time, and everything else waits in a list down the side. That is fine with two agents. It is the wrong shape for ten.

The reason to watch two agents is that one of them is about to ask you something. Every pane keeps its own message box, so replying never means finding your place again.
Order the list by who has been waiting longest, then fill the screen from the top. You deal with the fleet in the order it actually needs you, not the order you happened to start things in.
Panes stay where you put them. The app never re-arranges itself under your hands while you are typing into one of them.
Any session can leave the main window and become a window of its own — then dock back when you are done with it.

Not four. All of them — every session as a small live card, so you can find the one you want and put it on screen.

Shorter descriptions, same rule: none of this exists yet.
Token spend turned into dollars, per task, per repository, per hour of the day. Right now almost nobody running coding agents can answer what their month actually bought them. You will be able to.
Give each session its own isolated checkout, so two agents working at once can never trip over each other’s edits. Review what one changed and merge it without leaving the app.
Shut everything down at the end of the day and restore the whole workspace tomorrow — every agent back on its task, with the context it had, whichever coding agent it is.
Instead of asking you to pick a session, the app opens on what is waiting — longest wait first — and lets you answer, approve or wave it on without opening anything.
An agent that has hit its own usage limit looks nothing like one asking you a real question. It will stop pretending to be the same thing.
An honest report on your week with the agents and how to get more out of the next one. A coach, not a scoreboard — and it comes to you rather than waiting to be opened.
One screen for what your week actually looked like: how much you spoke versus typed, from which device, on which projects. The measurements are already being taken; the screen is what is missing.
The order this gets built in is not fixed. If one of these would change how you work, say so — that is the most useful thing you can send us.