@brainbase-labs/cli 0.57.0 → 0.59.0-rc.1

package/README.md

@@ -306,8 +306,8 @@ re-cutting the number.
 
 ## Agent runtime configuration
 
-`brainbase.agent.yaml` can declare the provider and default model used by
-managed runs:
+`brainbase.agent.yaml` can declare the provider, default model and runtime mode
+used by managed runs:
 
 ```yaml
 schema: 1
@@ -322,9 +322,17 @@ agent:
 `machine_kind` is applied when the cloud agent is created. Changing it on a
 claimed agent fails before any cloud writes; create a new agent to switch
 providers. `default_model` can be changed with `brainbase agent push`; set it
-to `null` to clear the override. Omitting either field leaves it unmanaged, so
+to `null` to clear the override. Omitting these fields leaves them unmanaged, so
 older manifests keep their existing behavior.
 
+`runtime_mode` accepts `fixed` or `auto`, separately from the lead harness and
+model. An explicit value is synced by `agent create` or `agent push`; omission
+preserves the remote mode. A mode-aware control plane's pull writes `auto` and
+omits `fixed`.
+Runtime Auto requires the server's `self-delegation` feature flag, and children
+also need a self-edge in an orchestration. Legacy control planes refuse explicit
+mode writes. `agent pull --force` discards local runtime-mode edits.
+
 When `agent create` claims a manifest with no `default_model`, the control plane
 gives the agent the platform default for its harness, the same model the web
 console picks, and `agent create` shows it. Cursor, Factory, and Qoder agents