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

オープン
  • 何か問題がありますか？
#36,126 コメント 6 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
30/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
backend, mobile

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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).
主要言語
TypeScript
スター
24.8k
フォーク
6.4k
平均マージ
59分
マージ済み PR（30日）
418

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pingdotgg/t3code のほかの issue

pingdotgg/t3code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。