Docs/Tutorials/What you have used
Tutorials

Your Throttle: what you have used

5 min read

After a few weeks of driving agents you start to wonder about your own habits. How much of this do I actually speak rather than type? How often am I steering from my phone? Which repositories is the work really going into? Your Throttle is the page that answers those questions - a private dashboard of how you drive your fleet.

One thing to know before you open it: the page shows activity, not money. It counts turns and characters - never cost, credits, balance, or tokens. That is a deliberate product decision, and it holds everywhere in DevThrottle: your agents run on your own subscriptions and keys, so there is no meter running behind this page.

Five minutes. You need the Cockpit open - if you have never opened it, start with Open the Cockpit from any browser.

  1. Open Your Throttle

    In the Cockpit, look at the bottom of the left rail - the short list pinned under the fleet destinations, where Account and Settings live. Choose Your Throttle.

    If you have never sent anything, the page says so and asks for a turn rather than showing a made-up zero. Send one message to any session and come back.

  2. Read the three rings

    The page opens on Overview: three rings, one question each. Voice vs typing is how much of your driving you speak. Mobile vs desktop is how much of it comes from your phone. Wingman (voice mode) is how much happens with voice mode on, with a note counting the sessions that used it.

    The unit everywhere is the turn - one submitted message. One spoken utterance and one typed message each count as one turn, which is what makes the voice share a fair comparison. Below the rings, a single bar shows where your turns come from - desktop, cockpit, phone - and three tiles give the totals: turns, characters driven, and the most sessions you have ever had running at once.

  3. See your working day on the Activity tab

    Activity holds two charts of the last 24 hours. Turns per hour is the shape of your working day - each bar an hour, voice stacked over typed, empty bars where you were away. Sessions per hour is the fleet's shape - how many sessions were loaded or running each hour, with the darker portion actively working.

    The hours read in the time zone set in Settings, so the axis matches your clock.

  4. See where the work went on the Repos tab

    Repos ranks the codebases you work in by how much driving each one took. It is badged Private - only you: which repositories take your time is nobody else's business, so this tab never renders next to the shareable splits - you have to select it.

    Each row is one repository, with a bar split into spoken and typed turns. Every worktree and every machine you check a repository out on rolls up into its one row - and when more than one checkout fed a row, the working directories are listed under the name. Switch the ranking between Turns, Characters, and Sessions - sessions is the count of distinct sessions that drove input into that repository.

    Time spent is deliberately not shown: an idle hour looks the same as a heads-down hour, so it would lie. Turns and characters track what you actually pushed through.

  5. See which agents you drive on the Agents tab

    Agents is the same ranking by the agent CLI the work goes through - Claude Code, Codex, and the rest. It is also where the fleet's own driving shows up: turns one agent drove into another are counted separately from yours, never added in, and once they exist a Leverage card states how many turns the fleet spent off the back of each turn of yours.

    This tab states the date its attribution started, and its numbers can be smaller than the all-time totals on the other tabs: sessions that finished before the breakdown existed never recorded which agent they ran under, and the page will not guess.

Note
The Breakdown tab holds the supporting tables: fleet concurrency now, this week, and all-time; turns by surface; the full voice-and-typed by surface table; and a plain list of what the numbers do not include. When a figure on the other tabs surprises you, this is where to check what it is made of.
Note
The page refreshes itself every ten seconds, and it remembers which tab you were on in this browser. Your phone has a compact Your Throttle too - the three rings and the totals under the menu - and a separate Repos item; the full charts and breakdown stay on the desktop page.
Tip
Counting happens at the Director, so turns you type into the desktop app count the same as turns sent from the phone or the Cockpit. If your voice share looks low, remember it is measuring everything - including the quick typed one-liners you forget about.

Next

Your Throttle is how you drove; for what the fleet did, work through What did I actually get done this week?. Separate from all of this, your account on devthrottle.com has a Usage page - the record of requests to DevThrottle hosted AI, such as dictation. As a member you see activity there too, in each service's own units; the only money on it is shown to the service's administrators, not to you. Sessions running on your own subscriptions and keys never appear there at all.