ChatGPT iOS hides direct-thread delegation bodies, preventing audit of create_thread and send_message_to_thread

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

1. In a task, call create_thread with an initial task prompt, or call send_message_to_thread for an existing task.
2. Open the target task in ChatGPT for iOS 1.2026.230 and inspect its first or resumed turn.
3. Observe that the received delegation is not presented as a readable, inspectable message.
4. 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 (build 7377), macOS 26.6.1 (build 25G76), Apple Silicon (arm64). The message body is visible for the same task.
• Local direct-thread delegation via create_thread and send_message_to_thread

Related but distinct reports

• #29886: delivery-result ambiguity for send_message_to_thread
• #40397: no target turn ID returned by send_message_to_thread

Start by reproducing create_thread and send_message_to_thread on ChatGPT for iOS 1.2026.230, then compare the target task with the Mac ChatGPT Desktop behavior. Trace where the direct-thread delegation is rendered on both sender and target; done means the exact body, source and destination, delivery time, and available target message ID are durably visible and visually distinct from normal input.