codex - 💡(How to fix) Fix Codex Mobile remote-control tasks with custom provider disappear from thread list after refresh

What version of the Codex App are you using?

Codex Desktop: 26.519.81530
Codex CLI: 0.133.0

What platform is your computer?

macOS 26.3.1 (a) (25D771280a)

What issue are you seeing?

When Codex Desktop on macOS is configured to use a custom OpenAI-compatible Responses API provider, Codex Mobile remote control can start a new task and the Mac host executes it successfully. However, after refreshing the Codex Mobile thread/task list, that task disappears from the mobile list.

The task is not deleted locally. It remains present in the Mac host's local Codex state (~/.codex/state_5.sqlite) and rollout JSONL under ~/.codex/sessions/....

This appears related to custom-provider thread list/history filtering, but the user-visible symptom is specifically in Codex Mobile remote control:

• Mobile can create/send the task to the Mac host.
• The Mac host executes the task using the custom provider.
• The live task is visible while it is running.
• After refreshing/reopening the mobile list, the task is no longer visible.
• Threads created with the normal openai provider are visible in the mobile history/list.
• Existing local custom_responses_provider/custom-provider Mac threads are not discoverable from the mobile history/list.

The custom provider is configured in ~/.codex/config.toml similarly to:

model = "gpt-5.5"
model_provider = "custom_responses_provider"

[model_providers.custom_responses_provider]
name = "Custom Responses Provider"
base_url = "<redacted OpenAI-compatible /v1 endpoint>"
wire_api = "responses"
env_key = "CUSTOM_RESPONSES_API_KEY"

The Mac host is still logged in to the ChatGPT/OpenAI account for Codex Mobile remote control. Remote control enrollment is present and working: mobile remote control can reach the Mac and submit work.

What steps can reproduce the bug?

1. On Codex Desktop for macOS, configure a custom model provider in ~/.codex/config.toml, for example model_provider = "custom_responses_provider" with wire_api = "responses".
2. Keep Codex Desktop logged in to the ChatGPT/OpenAI account used by Codex Mobile.
3. Connect Codex Mobile to the Mac host through remote control.
4. From Codex Mobile, start a new task/thread on that Mac host.
5. Observe that the Mac host receives the task and executes it successfully through the custom provider.
6. Refresh or reopen the Codex Mobile task/thread list.
7. Observe that the newly created custom-provider task disappears from the mobile list.
8. Switch the Mac host back to the normal openai provider and create a task. That task appears in the mobile history/list as expected.

What is the expected behavior?

Codex Mobile should list and allow reopening/continuing local Mac-host threads created through remote control even when the host used a custom model provider.

More specifically:

1. A task created from Codex Mobile and executed on the Mac host with model_provider != "openai" should remain visible after mobile list refresh.
2. The mobile history/list should include local host threads across providers, or at least include threads for the currently connected host regardless of provider.
3. Opening a custom-provider thread from mobile should route continuation back to the same Mac host and preserve the thread's persisted model provider.

What is the actual behavior?

1. The custom-provider task runs successfully on the Mac host.
2. It may appear temporarily while live/running.
3. After refreshing the Codex Mobile list, it disappears.
4. Local Mac state still contains the thread and rollout file.
5. Normal openai provider threads remain visible in the mobile history/list.

Local evidence

On the affected machine, local SQLite state shows custom-provider threads are persisted and not archived:

model_provider  source  thread_source  archived  n
--------------  ------  -------------  --------  --
custom_provider  cli     user           0         1
custom_provider  vscode  user           0         7
openai          cli                    0         17
openai          exec                   0         12
openai          vscode                 0         34
openai          vscode  user           0         8

Remote control enrollment exists locally, and the mobile-to-Mac execution path works:

app_server_client_name  server_name               websocket_url_len
----------------------  ------------------------  -----------------
Codex Desktop           <local Mac host name>      56

The custom-provider threads also have rollout JSONL files under ~/.codex/sessions/YYYY/MM/DD/.

Related issues

This seems related to existing custom-provider history/list issues, but this report is specifically about Codex Mobile remote-control visibility after refreshing the mobile list:

• https://github.com/openai/codex/issues/20184
• https://github.com/openai/codex/issues/19088
• https://github.com/openai/codex/issues/20004
• https://github.com/openai/codex/issues/15494
• https://github.com/openai/codex/pull/19287

Security notes

No API key or private provider URL is included here. Thread titles and message content are intentionally omitted.