Mobile-created Remote root threads can receive a reduced task-management tool profile

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

ChatGPT desktop app powered by Codex & OWL, version 26.715.31925, released July 18, 2026; bundled Codex CLI not detected in PATH by the local collector.

What subscription do you have?

Originally reproduced under ChatGPT Max and reproduced again under the current ChatGPT Pro subscription.

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64; mobile client: ChatGPT 1.2026.188 on Android 16

What issue are you seeing?

A brand-new root thread created through the ChatGPT Android Remote UI received a smaller task-management tool profile than equivalent threads on the same connected desktop host, ChatGPT account, and local project.

The affected mobile-created root thread reported 128 available tools and did not include the native codex_app__set_thread_title capability. By contrast:

• An existing desktop-created thread controlled from mobile could use the native rename capability successfully.
• Delegated child threads created from a full-profile parent, including a child in the same local project, received codex_app__set_thread_title and successfully renamed themselves.

The tested difference was not explained by the selected project, by controlling an existing desktop-created thread from mobile, or by creating a delegated child inside versus outside the project.

This is an observed capability-profile difference. It does not claim a confirmed root cause.

What steps can reproduce the bug?

1. Connect ChatGPT 1.2026.188 on Android 16 to the Windows desktop host through Remote.
2. From the mobile Remote UI, create a brand-new root thread in a local project.
3. Inspect the thread's available tool registry and attempt to rename the thread using the native task-management capability.
4. Observe that the tested root thread reports 128 tools and does not include codex_app__set_thread_title.
5. From an existing full-profile parent on the same host and in the same local project, create a delegated child thread.
6. Inspect the child's tools and attempt the same native rename.
7. Observe that the delegated child includes codex_app__set_thread_title and the rename succeeds.
8. As a control, open an existing desktop-created thread from mobile and observe that its native rename also succeeds.

What is the expected behavior?

For the same connected host, ChatGPT account, and local project, a new mobile-created Remote root thread should receive the same supported task-management capability profile as an equivalent desktop-created or delegated thread.

If the reduced profile is intentional, the product should clearly disclose that limitation when the thread is created.

Additional information

Please confirm whether the creation path of a mobile Remote root thread is expected to affect the task-management tool profile. If not, please investigate why the native rename capability is omitted from the mobile-created root thread while delegated children retain it.

Related issues reviewed:

• #22773 covers broader mobile Remote state, hydration, and control-surface failures, not this creation-path tool-profile difference.
• #23527 covers mobile visibility of SSH remote projects, not task-tool injection for a root thread.
• #23699 covers capability loss after an SSH restart path, which is a different trigger.

No session or thread ID is included in this public report. No screenshot, JSON, log, hostname, account identifier, local path, project name, repository name, credential, or network information will be attached. A session identifier can be provided later through a private support channel if maintainers require it.