Repository navigation
Subagent model allowlist doesn't apply to "new conversations" (blank sessions are reused) #13266
Replies: 1 comment
|
Confirmed on Environment: DSH Repro (deterministic)
A Session created after the change records the current list, so the difference is exactly "when the Session was created" — not a settings problem. On the same installation, the old Session records the old 8 routes and a new one records the new 8 routes. Why a restart does not helpOn startup the client restores the saved selection through
The composition facet is the same root causeThe reuse guide states that a reused blank whose Agent is still loading keeps its creation-time preset composition ("被复用的空白会话若其 Agent 仍在加载状态,会保留创建时的 preset 装配"). In code, Proposed invariant
Minimal shape:
Started Sessions and child Sessions keep their recorded composition and policy; only unstarted top-level Sessions refresh. ScopeA Web/Desktop client workaround exists (bypass blank reuse and create a genuinely fresh Session, which records the current policy), but it cannot help other clients (ACP/SDK/remote) and does not repair Sessions that already started. This needs the Host-side fix. Happy to test a candidate patch on 中文摘要:空白会话的 |
Uh oh!
There was an error while loading. Please reload this page.
中文
授权只在会话创建时采样一次,之后不随设置变化;「新对话」会复用从未发过消息的空白会话,空壳不过期、不清扫。
结果:修改子代理模型授权后点「新对话」,仍可能落进几周前创建的空壳,授权仍是旧的(或为空),委派时报
child LLM route … is not allowed for this Session。用户必须反复新建会话,才能越过之前创建但完全没用过的空会话。English
The subagent model allowlist is sampled once when a session is created, and later settings changes never reach existing sessions. Meanwhile 'New conversation' reuses blank sessions that never started a turn — those shells never expire and are never cleaned up.
So after changing the subagent model settings, clicking New conversation can still land in a weeks-old shell whose authorization is stale (or empty), and delegation fails with
child LLM route … is not allowed for this Session. Users have to create sessions repeatedly just to skip over blank shells they created earlier but never used.Environment:
@deepseek-ai/dsh0.2.2-rc.1 ·dsh web· Windows.All reactions