Guide: Settings and Runtime Config

What this guide covers

Use this guide when you need to understand how system posture, auth tokens, policy controls, and runtime or agent settings work together inside the workspace settings page.

• Start with the posture hero and status overview so you understand health, auth mode, provider-key posture, and hard-block policy state.
• Treat token security, onboarding, and policy cards as the operational center of settings rather than isolated forms.
• Use runtime config and agent profiles carefully because they influence research, automation, and execution behavior downstream.

Routes and surfaces

These settings surfaces currently shape how a workspace controls policy, runtime behavior, and operator readiness.

Recommended configuration loop

Use this sequence so settings changes stay deliberate and observable.

Status, token, and onboarding controls

These controls tell you whether the workspace is safe to operate before you touch deeper policy or runtime settings.

Policy, runtime, and agent-profile controls

The lower settings cards are where workspace posture turns into actual runtime behavior.

Example change scenarios

Use these scenarios when a settings change needs a concrete operating loop instead of only abstract control descriptions.

Change-control reminders

• Do not change runtime or agent behavior without checking whether the broader posture is already degraded.
• Treat token issuance and active-token use as security events, not only convenience actions.
• Keep block-vs-warn policy changes explicit because they alter how research, data, and production flows fail.
• Review runtime and agent audit trails after major settings changes so downstream behavior stays explainable.

Next steps