openai / openai/codex

ChatGPT iOS Remote does not display the input prompt delivered by a scheduled automation

Open
#44,977 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

automations bug iOS remote
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Environment

  • Host: macOS 26.6.2, Apple Silicon; ChatGPT Pro.
  • Desktop build used for the diagnostic inspection below: 26.903.71938 (build 8576), bundled codex-cli/app-server 0.153.4.
  • The host has since updated to Desktop 26.908.40834 (build 8881). No separate version-pinned iOS reproduction has been performed after that desktop update.
  • Client: ChatGPT for iOS, using Codex Remote. Exact installed iOS app version/build has not yet been recorded.
  • Observation date: September 12, 2026.
  • Affected scheduling mode (same-thread heartbeat or standalone scheduled run): not captured.

What issue are you seeing?

When I open an affected task in ChatGPT iOS Remote, the input prompt delivered by the scheduler is not displayed in the conversation. I cannot inspect the instructions that initiated the automation turn.

Cross-task messages delivered by send_message_to_thread now appear readable in my usage after a recent iOS update. That agrees with the iOS 1.2026.244 release notes about restoring delegated-task messages. The scheduler-originated input remains missing in my observation.

Steps to reproduce

  1. Let a scheduled Codex automation trigger on the desktop host.
  2. Open the affected task through ChatGPT iOS Remote.
  3. Inspect the turn initiated by the scheduler.
  4. Observe that its initiating instruction body is not presented as a readable message.

Expected behavior

Display the scheduler-delivered instructions with their automation provenance, so the user can review the input that caused the turn to run. Preserve the distinction from manually authored user messages.

Diagnostic context and limits

Read-only inspection of the desktop build above shows that its automation runner delivers inputs as toolOutput with namespace codex_app and name automation_update. Same-thread heartbeat inputs use a <heartbeat> envelope, while cross-task delegation uses <codex_delegation>.

This confirms a different desktop input representation; it does not establish the iOS rendering cause. The affected scheduling mode and mobile build were not captured. This report does not claim that both standalone and same-thread schedules have been separately reproduced.

Related reports have different scopes:

  • #41964: my earlier report of missing direct-thread delegation bodies.
  • #41995: desktop heartbeat assistant results disappearing after reload or pagination.
  • #32614 and #44133: tasks missing from discovery/listing.

The symptom reported here is the missing scheduler-originated input inside an opened iOS task.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified. First reproduce the issue with the exact iOS build and scheduling mode recorded, then compare how the codex_app automation_update toolOutput is rendered against readable send_message_to_thread messages. Done means the scheduler-delivered instructions appear in iOS Remote with automation provenance while remaining distinct from authored user messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, rust
Domain
backend-api-design, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.