子代理BUG

[localhosts-A]

使用第三方api时模型调用子代理会失败，llm-deepseek: no API key for provider route "deepseek-official"; store DEEPSEEK_API_KEY through the credentials service (the web Models page writes it), or export DEEPSEEK_API_KEY in the launching environment

[DRAG0NM]

已定位根因：父代理创建时 agentOptions 固化为默认模型选择（defaultModelSelection），而父代理实际运行模型是会话级选择（selectionFor：in-process 选择 → session request header → 默认）；子代理继承的只是 parent.options（创建时默认路由），因此会话内切到第三方 provider 时，子代理仍按 deepseek-official 解析凭据、必然 MISSING_CREDENTIAL。完整源码定位（4 个断点）与修复方案（推荐继承父代理有效模型）见 #455 。

[GaaHoi]

我也遇到了。我当前使用的时deepseek-v4-flash，但workflow工具创建的9个子模型用的却是deepseek-v4-pro😢

[zhujiang611]

Same root cause, full bug report with two-way reproduction & proposed fix:

#1581 — Bug: Subagents inherit the parent session's creation-time model snapshot instead of the model the session actually uses

Summary: resolveChildAgentOptions reads the static creation snapshot (parent.options), while the parent session's actual model is resolved dynamically (selectionFor → latest request header). After a model switch, subagents keep running on the creation-time default. Includes two-way API reproduction (A: created local → switched flash → subagent still local; B: created flash → switched local → subagent still flash), impact analysis (hidden billing, moderation divergence, connection failures), and a precise fix proposal (Option A: request-header precedence with snapshot fallback).