[Bug]: Mobile Settings > Providers hides working providers (Codex, Grok, Muse, Pi)

Aperta Adatta ai principianti
#40,598 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
64/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
react-native, typescript
Ambito
mobile

Direzione di ricerca

Inizia da apps/mobile/src/features/settings/SettingsProviderAccountsRouteScreen.tsx sul filtro canManageProvider, poi guarda il test vicino claude-accounts e i tipi degli account provider che utilizza. Riproduci confrontando Settings > Providers con lo stato dei provider sul desktop e con la scheda Usage dell'app mobile. È fatto quando ogni istanza di provider che il server segnala come pronta viene mostrata (quelle non gestibili in sola lettura), il raggruppamento è coperto da un test unitario e poi si eseguono il typecheck mobile, i test unitari e il lint.

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

Descrizione

Area: apps/mobile
Impact: Minor bug or occasional failure
Version or commit: read against main @ 26d81d88; installed iOS app version not recorded
Environment: iPhone (T3 Code iOS app) connected to a macOS desktop environment; providers on the server include Codex, Claude, Cursor, Grok, Antigravity, Copilot (ACP Registry), Muse Code and Pi

Steps to reproduce
  1. On a desktop environment, configure several providers, including at least one Codex instance signed in through the Codex CLI and one of Grok, Muse Code or Pi. All show ready on desktop.
  2. Open the mobile app, connect to that environment, and go to Settings > Providers.
Expected behavior

Every enabled provider instance on the environment is listed, so I can see what the phone can use. Providers whose sign-in cannot be managed from the phone can be read-only.

Actual behavior

Only Cursor, Antigravity, Copilot and the Claude config-folder accounts are listed (only some of my enabled instances). Codex, Grok, Muse Code and Pi are missing with no explanation, so the screen reads as if those providers are not connected. They do work from the phone: the Usage tab lists the Codex accounts and their limits.

The cause appears to be the filter in apps/mobile/src/features/settings/SettingsProviderAccountsRouteScreen.tsx: canManageProvider keeps a provider only when setup.canAuthenticate is true or it is an installed acpRegistry driver, and Claude instances are rendered separately. Every other instance is dropped. The screen is titled "Providers", which is what makes the short list misleading.

Workaround

Check provider state on desktop, or on the mobile Usage tab.

Offer

I have a small patch against 26d81d88 that renders the remaining policy-allowed instances as read-only rows with their reported status ("Available" when the server reports ready with unknown authentication), and moves the three-way grouping into a tested helper. Locally: 12 of 12 unit tests pass (the new helper test and the neighbouring claude-accounts test), the mobile typecheck passes, and lint and format pass on the changed files. It has not been run on a device and I have no before/after screenshots yet. If you consider this a bug and not intended design, I can open a PR with screenshots; if it is intended, renaming the screen to something like "Provider accounts" would also remove the confusion.

The analysis and patch were produced with Gemini 4 Neon (Antigravity CLI) and GPT-6.2 Sol (Codex) in T3 Code, then reviewed over three rounds by models from three other labs.

Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
2h 18m
PR unite (30g)
448

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.