Repository navigation
[Bug] subagent model selection (list_subagent_models, provider/model) silently missing in resumed/imported sessions and their children #8444
Clemens66666
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Environment: DSH Desktop 0.9.2 on Windows 11,
@deepseek-ai/dsh-tool-subagent0.1.5-rc.2, andsettings.yamlwithsubagent-model-selection.enabled: trueplus a non-emptyallowedModelslist.Symptom: In some sessions,
subagenthas noprovider/modelparameters andlist_subagent_modelsis not registered. The subagent-model-selection setting is ignored, and no error or hint appears. In other sessions on the same machine both are present.We scanned 42 local session logs that use the dsh tools (through the dsh-oh-my-claude MCP bridge and natively). 20 of them have no
subagent/model-selection-policyevent.Cause (
dsh-tool-subagent/lib/index.js,selectForSession, ~L588-601): the policy is read from settings only for a fresh session:list_subagent_modelsand the provider/model schema fields are registered only when a policy exists (~L385-389, L412-425). This causes:session/end-seed, orfirstLiveSeq > 0) never gets the policy, even thoughenabled: trueis set.Expected: a session that has no persisted policy falls back to
settings.current()whenenabledis true, whether or not it is fresh, and child sessions without a parent policy get the same fallback. The alternative is to at least surface a hint that model selection is inactive for this session.Related, but not the same: #7168 (the allowlist is bypassed when provider/model are omitted) and #7421 (the subagent still uses the main model).
Workaround: start a new session instead of resuming one.
All reactions