From 7db2084787edbc63b585badc8fe41beaa0d03d89 Mon Sep 17 00:00:00 2001 From: Linze Shi Date: Wed, 30 Sep 2026 17:00:40 -0700 Subject: [PATCH] docs: fix utility model migration links (#157441) --- docs/gateway/doctor/config-migrations.md | 2 +- docs/plugins/apple-fm.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/gateway/doctor/config-migrations.md b/docs/gateway/doctor/config-migrations.md index cd70e6f6ebdd..8875088d0fb8 100644 --- a/docs/gateway/doctor/config-migrations.md +++ b/docs/gateway/doctor/config-migrations.md @@ -303,7 +303,7 @@ model value into a different embedding model. See [llama.cpp](/plugins/llama-cpp During an update, Doctor records model-retirement repairs that must wait until plugin installation finishes. The updated OpenClaw completes those repairs after plugin convergence, even when no plugin version changed. `openclaw update status` records their completion so retired subscription models do not fall through to metered API credentials. - Utility-model separation preserves an older config's implicit primary before recording `meta.migrations.utilityModelSeparation: true`. Doctor and normal config writes use the previous config to save that primary explicitly; existing primary selections, fallbacks, and credential bindings stay authoritative. This keeps regular chat available when the old implicit primary also served utility tasks. Fresh utility setup records the separation without choosing a primary, and a provider added during utility setup is not mistaken for the previous primary. See [agent model configuration](/gateway/config-agents/models#agentsdefaultsmodel). + Utility-model separation preserves an older config's implicit primary before recording `meta.migrations.utilityModelSeparation: true`. Doctor and normal config writes use the previous config to save that primary explicitly; existing primary selections, fallbacks, and credential bindings stay authoritative. This keeps regular chat available when the old implicit primary also served utility tasks. Fresh utility setup records the separation without choosing a primary, and a provider added during utility setup is not mistaken for the previous primary. See [agent model configuration](/gateway/config-agents/models#agents.defaults.model). Other commands that encounter legacy keys still ask you to run `openclaw doctor`. Doctor explains the issues, shows its migrations, and rewrites `~/.openclaw/openclaw.json` with the updated schema. Cron job store migrations are also handled by `openclaw doctor --fix`; automatic config-key migration does not import legacy session stores or repair services. diff --git a/docs/plugins/apple-fm.md b/docs/plugins/apple-fm.md index 2ebe82170ae9..d4b61f81b284 100644 --- a/docs/plugins/apple-fm.md +++ b/docs/plugins/apple-fm.md @@ -67,7 +67,7 @@ utility model; the system assistant follows the primary model normally. On an existing installation, choosing Apple preserves your primary model, fallbacks, and credentials. If an older config relied on an implicit primary, setup records that existing route before adding the Apple provider. Doctor and -normal config writes apply the same [utility-model migration](/gateway/config-agents/models#agentsdefaultsmodel). +normal config writes apply the same [utility-model migration](/gateway/config-agents/models#agents.defaults.model). If that migration is still pending, setup asks you to run `openclaw doctor --fix` or choose an explicit primary before connecting Apple. Explicit utility-model configuration can also be set per agent