Docs/Get started/Start here
Get started

Get started with DevThrottle

2 min read

This is the path through DevThrottle, in order. Each step is one sitting - five to ten minutes - and each one ends by naming the next, so you never have to decide what to read. Start at the top and work down.

You do not need to know anything first. Step 1 assumes an empty machine, and every step after it assumes only the steps above it.

  1. Step 1: Install DevThrottle and connect a gateway - Download, install, sign in, connect a gateway, and get out. Using the Director is step 2.
  2. Step 2: Start your first session - From an empty Director to one agent doing real work in your own code: the New Session window end to end, then the first instruction and the first minute of watching.
  3. Step 3: The prompt bar is not the terminal - The agent has its own live input line; DevThrottle gives you a second box outside it that holds what you write until you send it.

More steps are being written, and each one appears here as it lands.

Then keep going

The steps above teach the spine - the Director, on the machine in front of you. These carry on from there, and they are in order too: the fleet following you off your desk, then running several agents at once, then making DevThrottle work the way you work. Every one of them is written and ready to read now.

Most people walk this part over weeks rather than in one sitting, and stopping partway is a perfectly good place to stop. When you do carry on, this is the order to take them in.

Out of the chair

After these, your fleet follows you off your desk.

  1. Pair your phone with your fleet - Open your gateway address on the phone, approve it on devthrottle.com, and turn on notifications - five minutes at your desk, done before the day you need it.
  2. Answer an agent in thirty seconds - The roster puts what is waiting on you at the top in red. Read the question, answer short, move on.
  3. A whole session by voice, on a walk - Put the fleet on voice, tick Auto-speak, and the queue reads itself to you - Respond by talking, Snooze the rest, and the three-second pause is the way out.
  4. Your whole fleet in a browser tab - Reach every session from any browser, put what is waiting on top, answer it, and sign out again.

More than one at a time

After these, several agents work at once without colliding, across more than one machine.

  1. Repositories and worktrees - Two sessions in one folder edit over each other and nothing stops them. Give each its own worktree, start the session there, and see every worktree of a repository from the Worktrees page.
  2. Roles: who plans, who manages, who builds - Declare an Architect, hand work down and watch the Worker badge appear on its own - the declared planner keeps its A - then read the colours: a supervised Worker never turns red; its Supervisor deals with it.
  3. One agent starting another - From inside a running session, spawn hands work to a fresh session - a Worker supervised by its spawner that never turns red at you - message ask collects the answer, and session done reaps the helper.
  4. The fleet map - Read the whole fleet in one picture, regroup it around the question you actually have, and click straight through to the session that is waiting.
  5. Using more than one machine - The Gateway is the only shared part. Point a second machine at it and that machine becomes somewhere you send work.

Make it yours

After these, DevThrottle runs your way, on your words, on your schedule - including while you sleep.

  1. Workflows: your named ways of working - Read what your fleet already works by, pull one down, write the rules you keep repeating, and publish it everywhere at once.
  2. Work that runs without you - Create a recurring job, read the schedule back in plain English, and prove it works before two in the morning does.
  3. Teach it the words you use - Add your vocabulary and the wrong spellings you actually saw, save, and the cleanup pass corrects them in the transcriptions it covers.
  4. What did I actually get done this week? - Widen the window to a week, read the work by repository, and turn the needed-you count into one prompt worth rewriting.

Four tutorials sit off the path, because not everyone needs them: giving an agent its own browser, driving DevThrottle from a script, what you have used, and dictating on your phone. They are on the tutorials index with everything else, grouped by where you are working.

For the facts behind any of it - every menu item, every setting, every command - the rest of these docs are the reference, and every page here links into them.