fix(web): subagent cards name the provider account

[SunkenInTime]

Problem

If you have more than one account on a provider (say two Codex logins), you can't tell which account a subagent ran on. The composer, model picker, and sidebar thread card all show the account, but the subagent hover card in the lineage panel and timeline shows only the model. The bar on a provider-native subagent thread shows only the brand glyph. A user hit this after trying Orchestrator V2: https://x.com/EarleS_0/status/2106589263802323393

To reproduce, configure two instances of one driver (here "Codex Personal" and "Codex Work"), open a thread that delegated work to subagents, and hover a subagent row under Lineage. The card says "GPT-6-Astra" and nothing about the account.

Change

The subagent hover card now reuses the sidebar card's rule. When shouldShowInstanceBadge says the glyph is ambiguous (several instances of one driver, or an accent color set), the model line reads model · account and the icon gets the account's accent dot. Lineage and timeline both render SubagentTooltipContent, so each caller now passes the environment's provider list along with the subagent's provider.

The native subagent bar gets the same two-letter account badge the composer trigger shows.

On mobile, subagent rows already print the account name, but they used the raw snapshot displayName, which falls back to the brand label for an unnamed custom instance. A codex_work instance read as "Codex". They now use resolveProviderInstanceDisplayName like every other surface.

Users with one account per provider see no change.

Scope and approval

There's no approval link. This is a small consistency fix inside an existing capability: per-instance account badges and labels already ship in the composer, picker rail, and sidebar thread card, using shouldShowInstanceBadge and resolveProviderInstanceDisplayName from client-runtime. This PR applies the same helpers to the subagent surfaces that skipped them. It adds no new setting or rule.

Verification

Web dev build in Edge driven by Playwright, seeded from a real database with migrate-dev-db. The sandbox settings name the default Codex instance "Codex Personal" (blue accent) and add a second "Codex Work" instance. The real config already has a second Claude account, "Claude Base". Before shots come from the same build with only the changed file swapped back to main.

• Lineage hover cards on the six visible rows of a thread with 41 subagents. Before: GPT-6-Astra, Claude Opus 5.5. After: GPT-6-Astra · Codex Personal with the blue dot, and Claude Opus 5.5 · Claude.
• Native Claude subagent thread. Before: plain Claude glyph. After: glyph with the CL badge, same as the composer.
• tsc --noEmit in apps/web and apps/mobile: clean. vp lint and vp fmt --check on the touched files: no errors (only existing ChatView.tsx compiler warnings).

Full after view for context:

Not checked: the timeline subagent row hover (it renders the same SubagentTooltipContent, with providers passed from V2LifecycleRow), and the mobile row in a running app. The mobile change is a one-line label swap, covered by its typecheck.

Claude Opus 5.5 in Claude Code, running inside T3 Code.

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at 70b0c13

Macroscope's review found this PR approvable — This is a localized UI fix that makes provider accounts distinguishable in existing mobile and web subagent cards. It only changes displayed labels and badges, with no schema, configuration, processing, or production-infrastructure impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: pingdotgg/t3code/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 6279816d-4be7-4aeb-81ee-423c133980ac

📥 Commits

Reviewing files that changed from the base of the PR and between c5a0c78 and 70b0c13.

📒 Files selected for processing (6)

• apps/mobile/src/features/threads/SubagentRow.tsx
• apps/web/src/components/ChatView.tsx
• apps/web/src/components/chat/ProviderSubagentBar.tsx
• apps/web/src/components/chat/SubagentTooltipContent.tsx
• apps/web/src/components/chat/ThreadRelationshipsControl.tsx
• apps/web/src/components/chat/V2LifecycleRow.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

Web and mobile subagent views now use provider-instance data to display provider names and badges. Web components pass provider lists and badge state to subagent bars and tooltips, which resolve matching instances for display.

Changes

Subagent provider instance labels

Layer / File(s)	Summary
Pass provider data and badge state apps/web/src/components/ChatView.tsx, apps/web/src/components/chat/ProviderSubagentBar.tsx, apps/web/src/components/chat/ThreadRelationshipsControl.tsx, apps/web/src/components/chat/V2LifecycleRow.tsx	Web subagent components pass provider lists or badge state to bars and tooltips. The provider bar uses the supplied state to control its icon badge.
Resolve and display instance labels apps/web/src/components/chat/SubagentTooltipContent.tsx, apps/mobile/src/features/threads/SubagentRow.tsx	The tooltip resolves a matching provider instance for its icon and model label. Mobile subagent metadata uses the provider-instance display-name resolver.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Suggested reviewers: juliusmarminge, jakeleventhal

Merge Risk: ⚪ Minimal · up to 70b0c

This PR changes how subagent views display provider names and badges. The supplied evidence shows compatible data flow and fallback behavior, with no actionable merge risk established; it is mergeable after normal checks.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 44.44% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 6 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: identifying provider accounts on subagent cards.
Description check	✅ Passed	The description covers the problem, change, scope and approval rationale, and verification. It includes before-and-after screenshots and states that timeline hover behavior and the mobile row were not…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}