Skip to content
Discussion options

You must be logged in to vote

Diagnosed the mechanism in the rc.2 source: not intentional, and not the inheritance logic itself -- it is a tier split between what the parent runs and what children inherit.

Agent.options (provider/model) is frozen at session creation, seeded from the default model selection AS OF THAT MOMENT. Everything that steers the model afterwards -- the web model picker, an agent-default-model written to settings mid-flight -- acts through a per-agent selection ref and the agent/request waterfall, then lands in the session log. The parent's own turns therefore follow the CURRENT route (your 838 consistent stealth/ox-alpha entries), but resolveChildAgentOptions in @deepseek-ai/dsh-subagent/src/chi…

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by cancerstick
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants