Policy and runtime values
The dashboard owns managed harness settings, MCP entries, and extension packages. The mountedblue.yaml owns allowed harnesses, session-upload policy, the gateway section, and the optional curated package catalog. The Control API binds inference access to the source OAuth session while keeping the provisioned gateway credential server-side.
gateway.type into policy and adds gateway.proxy_url and the runtime-only gateway.token only to the delivered client response. Server credentials never enter the governance document. The token is a session-bound inference JWT and is never persisted by the Control API. The gateway has no model field; each agent uses its managed model when present or leaves model selection to the agent. gateway.provisioner.type selects the built-in LiteLLM implementation or the pinned executable. Gateway-specific key models, teams, budgets, resets, and API behavior belong in that implementation, not in blue.yaml.
Revisions and caching
Every successful dashboard save creates a new immutable revision. Clients cache the most recently fetched response and honorttl_seconds. A running governed wrapper watches the optional server-sent revision stream and displays a desktop notification when a restart is needed; older or BYO services fall back to a 60-second check. The active agent is never interrupted or rewritten. Login only stores authentication. Run blue apply or blue daemon to keep the default agent current; another agent is reconciled when explicitly launched through Blue.