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

Abierto Apto para principiantes
#40,598 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
64/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
react-native, typescript
Área
mobile

Línea de trabajo

Empieza en apps/mobile/src/features/settings/SettingsProviderAccountsRouteScreen.tsx en el filtro canManageProvider, luego revisa la prueba vecina de claude-accounts y los tipos de cuentas de proveedor que consume. Reproduce el problema comparando Settings > Providers con el estado de proveedores en el escritorio y con la pestaña Usage de la app móvil. Está terminado cuando cada instancia de proveedor que el servidor reporta como lista se muestra (las que no son gestionables, en solo lectura), la agrupación está cubierta por una prueba unitaria, y luego se ejecutan el typecheck móvil, las pruebas unitarias y el lint.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
2 h 18 min
PR fusionados (30 d)
448

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.