Repository navigation
[Feature] Ability to have “steer” be the default for cross-agent messages? #28960
Description
via Discord
Is there a way to make it so that when agents message each other, they’re sent as a “steer” by default? (instead of a queue). I’m finding that I can end up with 10+ messages queued up in an agent but by the time the agent gets to them they’re no longer relevant or timely.
Not sure if this is an issue with all models or just codex I know within the codex app itself you can choose whether the default is “steer” or “queue” — wasn’t sure if that’s something to put in the skill itself or as a setting that the skill reads from.
Activity
orca-discord-issues commentedon Oct 15, 2026
via Discordnwparker commentedon Oct 22, 2026
Closing as completed by merged #28540: orchestration mail notices to native-chat agents now use immediate delivery by default, so they no longer accumulate as queued cards waiting for the whole turn to end.
This matches the notices in your screenshot. The current host sends them through the same plain-send path as a person's mid-turn message. Codex, Claude and Pi take the message into the running turn at their next supported step; ACP agents handle it as their normal immediate send. Mail is deliberately held while a human approval or question is open, then delivered after the answer. Terminal-agent delivery keeps its existing behavior.
Verified the current host/send paths and re-ran the coordinator-mail, dispatch-worker-mail, host/send and ACP approval-admission tests: 49 tests passed across five suites, including Codex
turn/steerduring a running turn, no queued card, and preservation of an open question. The merged PR also records hidden-app validation with real Codex and Grok sessions.Update the Orca host that runs the chat to receive this behavior; an older paired server retains its older delivery policy.