Director settings

4 min read

Open settings with the Settings toolbar button, or File - Settings (Ctrl+comma). The dialog is organized into seven tabs: Account, Gateway, Agents, Browser profiles, Directories, Advanced, and Tools.

Account

A read-only view of your DevThrottle account: the Gateway this Director connects through, and who is signed in. There are deliberately no sign-in controls here - when a Gateway is connected, your account is managed there, sign-in and identity included, and every Director on the machine inherits it. One button, Manage connection..., jumps you to the Gateway tab at whatever step the connection is currently on.

Gateway

This tab is a single guided connection panel rather than a form of addresses and tokens. It scans for Gateways - on this computer and over Tailscale - and lists what it found, with one marked Recommended. Picking one connects immediately and checks the connection in both directions, so there is no separate Test step: you watch it reach the Gateway, then watch the Gateway reach this Director back. Then it asks you to Sign in with DevThrottle, which is what puts this device's own token on it - there is no pairing code to type.

When it is done the tab shows the two green ticks - connected, signed in - and an Advanced disclosure holding the things you rarely need: the Gateway address and this device's token, masked. Back on the scan step, the same disclosure holds a box for typing an address by hand when the scan cannot find yours. Change gateway disconnects and starts the scan over, for moving between a local Gateway and the hosted one.

Agents

The list of coding agents that appear in the New Session dialog, in the order they appear there. Each row has a display name, a type, an Enabled checkbox, and a status pill saying whether the agent's command checked out; the arrows on the left reorder the list, Edit opens that entry in its own dialog, and the trash removes it. + Add Agent creates an entry by hand. You can have several entries of the same type - two Claude entries with different presets, say.

Setup wizard... re-runs the whole first-run setup - agents, tools, where your code lives, screenshots, and the Gateway - and leaves anything already set up alone. It is the way back to the guided path, not an agent scanner.

Note

Eight agents ship with a built-in driver - Claude Code, Pi, Codex, Gemini, OpenCode, Cursor, Grok and GitHub Copilot - and any command line of your own runs as a custom agent. What you find in this list the first time is not all eight, though: DevThrottle looks for each of them on the machine and seeds a row only for the ones it finds, so an agent you have not installed is simply absent rather than listed and broken. Install it and re-run the setup wizard, or add the entry by hand. What each entry holds is covered on coding agents in the Director.

Browser profiles

Real, signed-in browser profiles your agents can drive, each with its own logins and kept apart from the browser you use yourself. + New browser profile asks what the profile will be signed in as and which installed browser to use, then opens an empty window for you to sign in by hand - DevThrottle never types your credentials and never sees them. Tell it you are done and the profile is listed as ready for any agent on the machine to drive. Profiles can be renamed and removed, and removing one takes its own folder with it.

Driving them needs Browser Harness, which this tab installs for you into its own environment; until it is there the profiles stay listed but cannot be driven. The full walkthrough is on giving an agent its own browser.

Directories

Where screenshots land. Images you send from your phone are saved to this folder and appear in the session's Screenshots panel; Detect finds the default location and Browse picks another. On a Mac this one has to be set explicitly.

Advanced

Two cards. Network and Firewall turns off the Windows pop-up that asks whether to allow the app on your networks - Windows asks for administrator approval once, and then it stops appearing. Alpha Features is a single checkbox, off by default, that reveals experimental features still being verified. This documentation covers the product with the checkbox off.

Tools

DevThrottle ships a set of command-line helper tools (the cc-* tools) that agents can use. This tab shows their status, offers Download and repair tools, and has an Automatically keep cc-* tools up to date checkbox - on by default, so the tools stay current without you thinking about them.

Tip

The footer of the dialog has an Open config.json link - the file behind every setting, for when you want to see or script the raw configuration.

Settings that are not in this dialog

Settings that belong to your account rather than to one Director window are on the Cockpit's Settings page (open Cockpit from the toolbar). That is where choices such as voice transcription live - dictation comes with your plan and needs no key of its own. See the Cockpit.

Two things people go looking for there are somewhere else entirely. Whether the Gateway starts when you log in is set by the installer and changed with the cc-devthrottle autostart command (on, off, status) - see keeping agents running. And there is no longer any setting for how devices address each other on your network; the Gateway tab's own scan works that out.