[Bug]: Orchestration works with omp but stalls when worker is Codex

[AmethystLiang]

Operating system

Other

Orca version

Unknown

Details

Short summary: Orca orchestration progresses when the worker agent is omp, but stalls when the worker is Codex.

What happened?
Orchestration with an omp worker continues successfully; the same (or similar) flow with a Codex worker gets stuck and cannot continue.

Steps to reproduce

1. Run an orchestration flow with an omp worker — completes / continues.
2. Run a similar flow with a Codex worker.
3. Observe stall / inability to continue.

Expected behavior
Orchestration should progress for Codex workers similarly to omp (dispatch, inject, wait for completion).

Actual behavior
Codex worker path stalls; omp path works.

Additional context
Possibly related:

• [Bug]: dispatch --inject to Codex never submits large payloads — trailing Enter is concatenated into the bracketed-paste PTY write (v1.4.159) #11343 — dispatch --inject to Codex never submits large payloads (Enter concatenated into paste)
• [Bug]: Orchestration push-on-idle delivery still clobbers in-progress user input, and auto-submits it when no coordinator run is registered (v1.4.159) #11242 — orchestration push-on-idle / auto-submit issues
• [Bug]: orchestration dispatch --inject silently answers Codex's directory-trust prompt and swallows the task #10666 — inject swallows Codex directory-trust prompt

If this is a duplicate of the inject/Enter path, close as duplicate and link the root cause.

Please comment with: Orca version, OS, orchestration skill/version, and where it stalls (before dispatch / after inject / waiting forever).