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

Aberta Para iniciantes
#40,598 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
64/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
react-native, typescript
Domínio
mobile

Direção de pesquisa

Comece em apps/mobile/src/features/settings/SettingsProviderAccountsRouteScreen.tsx no filtro canManageProvider, depois veja o teste vizinho de claude-accounts e os tipos de contas de provedor que ele consome. Reproduza comparando Settings > Providers com o estado dos provedores no desktop e com a aba Usage do app móvel. Está pronto quando cada instância de provedor que o servidor informa como pronta é renderizada (as não gerenciáveis em somente leitura), o agrupamento está coberto por um teste unitário, e então são executados o typecheck do mobile, os testes unitários e o lint.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
24.8k
Forks
6.4k
Merge médio
2h 18min
PRs com merge (30d)
448

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de pingdotgg/t3code

Todas as issues de pingdotgg/t3code

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.