Android Thread settings shows disabled models and selects one as default

[asafbennatan]

Description

On Android, Thread settings shows models that have been hidden/disabled in T3 Desktop. Worse, one of the hidden models is selected and marked as the default.

The reporter states that only GPT-6-Luna is enabled in the T3 Desktop model preferences. Android nevertheless shows the full provider catalog and can retain a model hidden on Desktop as the default.

Evidence

Android

Desktop

Steps to reproduce

1. On T3 Desktop, hide/disable all but GPT-6-Luna in the Codex model preferences.
2. Connect the Android app to the same T3 environment.
3. Open an existing Codex thread.
4. Open Thread settings.
5. Expand the Codex model list.
6. Observe the available models and the model marked Default.

These steps are based on the reporter's observation and supplied screenshots; they have not been independently reproduced in this report.

Actual behavior

Android shows Codex models hidden in T3 Desktop. A model hidden/disabled on Desktop is shown as the selected default on Android.

Expected behavior

• Connected clients should either share the same model visibility preferences, or mobile should provide its own model visibility controls.
• Hidden models should not appear as selectable models on Android or iOS.
• A hidden model should never be shown as the default. If the current default becomes hidden, the client should choose a valid visible fallback or require the user to select one.

Impact

Users can unknowingly configure or start threads with a model they intentionally hid/disabled on Desktop. The UI also communicates an incorrect default, which can lead to unexpected token spending when the unintended model has different usage costs.

Root cause context

T3 Desktop stores hidden models in the client-local providerModelPreferences. Mobile currently does not receive or apply that preference, so Android shows the full provider catalog. This is a T3 client-preference synchronization gap, not Codex account availability.

There are two viable product directions:

1. Make model-visibility preferences environment/server-owned and synchronize them across web, desktop, Android, and iOS.
2. Add model visibility configuration to mobile as well, so mobile users can manage its local picker independently.

The first option best matches users expecting Desktop and mobile connected to the same T3 environment to show the same model list.

Environment

• Client: Android app
• App version: 1.1.0
• Provider: Codex
• Desktop Codex version shown in evidence: 0.154.0
• Android version/device: Unknown
• Server/environment version: Unknown
• Reproduction frequency: Reported occurrence; frequency not yet measured

Related issues

• #9350 — closed report documenting the same Desktop/mobile hidden-model preference mismatch.
• #10902 — similar mobile Thread settings/model visibility report, but filed for iOS.

[juliusmarminge]

Triage

Plausible mobile/Codex catalog-vs-default issue; not reproduced here, and not Android-only in code. The reported list (GPT-6-Astra, GPT-5.6-Sol marked Default and selected, GPT-5.6-Terra, GPT-5.6-Luna) matches the current Codex GPT set on main, including the same four rows and Sol Default badge already captured on iOS in #10902.

What the code does

On current main (mobile app version 1.1.1; report is 1.1.0):

1. Thread settings is shared RN. apps/mobile/src/features/threads/ThreadSettingsSheet.tsx + apps/mobile/src/lib/modelOptions.ts buildModelOptions(). There is no Android-specific model filter. An existing Codex thread is scoped to that harness (ThreadComposer → threadProviderGroups).

2. Mobile lists the full server catalog. It skips disabled / uninstalled / unauthenticated providers (and Antigravity-unavailable), and can hide legacy rows until the Catalog toggle. It does not read ClientSettings.providerModelPreferences.hiddenModels. Web does (apps/web/src/modelSelection.ts applyInstanceModelPreferences). Those hide prefs are client-local, not server settings — same split as closed [Bug]: Opencode lists hidden models on mobile app #9350.

3. The Default badge is the catalog preferred default, not “user-enabled.” PREFERRED_DEFAULT_CODEX_MODELS is gpt-5.6-sol then gpt-5.6-terra (packages/contracts/src/model.ts). applyPreferredCodexDefaultModel in apps/server/src/provider/Layers/CodexProvider.ts stamps Sol as isDefault whenever that slug is in the live model/list. The sheet badges that flag. An existing thread stays selected on its stored model; a new-task implicit pick also prefers isDefault. Environment/project defaultModelSelection (e.g. Luna) does not retarget that badge.

4. Codex hidden is ignored. V2ModelListResponse__Model.hidden exists; parseCodexModelListResponse drops it. requestAllCodexModels calls model/list with {} / { cursor } only (no includeHidden). ServerProviderModel has no hidden/enabled field. If Codex still returns hidden: true rows in the default list, every client would show them.

Likely causes (ranked)

1. This is the normal current Codex catalog, with Sol as T3’s preferred default. “Only Luna is enabled” may mean environment/project default, a ChatGPT/Codex plan limit, or a hide on web — none of which currently shrink this Android list. Same four rows on iOS in [Bug]: iOS Thread settings no longer exposes third-party/legacy model selection after update #10902.

2. Web/desktop hide prefs are not applied on mobile. If Astra/Sol/Terra were hidden under Settings → provider models on another client, Android will still show them and can keep Sol as Default/selected. Product/architecture, not an Android renderer bug.

3. Server drops Codex hidden. If the CLI marks Sol/Astra/Terra hidden but still returns them, T3 treats them as first-class and can default to Sol. Would also show up on web unless those slugs were hidden in ClientSettings.

An Android-app-only update does not rewrite the server catalog or Default ranking.

Related, not duplicates

• [Bug]: iOS Thread settings no longer exposes third-party/legacy model selection after update #10902 — same sheet and the same four Codex slugs; iOS report is missing legacy/third-party models. Opposite symptom.
• [Bug]: Opencode lists hidden models on mobile app #9350 (closed) — OpenCode hidden models on mobile. Closed as desktop hide prefs not syncing to the environment catalog.
• [Bug]: Expanding the OpenCode provider does not reveal its models without manual scrolling #10082 — OpenCode expand does not scroll new rows into view.
• [Bug]: Amazon Bedrock Codex model IDs are misclassified as legacy and break text generation defaults #9659 — Bedrock-qualified IDs misclassified as legacy.
• fix(mobile): release confirmed thread model overrides #10205 — mobile draft model-override lifetime after send; not picker visibility.

No open PR filters this Android/Codex disabled-model list or stops Sol from being Default when it is not the user’s enabled model.

Next step

Need a same-environment check before changing UI or the Codex adapter:

• On web/desktop against this server, does the Codex picker also show Astra / Sol / Terra / Luna, with Sol as Default?
• How was “only Luna enabled” configured: Settings hide, environment/project default model, or Codex/ChatGPT plan?
• Does picking Sol on Android actually fail, or is the complaint the badge + extra rows?

If web matches the screenshot, treat this as catalog-default UX (and document Default vs enabled). If web is Luna-only, the gap is mobile not applying hiddenModels (or server not honoring Codex hidden).

Helpful follow-up

• Android build (Play / sideload; repo is 1.1.1) and device/OS.
• Whether Sol/Astra/Terra appear on web for the same environment.
• Whether selecting Sol starts a turn or errors.
• How Luna-only was set, if known.

Labels: bug needs more info via-triage