Codex Remote mobile-created tasks ignore the host model provider and offer no provider selection

Open 💬 0 comments Opened Jul 14, 2026 by Follen

What issue are you seeing?

When creating a new Codex task from the official mobile Remote interface connected to Codex Desktop, there is no way to choose the model provider.

The host is configured with a non-default provider in ~/.codex/config.toml, and tasks created directly on the host use that provider correctly. Existing host-created tasks also continue to work when controlled from mobile.

However, a task created directly from mobile Remote is recorded with model_provider=openai instead of the host's configured provider. The request then uses the built-in ChatGPT/OpenAI route. If the selected model is only available through the configured provider, the task fails before producing an assistant response.

Environment

  • Host OS: Windows x64
  • Codex Desktop: 26.707.9981.0
  • Codex CLI: 0.144.2
  • Mobile client: official ChatGPT mobile app / Codex Remote
  • Authentication: ChatGPT login
  • Host config: non-default OpenAI-compatible Responses provider

Steps to reproduce

  1. Configure Codex Desktop with a non-default model_provider in ~/.codex/config.toml.
  2. Confirm that a task created on the desktop uses the configured provider.
  3. Connect the official mobile app to the desktop using Codex Remote.
  4. From mobile, open an existing desktop-created task and send a message. It continues using the configured provider.
  5. From mobile, create a new task and send a message.
  6. Inspect the new task metadata and request route.

Expected behavior

A task created through mobile Remote should either:

  • inherit the connected host's effective model_provider; or
  • allow the user to select a provider before creating the task.

Actual behavior

The new mobile-created task uses model_provider=openai regardless of the host's configured provider. The mobile UI does not offer a provider selector.

This can make the task fail when the chosen model is not available through the built-in ChatGPT route, even though the same model and provider work for tasks created on the host.

Additional context

This appears related to #31370, which also reports mobile-created tasks being recorded with model_provider=openai. This report focuses specifically on provider selection/inheritance and the resulting request failure.

View original on GitHub ↗