Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Mobile thread picker hides compatible Codex accounts

Open Beginner friendly
  • Is something wrong?
#14,798 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Brechard is already working on this.

Since Oct 2, 2026.

  • #14805 by @Brechard — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
react-native, typescript
Domain
mobile

Research direction

Start in apps/mobile/src/features/threads/ThreadComposer.tsx, where the exact-instance filter is identified. Compare the mobile picker with the web client's compatible-instance behavior, then reproduce the two Codex instances sharing a CODEX_HOME while separate homes remain excluded. Done means the existing-thread picker shows compatible accounts with different instanceId values and preserves the separate-home restriction.

Written by the indexing model from the issue text.

Description

bug via-triage
Before submitting
  • I searched existing issues and did not find a duplicate for the mobile picker restriction.
  • I included enough detail to reproduce the problem.
Area

apps/mobile

Steps to reproduce
  1. Configure two enabled, authenticated Codex instances with distinct account shadow homes and the same underlying CODEX_HOME. Confirm the server reports the same continuation.groupKey for both.
  2. Start a thread on one instance.
  3. In the mobile thread composer, open Model and reasoning settings.
  4. Look for the other compatible instance's models.
Expected behavior

The existing-thread picker offers compatible instances, matching the web client's behavior and the documented Switch accounts in an existing thread capability. Instances with a separate Codex home remain excluded.

Actual behavior

The mobile composer filters provider groups by exact instanceId, hiding the compatible account. An account reaching its usage limit cannot be changed from that thread on mobile.

Impact

Major degradation: the mobile user must move to another client to select the compatible account, or abandon the existing thread.

Version or commit

Upstream 54084ae1e6c32809db040e4fa571c80fdf2d8ae4. The exact-instance filter is in apps/mobile/src/features/threads/ThreadComposer.tsx.

Environment

React Native mobile client; Codex instances sharing one underlying Codex home. This restriction is shared by the iOS and Android composer code.

Workaround

Select the compatible account through the web client. No new provider or cross-provider switching feature is requested.

Supporting evidence

Verified the picker restriction on iPhone 17 Pro / iOS 26.5, Expo 58 / React Native 0.88.0-rc.3, against the upstream composer at the reported commit.

Baseline existing-thread picker — only Codex Personal

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
7h 14m
Merged PRs (30d)
201

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.