›_ Codex Issues
Codex Issues / #32553

Codex Remote on Android omits codex_app tools in mobile-created tasks and hangs them in desktop-created tasks

Open 💬 4 comments Opened Jul 12, 2026 by findolor
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Current build available on 2026-07-12 (exact version unavailable while reporting remotely)

What subscription do you have?

Not provided

What platform is your computer?

macOS (Apple Silicon), controlled through ChatGPT mobile on Android and iOS

What issue are you seeing?

Codex Remote on Android has two different failure modes for codex_app thread-management tools, depending on where the task was created.

1. Task created in the Codex desktop app, then opened from Android

The thread-management tools are present in the agent's tool manifest, including codex_app.list_threads. However, calls hang indefinitely and return no data. We reproduced this with list_threads({ limit: 3 }), waited 60–90 seconds, and had to terminate the call.

Ordinary conversation continues to work in the same task.

When the same desktop-created task and connected host are controlled from iOS, the identical list_threads call completes successfully.

2. Task created from ChatGPT mobile on Android

The codex_app thread-management tools do not exist in the agent's tool manifest at all. This matches the behavior described in #26907.

Together, these suggest that Android Codex Remote handles both the dynamic tool manifest and tool-call result delivery differently from iOS.

Related: #26907

What steps can reproduce the bug?

A. Tools are available but hang
  1. Create a task directly in the Codex desktop app on macOS.
  2. Pair an Android device with that Codex host.
  3. Open the desktop-created task through ChatGPT on Android.
  4. Confirm that codex_app.list_threads is available.
  5. Ask Codex to call list_threads({ limit: 3 }).
  6. Observe that the call remains running for 60+ seconds and returns no data.
  7. Open the same host and task through ChatGPT on iOS.
  8. Run the same call and observe that it completes successfully.
B. Tools are missing
  1. From ChatGPT on Android, create a new Codex task on the connected host.
  2. Inspect the tools available to the agent.
  3. Observe that codex_app thread-management tools such as create_thread, list_threads, read_thread, and set_thread_title are absent.

Affected desktop-created task/thread ID observed during testing:

019f55a8-30aa-7f23-b362-acc51be73886

What is the expected behavior?

Android-created and desktop-created tasks opened through Android Remote should receive the same appropriate codex_app tool manifest as equivalent local/iOS tasks, and available tool calls should complete normally.

Additional information

  • Reproduced the hanging call multiple times from Android.
  • Reducing list_threads to three results did not help.
  • Normal messages continue working through Android.
  • The same tool, host, and desktop-created task work through iOS.
  • No repository or Git operation is involved.
  • Approximate reproduction date: 2026-07-12, Europe/Istanbul timezone.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #31366
  • #31584

Powered by Codex Action

venkatd · 1 month ago

Wanted to mention that I also have a problem where I'm not able to use thread tools on Android. I believe it's a similar issue to what was reported. Happy to share more details to help debug.

ginishuh · 24 days ago

Fresh reproduction on 2026-08-04: this is still affecting the Android Remote path.

Environment available from the connected host:

  • Codex CLI: 0.146.0
  • App-server daemon: managed and running, appServerVersion=0.146.0
  • Mobile client: ChatGPT on Android (exact mobile build unavailable while reporting remotely)

User-visible result reproduced again:

  1. The thread-management tool is exposed to the Android-controlled task, but invoking it fails.
  2. As a result, the Android workflow still cannot create a new persistent Codex task.
  3. Cross-thread control/communication also fails because the required thread-management calls for listing, reading, or sending a message to another task do not complete successfully.
  4. The host app-server is running normally, so this is not explained by the host daemon being offline.

This occurrence is therefore specifically a tool-call failure, not a missing-tool-manifest observation and not merely an indefinite wait. The exact returned error string was not captured for this comment, so I am not inferring a lower-level cause.

This confirms that the core Android outcome reported here remains present on a newer 0.146.0 host. A Desktop-created controller task remains only a partial workaround, not a fix, because Android-side thread-tool execution is still not reliable.

ropepop · 17 days ago

Same family of issue here on the custom-model side: macOS host with a custom provider. Desktop-created threads opened from Android remote show the tool-manifest divergence described here, and the reasoning/tool-call middle section from desktop is not rendered on remote. The thread-management tool gaps in #26907 and the rendering gaps in #37598/#32185 look like the same root cause: the remote path does not faithfully carry the local session's tool manifest and item rendering. Worth treating these as one remote-parity bug family.