[FEATURE]:Show reasoning/variant level for subagents in the UI #26266

Activity

1. github-actions

   assigned

   Hona

   on May 8, 2026
2. github-actions commented on May 8, 2026

   

   github-actionsBot

   on May 8, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [FEATURE]: Show subagent model in session tree / subagent view #23028: Requests showing the subagent's model in the session tree/UI — your request to also show the reasoning/variant level is closely related and may be better added as a comment there.
   • Subtasks do not inherit the active model variant from the parent session #24757: Subtasks not inheriting the active model variant from the parent session — related to variant/reasoning level handling in subagents.
3. zzy2210 commented on May 8, 2026

   

   zzy2210

   on May 8, 2026

   Author

   More actions

   This issue might be a duplicate of existing issues. Please check:

   * [[FEATURE]: Show subagent model in session tree / subagent view #23028](https://github.com/anomalyco/opencode/issues/23028): Requests showing the subagent's model in the session tree/UI — your request to also show the reasoning/variant level is closely related and may be better added as a comment there.
   
   * [Subtasks do not inherit the active model variant from the parent session #24757](https://github.com/anomalyco/opencode/issues/24757): Subtasks not inheriting the active model variant from the parent session — related to variant/reasoning level handling in subagents.
   

   I think this feature would be even more useful if the UI showed not only the subagent's model, but also the effective reasoning / variant / effort level being used.

   For example:

   • Plan — GPT-5.4 — high
     • General — GPT-5.4-mini — medium
     • Build — Sonnet-4.5 — default

   Currently, when a subagent is invoked, seeing only the model name can still feel incomplete, especially for models where variants or reasoning-effort levels significantly affect behavior, latency, and cost. Displaying the effective variant/reasoning level would make subagent runs more transparent and easier to audit/debug.

   This also seems related to #24757, where subtasks may not inherit the active model variant from the parent session. Even after inheritance/configuration behavior is fixed, showing the effective variant in the session tree or subagent view would help users verify what is actually being used at runtime.
4. mewa commented on Jun 26, 2026

   

   mewa

   on Jun 26, 2026

   More actions

   Agree. It's really unintuitive that the subagent is missing the model variant. It should be showing the exact same way the top-level UI already does.
5. akhansari commented on Jul 15, 2026

   

   akhansari

   on Jul 15, 2026

   More actions

   This feature will be really helpful. Especially because it's not the same cost between medium and xhigh variants. It's reassuring to verify that and avoid accidentally burning tokens.
6. samiralibabic commented on Jul 23, 2026

   

   samiralibabic

   on Jul 23, 2026

   More actions

   I can reproduce this in the current TUI.

   The main-session prompt footer shows the selected model variant, but when navigating into a subagent session, the TUI replaces that footer with SubagentFooter. That footer currently shows only the subagent name, position, context usage, cost, and navigation controls—no model or variant.

   It would be useful to display something like:

   Explore · gpt-5.4 · xhigh

   The value should be derived from the child session’s effective persisted model/variant, rather than the parent/global model selector, so it remains accurate when the subagent has its own model or variant configuration.

   This appears to be a presentation-only gap: the child session already records the effective model/variant.
7. github-actions commented on Sep 22, 2026

   

   github-actionsBot

   on Sep 22, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
8. github-actions

   closed this as not plannedon Sep 22, 2026
9. samiralibabic commented on Sep 29, 2026

   

   samiralibabic

   on Sep 29, 2026

   More actions

   Why "open a new one" and not "re-open it"?! Stupid bot!