Runtime Settings
Manage developer binding, account selection, models, reasoning, fast mode, and server lifecycle actions.
On this page
What Runtime Settings controls
Runtime Settings is the control layer for developer binding, account selection, model configuration, reasoning setup, fast mode, public domain visibility, and lifecycle actions such as save, start, restart, and stop.
It is where teams define how the workspace should actually run once the general defaults are already in place.
- 1Bind the correct developer profile for the workspace.
- 2Choose the target account or account-selection mode.
- 3Adjust model, reasoning, and access settings for the workload ahead.
- 4Save the changes, then start, restart, or stop the runtime as needed.
Server runtime
The server runtime area acts as the live control center for runtime behavior. Status panels show the effective state so operators can verify the environment before handing work to the team.
Why it matters
Shared workspaces become risky when runtime state is unclear. Runtime Settings keeps those high-impact controls visible and deliberate.
Verify live state after every change
Runtime configuration only helps when the effective state matches the settings the team believes it is using.