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? Do these three, in order.
About half an hour, and you will have a coding agent doing real work in your own code.
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.
3 tutorialsOut 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 tutorials28 tutorials
Start here
Nothing installed yet, or an empty board. These get you to an agent doing real work.
Download, install, sign in, and point DevThrottle at a gateway - walked through slowly, because this is the step most people fall off at.
A brand new sessionPick a repository, pick a coding agent, name the session, and get a cursor waiting for your first instruction.
Your first real jobEnd to end: ask an agent for a change in your own repository, watch it work, read what it changed, and keep it.
Reading the boardThe colours, timers and labels on a session card, and how to read a whole board of agents in one glance.
The three ways to workDevThrottle is built for three situations - at the office, out and about, and away but at a keyboard. What each is best at, and how the same fleet follows you between them.
The daily loop
The handful of things you do every day once agents are running for you.
The waiting clock, the notification, and what "needs you" actually means - so no agent sits blocked for an hour without you knowing.
Steer a wrong turnInterrupt it, clear what it is holding, compact the conversation, and read back the history to see where it went off.
Talk instead of typingDictate 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 picturesDrag a screenshot onto the prompt, paste one from the clipboard, or send a photo from your phone - and find the pictures your agent produced.
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 agents 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, give it a name, and every agent in your fleet can follow it.
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.
Drop into the raw terminal of Claude Code, Codex or OpenCode and type to it directly, exactly as if you had started it yourself.
Queue the next instructionQueue what comes next while the agent is still busy, instead of sitting there waiting for a free moment to type it.
See what changedThe unsaved-changes badge almost nobody finds on their own, and reading the actual difference before you decide to keep it.
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 agent you are running is in your pocket from then on.
Answer in 30 secondsAn agent needs a yes, or a nudge in a different direction, while you are out. Deal with it and put the phone away.
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 everything is there, with nothing to install.
The fleet mapEvery machine and every agent you have running, drawn as one picture you can read at a glance.
What got done this weekThe history of what each agent did and the numbers behind it - the Friday afternoon question, answered from the Cockpit.
Teach it your wordsDictation keeps mangling your product and repository names. Fix it once: add your words to the dictionary your Gateway shares with every Director and every phone recording.
What you have usedWhat your agents have been spending, broken down by session and by repository.
Going further
Once the daily loop is second nature - the bigger, less obvious things.
Separate signed-in browser profiles, so an agent can use the web without ever acting as you.
Work that runs without youSchedule a job to run every night, or every Monday morning, through the gateway.
More than one machineOne fleet spread over several computers, and how work moves between them.
Driving it from a scriptThe command line and the API, for when you want DevThrottle to do something unattended.