Skip to content

[Bug]: Mobile composer doesn't show which account a thread uses (web shows the account badge) #15910

Description

@vitalyiegorov

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/mobile

Steps to reproduce

  1. Set up two accounts of one provider, for example two Claude instances named "Personal" and "Work".
  2. Open a thread on the Work account on web and on mobile.
  3. Compare the model control in the composer.

Expected behavior

The mobile composer shows the account badge (WO) next to the model, as web does. That's how you can tell which account the next message will use.

Actual behavior

Mobile shows only the bare provider glyph, so the same thread looks identical on Personal and on Work. You only find out which account it uses by opening the model sheet. Same thread, same moment:

Web:

Web composer: WO badge on the Claude glyph next to Claude Opus 5.5

Mobile (iOS 26.5 simulator):

Mobile composer: bare Claude glyph next to Claude Opus 5.5, no account badge

Cause

ThreadComposer.tsx (renderIcon) draws the plain ProviderIcon. Mobile already has the shared ProviderInstanceIcon and the shouldShowInstanceBadge rule, which the thread rows use since #9898 → #9899.

The other mobile places that pick or show a thread's account have the same gap: the new-task draft (NewTaskDraftScreen.tsx), the thread settings sheet (ThreadSettingsSheet.tsx), and subagent rows (SubagentRow.tsx, thread-subagent-group.tsx). On web, each of these has the badge.

Impact

Minor bug or occasional failure

Version or commit

main at a1d9d72

Environment

iOS 26.5 simulator (iPhone 17) and web, against one Linux host with two Claude accounts.

Workaround

Open the model sheet and read the instance name.

Related

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.via-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions