Glossary

4 min read

DevThrottle's terms, in one place, each with the meaning we use everywhere else in these docs and in the product. Each links to the page that goes deeper.

The apps

Director - the Windows desktop app: every agent session as a card in one place. The the Director.
Gateway - the always-on background service that keeps agents reachable, serves the Cockpit and mobile, and runs schedules. What the Gateway does.
Cockpit - the same sessions in a browser, served by your Gateway. The Cockpit.
Launcher - the tray app that keeps the pieces started.

In the Director

Agent - the coding agent tool itself: Claude Code, Codex, Gemini, Grok. It is what you run; a session is one running instance of it. Supported agents.
Session - one coding agent running in one directory; one card in the Director. Session cards and states.
Needs you - the state where a session stopped and asked a question; the Director counts these so nothing waits silently.
Snooze - park a session so it stops asking for attention until a time you choose. Ask for it while the session is still working and it takes effect the moment the work stops.
Queue - prompts waiting their turn in a session. Starting and steering agents.
Agent driver - the per-agent adapter (Claude Code, Codex, ...) that knows how to launch and read that agent; the custom driver runs any CLI. Supported agents.

Working together

Mission - an undertaking: why you are doing something, who is working on it together, and the tasks it breaks into. Sessions attach to a mission, and that attachment is what binds them into one group. Session roles and missions.
Task - one piece of a mission, handed to one worker. A mission has several.
Workflow - a reusable, versioned way of working that a mission can follow, such as one session working alone, or one doing the work and a second reviewing it. The how, where a mission is the what.
Run - one execution of a workflow, carrying what that workflow promised and the evidence for each promise.
Role - what a session is for within its mission: Standalone works alone and faces you, Architect settles the design, Manager drives the work and supervises, Worker builds. Most are worked out for you. Session roles and missions.

Account and money

Credits - the prepaid balance for direct catalog-model calls on the DevThrottle API. You want them when you are building something yourself: point any OpenAI-compatible script or tool at DevThrottle with one dt_ key and it can call any of the models your key supports, instead of holding a separate account and key for each one. A nightly summary job, a bot, a batch pipeline - each direct model call draws on your credits, and nothing can spend past what you loaded. Running your agents in the app needs no credits; dictation, spoken replies, and the wingman are included in Pro and the 14-day Pro trial, key or no key. Billing.
API key (dt_) - a key you create for your own tools to call the DevThrottle API.
Device key - the per-device credential a paired phone or machine holds; revocable per device. Devices.
Activation - the browser approval step that registers a new device to your account. Pairing your phone.

Voice

Custom dictionary - your words, taught once, respected by every transcription on every device. Voice.
Hosted transcription - the speech-to-text behind dictation, run by DevThrottle and included in Pro. Voice.

Automation

Cron / schedules - unattended agent runs on a timer. Scheduled runs.
Control API - driving the fleet from code: the Gateway is the programmatic surface, called by cc-devthrottle with the session's own key. There is no local REST API on the Director. Control API.