Unverified50% confidenceFactExact time
When a model goes from an ordinary call to an Agent, the model itself does not change; what changes is the code around it (the harness/orchestration layer), which feeds the model's tool requests and the tool return results back to the model round after round.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedSwitching models via /model or startup parameters does not override the model used by sub-agents during task execution.75% similarVerifiedAgents feed commands and contextual information to large language models as prompts, causing the model to return decomposed steps.74% similarUnverifiedA bare large model can only decide to call a certain tool but does not actually execute the tool, whereas an Agent can truly execute tool calls and return results.74% similarUnverifiedModel selection is an underlying variable that affects the stability of the entire Agent system, and models fine-tuned specifically for Agent scenarios tend to perform more stably on tool invocation than general-purpose models.73% similarUnverifiedThe new version added an optional model parameter to spawn_agent, allowing a separate model to be specified for a sub-agent when spawning it.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1007069API
curl https://kongchang.com/api/v1/knowledge/claims/1007069MCP
get_claim(id=1007069)