Uh oh!
There was an error while loading. Please reload this page.
feat(web): distinguish provider instances in the sidebar - #6005
Conversation
Threads running on different instances of the same provider looked
identical in the sidebar: every Claude thread showed the same Claude
logo, so two configured accounts (say personal and work) were
impossible to tell apart without opening the thread.
Thread rows now carry the instance's accent color as a dot on the
provider logo, and the hover tooltip names the instance next to the
model ("Claude Work - Claude Opus 5"). The badge appears when an
instance has an accent color, or when a driver has more than one
configured instance, so ambiguity is never silent. This reuses the
badge treatment the model picker already uses; no contract changes.Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 26e6423. Configure here.
Uh oh!
There was an error while loading. Please reload this page.
ApprovabilityVerdict: Needs human review New feature adding visual badges and display names to sidebar threads to distinguish provider instances. First-time contribution from this author; changes are well-contained and follow existing patterns but introduce new user-facing behavior that warrants human verification. You can customize Macroscope's approvability policy. Learn more. |
The sidebar rendered every thread's provider metadata from the primary server's instance list, but it lists threads from every connected environment. Instance ids are user-defined and a driver's default id is the driver kind itself, so `claudeAgent` exists on every server running Claude with a different name and accent on each. A remote thread therefore borrowed the primary machine's account name and color -- the confusion the badge exists to remove -- or lost its badge entirely when the id existed only on the remote. Each environment now gets its own instance lookup, built from the per-environment server configs the sidebar already reads for capabilities.
Problem
If you configure more than one instance of the same provider — two Claude accounts, say a personal one and a work one — the sidebar cannot tell them apart. Every Claude thread shows the same Claude logo, so the only way to know which account a thread runs on is to open it. Provider instances already carry a user-set display name and accent color (Settings → Providers); the sidebar just never used them.
Change
Thread rows now show the instance's accent color as a small dot on the provider logo, and the hover tooltip names the instance next to the model. The badge appears when an instance has an accent color, or when a driver has more than one configured instance, so the ambiguity is never silent.
This reuses the badge treatment
ProviderInstanceIconalready provides for the model picker. No contract or server changes — the instance id is already on each thread and the instance metadata is already on the client.Thread rows
Three of these threads run on Claude and two on Codex. Before, the three Claude rows are identical; after, green marks the personal instance and red the work instance.
Hover tooltip
Project names and thread titles in these screenshots are anonymized test data.
Scope
docs/user/thread-sidebar.mdgains a short section describing the badge.Verification
vp run --filter @t3tools/web typecheck,vp lint,vp fmt --checkclean.Made with Claude Opus 5 via Claude Code.
Note
Low Risk
Sidebar-only presentation using existing thread and per-environment config data; no API or server changes.
Overview
Provider instance badges and names now appear on web sidebar thread rows and hover tooltips, reusing
ProviderInstanceIcon’s model-picker badge treatment (accent dot when configured, or when multiple instances share the same driver).Per-environment lookup replaces resolving every thread against the primary server’s provider list: each row gets
providerEntriesByEnvironment.get(thread.environmentId), with a stable empty map fallback so rows don’t thrash before config loads.User docs add a short Telling provider instances apart section in
thread-sidebar.md.Reviewed by Cursor Bugbot for commit 7b869be. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Distinguish provider instances in the sidebar with badges and instance names
shouldShowInstanceBadgeutility determines badge visibility based on accent color or duplicate driver kinds per environment.deriveProviderInstanceEntries, replacing reliance onprimaryServerProvidersAtom, so threads from remote environments show correct instance names and styling.EMPTY_PROVIDER_ENTRIESconstant prevents unnecessary re-renders when an environment has no config.Macroscope summarized 7b869be.