Repository navigation
ChatGPT iOS hides direct-thread delegation bodies, preventing audit of create_thread and send_message_to_thread #41964
Description
Summary
In ChatGPT for iOS 1.2026.230, the UI no longer exposes the exact content delivered by the direct thread-management tools create_thread and send_message_to_thread.
A controller can create or wake another task, but in the iOS client cannot inspect the exact task prompt/message that the target received. This removes a necessary audit boundary: a user may authorize a task with requirements A/B/C, but cannot verify that the delegated input did not acquire unintended extra requirements or context before execution.
The same tasks are displayed correctly in the Mac ChatGPT Desktop app: the cross-thread message body is visible there. This appears to be an iOS presentation regression, not a delivery failure or a Mac Desktop regression.
Reproduction
- In a task, call
create_threadwith an initial task prompt, or callsend_message_to_threadfor an existing task. - Open the target task in ChatGPT for iOS
1.2026.230and inspect its first or resumed turn. - Observe that the received delegation is not presented as a readable, inspectable message.
- Open the same task in the Mac ChatGPT Desktop app and observe that the message body is displayed.
Observed behavior
- The direct-thread delivery starts or resumes the target task.
- In ChatGPT for iOS, neither the sender nor the target has a durable, readable UI record of the exact delivered body.
- Mac ChatGPT Desktop displays the same cross-thread message body normally.
Expected behavior
For both create_thread and send_message_to_thread, ChatGPT for iOS should display a durable audit record containing:
- the exact delivered prompt/input;
- the source and destination task/thread;
- delivery time and, if available, the resulting target turn/message ID; and
- a clear visual distinction between a cross-thread delegation and normal user input.
The record should be visible in both the sender and target task, matching the Mac Desktop client.
Why this matters
Cross-thread delegation is representational: the receiving task may act immediately. Hiding the body prevents users from verifying task scope, detecting unintended model-added instructions, reviewing accidental context leakage, or confirming that the receiving task matches what they authorized.
Environment
- Affected: ChatGPT for iOS
1.2026.230 - Working comparison: Mac ChatGPT Desktop
26.825.51511(build7377), macOS26.6.1(build25G76), Apple Silicon (arm64). The message body is visible for the same task. - Local direct-thread delegation via
create_threadandsend_message_to_thread
Related but distinct reports
- send_message_to_thread reports handler error even when delegation is delivered #29886: delivery-result ambiguity for
send_message_to_thread - send_message_to_thread omits the target turn ID, preventing exact completion correlation #40397: no target turn ID returned by
send_message_to_thread
Activity
github-actions commentedon Sep 1, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
[-]Codex Desktop hides direct-thread delegation bodies, preventing audit of create_thread and send_message_to_thread[/-][+]ChatGPT iOS hides direct-thread delegation bodies, preventing audit of create_thread and send_message_to_thread[/+]