feat(host-agent): default planner transport to cloud

2026-07-14 20:42:27 +08:00
parent 6e511111c4
commit 30f09b6268
10 changed files with 98 additions and 78 deletions
@@ -22,12 +22,11 @@ provider/model or rotate a key without touching any Host.
 - Cloud API owns `AI_PLANNER_PROVIDER`/`AI_PLANNER_MODEL`/provider API keys
  as its own configuration; these are no longer required on the Host Agent
  when the new proxy transport is used.
- Host Agent gains a new opt-in transport setting (proxy vs. direct-to-provider)
+- Host Agent gains a transport setting (cloud-proxy vs. direct-to-provider)
  and a new `ToolCallingClient` implementation that calls the cloud endpoint
-  instead of constructing a local Anthropic/OpenAI SDK client. The existing
-  direct-to-provider transport remains fully supported and is the default,
-  so hosts that already run with a local provider key keep working
-  unchanged.
+  instead of constructing a local Anthropic/OpenAI SDK client. Cloud-proxy is
+  the default; the existing direct-to-provider transport remains fully
+  supported as an explicit opt-out for hosts with local provider keys.
 - Reuse the existing Host-scoped bearer credential (already used for
  heartbeat/claim/renew/result) for the new endpoint; no new auth scope.
 - Cloud API does not durably persist screenshot bytes or full prompt text