Repository navigation
fix(web,mobile): lineage and agent rows show which account a subagent runs on - #24833
Approved
- Eligibility
- Correctness
Note
More information about how approvability works can be found in our Help Center.
Details
Eligibility
Adds account badges and branding to subagent and lineage rows so users can distinguish provider instances. The changes affect presentation only, not which account an agent uses or its permissions.
Additional Thinking
Your Custom Policy
Default approvability criteria apply. Neither restriction is triggered: the change displays existing account metadata without changing product defaults, and adds no static-analysis suppression directives.
Code
Adds existing provider-instance badges, names, and accent colors to mobile subagent rows and web lineage rows. Web entries use environment-scoped settings and existing branding helpers; badge visibility uses the shared disambiguation logic. Changes are presentation-only, with no changes to agent execution, account selection, permissions, or persisted settings.
Review Context
The supplied five-file diff was read and shared badge and branding helpers were inspected. Author identity was supplied; no ownership requirements were supplied. Two review threads were reported resolved, with no unresolved comments or correctness findings supplied. No check results were supplied.
Verdict
The change reuses existing account-branding presentation logic in additional UI rows. Its effects are limited to visual account disambiguation and status-marker placement, with no obvious material risk requiring human judgment.
Notes:
No code owners found in target merge base 15fe283
Agent Credits: 30 credits
Approvability runs at a flat rate of 30 credits whenever the agent is asked for a verdict.