[Bug]: Mobile model picker: Opus 5.5 under a second Claude instance runs on the default Claude instance

Offen
  • Stimmt etwas nicht?
#36,126 6 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
30/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
backend, mobile

Rechercherichtung

Start in the mobile thread settings sheet, ThreadSettingsSheet.tsx, and follow option.selection into selectThreadModel and draftModelPickMatchesThread, checking whether instanceId survives the pick. Then trace the draft send path and the server-side cross-instance resolution. Done means a mobile pick of Claude Pulse Opus 5.5 runs the turn on the Claude Pulse instance. Open PR #25587 may touch the same path, so check it first.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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. On a server with two Claude Code provider instances, the default claudeAgent ("Claude") and a second one with its own CLAUDE_CONFIG_DIR ("Claude Pulse"), both offering Claude Opus 5.5.
  2. Open an existing thread in the mobile app (iPad, split view). The thread was on Codex GPT-6.1 Terra.
  3. Open Thread settings, scroll to the Claude Pulse group and pick Claude Opus 5.5, then confirm with the check button.
  4. Send a message.
Expected behavior

The thread runs on Claude Pulse · Opus 5.5, as the same pick does on web and desktop.

Actual behavior

The thread switches to Claude Opus 5.5 on the default Claude instance instead. The model is right, the provider instance is wrong. In our case the default Claude account had already hit its usage limit, so the turn failed with "Claude API rate limit reached. Try again later." even though Claude Pulse was the account picked. It only happens on mobile; the same pick from web/desktop lands on Claude Pulse.

The picker in the screenshot lists both groups separately, each with its own "Claude Opus 5.5 · Default" row (Claude Pulse's Opus and Fable are starred favorites).

Reading main (7903b48), the sheet itself looks instance-aware: ThreadSettingsSheet.tsx passes option.selection (with instanceId) to selectThreadModel, which keeps a cross-instance pick as a draft until the next message, and draftModelPickMatchesThread compares instanceId. So the instance is probably lost after the pick: when the draft pick is sent with the message, or when the server resolves a cross-instance switch to a model of the same driver.

Impact

Blocks work: with two Claude accounts, mobile cannot move a thread onto the second account, which is the reason to have it.

Version or commit

Server 0.1.3 (macOS); current iOS/iPadOS T3 Code app (November 2026)

Environment

iPad mobile app connected to a macOS desktop server. Providers: Codex, Claude (claudeAgent), Claude Pulse (second Claude Code instance).

Workaround

Pick the Claude Pulse model from web or desktop.

Related
  • #28872: mobile had no way to switch to another Claude login (closed; that setup had only one Claude instance).
  • #25587: mobile model pick applies to the message it was sent with (open PR, may touch the same path).
Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
59 Min.
Gemergte PRs (30 T.)
418

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.