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

Aperta
  • Qualcosa non va?
#36,126 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend, mobile

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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).
Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
59m
PR unite (30g)
418

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pingdotgg/t3code

Tutte le issue di pingdotgg/t3code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.