# Let cross-task messages respect the recipient chat’s Queue setting

**URL:** <https://community.openai.com/t/let-cross-task-messages-respect-the-recipient-chat-s-queue-setting/1401612>\
**Category:** Feature Requests\
**Tags:** codex-app\
**Created:** [September 28, 2026, 1:31pm UTC](https://community.openai.com/t/let-cross-task-messages-respect-the-recipient-chat-s-queue-setting/1401612 "2026-09-28T13:31:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thisis](https://avatars.discourse-cdn.com/v4/letter/t/f07891/32.png) [@thisis](https://community.openai.com/u/thisis)\
**Post date:** [September 28, 2026, 1:31pm UTC](https://community.openai.com/t/let-cross-task-messages-respect-the-recipient-chat-s-queue-setting/1401612/1 "2026-09-28T13:31:30Z")

</div>

### Feature request

I regularly use several Codex tasks at the same time and sometimes ask one task to send an update to another.

My default **Follow-up behavior** is set to **Queue**. However, when ChatGPT sends a message from another task to a chat that is already running, the message appears to be inserted directly into the active run instead of waiting for the next turn.

This makes cross-task coordination unpredictable. A status update or additional piece of context can redirect work that was already in progress, even though the recipient chat is configured to queue follow-ups.

#### Steps to reproduce

1. Set **Settings → General → Follow-up behavior** to **Queue**.
2. Start a task and let it continue working.
3. From another task, ask ChatGPT to send a message to the active task.
4. The message appears as **“Sent by ChatGPT from another task”** and is handled during the active run instead of waiting for a new turn.

#### Requested behavior

When a task receives a message from another task:

- Respect the recipient chat’s existing **Queue** or **Steer** preference.
- If **Queue** is selected, hold the message until the current run finishes.
- Show clearly that the incoming message is queued.
- Allow the sending task to explicitly request **Steer** when an interruption is intentional.

The recipient’s preference could remain the default, with Queue or Steer available as an optional override when sending the message.

If cross-task messages are already intended to respect this setting, this may be a bug rather than a new feature.

#### Why this would help

This would make multi-task workflows much safer. Tasks could exchange findings and status updates without unexpectedly changing each other’s active work.

#### Environment

- Component: ChatGPT/Codex desktop app
- App version: 26.924.22138, build 11645
- Bundled Codex command-line interface: 0.158.0-alpha.2.1
- Operating system: macOS 26.6.2
- Follow-up behavior: Queue

---

<div class="post-metadata">

**Author:** ![rjj1](https://avatars.discourse-cdn.com/v4/letter/r/ce73a5/32.png) [@rjj1](https://community.openai.com/u/rjj1)\
**Post date:** [September 29, 2026, 9:11am UTC](https://community.openai.com/t/let-cross-task-messages-respect-the-recipient-chat-s-queue-setting/1401612/2 "2026-09-29T09:11:27Z")

</div>

Your optional Steer override should require permission on the recipient side; without it, the message stays queued for the next turn.

---

<div class="post-metadata">

**Author:** ![thisis](https://avatars.discourse-cdn.com/v4/letter/t/f07891/32.png) [@thisis](https://community.openai.com/u/thisis)\
**Post date:** [September 29, 2026, 9:47am UTC](https://community.openai.com/t/let-cross-task-messages-respect-the-recipient-chat-s-queue-setting/1401612/3 "2026-09-29T09:47:06Z")

</div>

Yeah i agree, i like that approach, thats a better way to handle it. The recipient should remain in control, and without explicit permission, the message should stay queued for the next turn.