Cross-chat task relays need explicit consent and a mute control

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

Unknown — not available in this session

What subscription do you have?

Unknown — please update if needed

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Cross-chat task messages can be sent and their replies automatically surfaced in the current Codex chat as “Sent by Codex from another chat.”

This is a serious consent and control problem when the target task has active, uncommitted work. The relayed messages can redirect or stop work without a clear per-message confirmation, and there is no clear way to mute relay cards independently of stopping the task.

In this incident, Codex also produced the contradictory statement “Ignore those long messages. They didn't come from me,” while the UI visibly identified the messages as sent by Codex from another chat.

What steps can reproduce the bug?

1. Open a coordinating Codex chat and multiple existing Codex tasks.
2. Ask the coordinating chat to communicate with or check another task.
3. A cross-chat instruction is sent to the target task.
4. The target task's reply appears in the coordinator as “Sent by Codex from another chat.”
5. Continue speaking or working away from the screen; the incoming relay can alter the task direction or produce noisy status messages without a distinct consent boundary.

What is the expected behavior?

Codex should require explicit confirmation before every outbound cross-chat message, showing the target task and exact text. Incoming task replies should be muted by default or controlled independently from task execution. The UI should clearly distinguish an incoming result, a proposed outbound message, and an action that changes task/worktree state.

Additional information

Requested controls:

• Per-message cross-chat confirmation
• Per-task “mute relay” without stopping the task
• A quiet coordinator mode that never contacts or summarizes other tasks unless explicitly instructed
• An outbound-message audit log (target, exact text, timestamp, reason)
• Clear warnings when a message may affect uncommitted work

Impact: this makes multi-task development unsafe and hard to supervise; it can change active work while the user is away and makes it difficult to establish which task caused a change.