docs: clarify secondary model default binding and override precedence - #2553
Merged
Conversation
The secondary_model section did not state whether spawned subagents are forced onto the secondary model or only default to it, nor the full override precedence. Make the semantics explicit in both locales: - spawning resolves the model in order: explicit tool-call model -> profile model_preference -> configured secondary model (default) - the tool's model parameter accepts only "primary" / "secondary" - "primary" means the model the main agent is currently running, not necessarily default_model - the user has no per-spawn switch; overriding is the main agent's decision or a profile setting Also unify secondary-model terminology and the [models] alias wording across the config-files, agents, slash-commands, and env-vars pages.
|
commit: |
daofazhiran
pushed a commit
to daofazhiran/kimi-code
that referenced
this pull request
Aug 4, 2026
…MoonshotAI#2553) The secondary_model section did not state whether spawned subagents are forced onto the secondary model or only default to it, nor the full override precedence. Make the semantics explicit in both locales: - spawning resolves the model in order: explicit tool-call model -> profile model_preference -> configured secondary model (default) - the tool's model parameter accepts only "primary" / "secondary" - "primary" means the model the main agent is currently running, not necessarily default_model - the user has no per-spawn switch; overriding is the main agent's decision or a profile setting Also unify secondary-model terminology and the [models] alias wording across the config-files, agents, slash-commands, and env-vars pages.
7723qqq
pushed a commit
to 7723qqq/kimi-code
that referenced
this pull request
Aug 15, 2026
…MoonshotAI#2553) The secondary_model section did not state whether spawned subagents are forced onto the secondary model or only default to it, nor the full override precedence. Make the semantics explicit in both locales: - spawning resolves the model in order: explicit tool-call model -> profile model_preference -> configured secondary model (default) - the tool's model parameter accepts only "primary" / "secondary" - "primary" means the model the main agent is currently running, not necessarily default_model - the user has no per-spawn switch; overriding is the main agent's decision or a profile setting Also unify secondary-model terminology and the [models] alias wording across the config-files, agents, slash-commands, and env-vars pages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
None — this is a documentation clarification; the problem is explained below.
Problem
The
[secondary_model]documentation did not make clear how a spawned subagent's model is actually chosen. A reader configuring a secondary model could not tell:modelwins over the agent profile'smodel_preference, which in turn wins over the configured secondary model;Agent/AgentSwarmtool'smodelparameter accepts only the symbolic values"primary"/"secondary", not a concrete model alias;"primary"means the model the main agent is currently running — not necessarilydefault_model(e.g. after a mid-session/modelswitch).What changed
Documentation only, both locales kept in sync (
docs/en+docs/zh), verified against the implementation inpackages/agent-core/packages/agent-core-v2:configuration/config-files.md: rewrote thesecondary_modelsection opening — states the default-vs-forced semantics, the full override precedence chain, the symbolicmodelvalues, and what"primary"resolves to; also fixes themodelfield wording (model id → alias of a configured[models]entry) and unifies subagent terminology.customization/agents.md: themodel_preferencerow now notes that an explicit tool-callmodelaccepts only"primary"/"secondary", links to the[secondary_model]config section, and describesprimaryas the caller's currently running model.reference/slash-commands.md+configuration/env-vars.md: unify the secondary-model terminology and the[models]alias wording.Verified with
npm run buildindocs/(VitePress build passes).Checklist
gen-changesetsskill, or this PR needs no changeset. (No changeset: docs-only change, per the skill's docs-only rule.)gen-docsskill, or this PR needs no doc update. (This PR is itself the doc update.)