Repository navigation
Replies: 2 comments
|
sol wrote this I traced the flow, and the issue seems to be in the Codex server integration, not the Agents panel. The UI already supports displaying
A straightforward fix would be to read the model and effort from the completed The spawn event may arrive after the child is registered, so the merge should work in either order. The Agents panel itself should not need changes. |
|
Thanks for calling out the missing model labels. The orchestrator V2 work has now merged in #2829. V2 carries subagent model metadata into the agent presentation and displays the reported model with its effort when available. Unknown values remain unknown rather than borrowing the parent's model. Closing this as delivered. If a specific part is still missing in a build containing V2, please open a focused follow-up with the provider/version and the behavior you are seeing. |
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/desktop
Problem or use case
The Agents panel does not consistently show which model each subagent is using.
In the attached screenshot, the agent row shows the agent name, current activity, token usage, and elapsed time, but not the model
Proposed solution
Show the actual model used by each subagent directly in its row in the Agents panel.
For example:
GPT-5.6 Luna -maxWhy this matters
Model visibility makes it easier to:
Smallest useful scope
Add a model label to every subagent row, visible while the agent is running and after it completes
Alternatives considered
Currently, the user has to inspect logs, open the child session, or ask the parent agent which model was used. These options are slower, and consume extra tokens. Pain
Risks or tradeoffs
No response
Examples or references
Related model-accuracy reports:
Contribution
All reactions