ChatGPT iOS-created Codex threads do not expose automation_update and have inconsistent Computer Use behavior

Open 💬 2 comments Opened Jul 8, 2026 by ludicarchitect

💡 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)?

26.623.141536

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Mac

What issue are you seeing?

Codex threads created from ChatGPT iOS remote control do not expose or reliably enable the same Codex desktop tools as threads created directly in the Codex Mac app.

Observed issue 1: automations missing

A thread created directly from the Codex Mac app exposes automation_update and supports kind: "heartbeat" same-thread scheduled messages.
Threads created from ChatGPT iOS do not expose automation_update.
The iOS-created threads can see some Codex thread tools, like fork/send-message, and unrelated connector tools, but not Codex automation tools.

Observed issue 2: Computer Use missing or degraded

An iOS-created thread asked to use Computer Use to inspect the macOS Messages app: 019f42ba-206d-75d1-967a-6ebae3769b55.
That thread did not successfully use Computer Use to complete the task.
A comparable thread created directly in the Codex Mac app was able to expose and use Computer Use successfully: 019f42bd-375a-7780-a106-c3bfea42e38a.
In the Mac-created thread, Computer Use successfully listed apps, inspected Messages, clicked UI elements, and read the latest received message.
In the iOS-created thread, Computer Use/tool access appeared inconsistent or restricted and the task could not be completed.

What steps can reproduce the bug?

Feedback ID: 019f42bd-83e7-7c01-bcd1-0b1fc9a36180

What is the expected behavior?

Threads created from ChatGPT iOS remote control should expose and use the same Codex desktop tools as threads created directly in the Mac Codex app, including:

automation_update for same-thread heartbeat automations
Computer Use tools for local macOS app inspection/control

Additional information

Impact: Mobile-created Codex sessions are missing or failing important desktop Codex functionality. I cannot create or inspect scheduled messages/heartbeat automations from iOS-created threads, and Computer Use behavior differs from equivalent Mac-created threads.

Codex app version observed in local config/runtime paths: 26.623.141536.
Local config now includes approval_policy=never, sandbox_mode=danger-full-access, and [features].enable_mcp_apps=true.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

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

#30380
#30623
#30905

Powered by Codex Action

elilevy28 · 17 days ago

Independent reproduction on 2026-08-11:

A Codex task initiated from iOS Mobile Remote and executed against a Mac desktop host inherits the host context successfully, including:

repository/worktree
shell access
host credentials
local/project skills

However, the task does not receive the host's scheduled-task/automation capability: automation_update is absent from the tool manifest. The same Mac host exposes working scheduled-task support to tasks initiated directly in the Codex desktop app.

Practical impact: the iOS-initiated task cannot create an in-chat 30-minute monitoring schedule even though its execution host supports automations.

This mixed result suggests capability negotiation may be keyed to the initiating surface (iOS Mobile Remote) instead of, or before intersecting correctly with, the execution host's capabilities. Expected behavior is that a remote task inherits the execution host's available capabilities, subject to the same account/workspace permissions and approval policy.

Suggested investigation: compare the dynamic tool/capability manifest negotiation for a desktop-initiated task versus an iOS-initiated task targeting the same host, especially registration/injection of automation_update.