DevThrottle tutorials
2 min read
Each tutorial is one job, start to finish, with the screens you will actually see. They teach you a path through something; the rest of these docs hold the details, and every tutorial links out to them.
New here? Start with the path, not this page.
There is a numbered path that takes you from an empty machine to running several coding agents at once. Read it in order - each step is one sitting and ends by naming the next.
Where are you working today?
DevThrottle is built for three situations, and the tool you reach for changes with where you are. Most people end up using all three in the same week.
Fastest of the three. Every agent's terminal is right there and you can type straight into it.
1 tutorialOut and aboutYour phoneAnswer an agent in thirty seconds while shopping - or work by voice for hours on a long walk.
3 tutorialsAway, but at a keyboardThe Cockpit, in any browserAs close to being at your desk as it gets, with nothing to install - plus your week in review.
5 tutorials19 tutorials
The daily loop
The handful of things you do every day once agents are running for you.
Dictate a prompt anywhere you would have typed one - much faster once it is a habit, on the desktop, in the browser, and on your phone.
Working with picturesThe detail behind the pictures step: which file types each surface recognises, what the Screenshots panel buttons do, which folder it watches, and where DevThrottle hands a picture over to the agent.
Running more than one
Where DevThrottle stops being a nicer terminal and starts being a team.
Split one job across several sessions so they help each other instead of colliding - what each role does and when to use one.
One agent starts anotherHand a piece of work to a fresh session from inside the one already running, and get its answer back.
Repositories and worktreesWhat stops two sessions fighting over the same copy of your code, and how to give each one its own place to work.
WorkflowsWrite down how a job should be run once, publish it, and sessions launched after each Director's next poll see it in their briefing - starting from a built-in workflow rather than a blank file.
At your desk: the desktop app
The fastest of the three ways to work. Nothing sits between you and the agent - every session carries a real terminal you can type straight into.
Out and about: your phone
Two quite different jobs. One is rescuing an agent in half a minute while you are shopping. The other is a long walk where the phone is the only thing you are working on.
Set your phone up once, and every session you are running is in your pocket from then on.
Answer in 30 secondsAn agent has stopped and is waiting on you while you are out. Open your phone, read the question, answer it, and put the phone away - the short interaction you will do most often.
A session by voiceVoice mode reads each turn out loud and you answer by talking - hours of real work from a footpath or a quiet bench, with no screen.
Any browser: the Cockpit
Away from the office with a real keyboard in front of you - and the place you go at the end of a week to see what actually happened.
A hotel laptop, a client machine, a spare desktop - sign in and every agent you are running is there, with nothing to install on the machine you are borrowing.
The fleet mapEvery machine and every session you have running, drawn as one picture - so the only question that matters, is anything waiting on me, is answered before you read anything else.
What got done this weekYour agents worked while you were elsewhere. The Cockpit history shows what ran, in which repository, how many turns it took and how often it needed you - which is the number worth acting on.
Teach it your wordsDictation keeps mangling your product and repository names. Fix it once: teach your Gateway dictionary the right spellings and the wrong ones you have seen, and they are corrected everywhere you dictate.
What you have usedHow you actually drive your fleet - spoken vs typed, phone vs desktop, and which repositories and agents the work went into. Activity in turns and characters; no money anywhere, by design.
Going further
Once the daily loop is second nature - the bigger, less obvious things.
Create a separate browser profile, sign it in once by hand, and have an agent drive it through Browser Harness - so which accounts an agent acts as is a decision you made on purpose, never your everyday browser.
Work that runs without youSchedule an agent to run every night or every Monday morning through the Gateway - pick the machine, say when in plain English, and run it once by hand before you trust it.
More than one machineOne machine runs out before you do. Add a second computer to the same fleet by enrolling it with the Gateway you already have, then give it its own clone of the code it will work on.
Driving it from a scriptThe command line, for when you want DevThrottle to act while nobody is watching - read your fleet, message a session, and put it on a schedule.