Bug type
Behavior bug (incorrect output/state without crash)
Summary
Summary:
When spawning a Codex ACP session via sessions_spawn({ runtime: "acp", agentId: "codex", streamTo: "parent" }), the parent session receives the started event and no output for 60s stall warnings, but never receives the completion event when the harness finishes.
The gateway log shows the full completion output (including build results, file changes, etc.), but the stream relay to the parent session stops after the stall warning. The parent has no way to know Neo finished without manually grepping the gateway log.
Config: permissionMode: approve-all, nonInteractivePermissions: deny
Version: OpenClaw 2026.3.24, acpx plugin, Codex agent
OS: macOS Tahoe
Impact: High — the orchestrating agent cannot manage coding sub-agents effectively without manual log monitoring. This is documented in the troubleshooting table ("ACP session stalls indefinitely after completing work") but no dedicated issue exists.
Steps to reproduce
Steps to reproduce:
- From a main Telegram session, call sessions_spawn({ runtime: "acp", agentId: "codex", mode: "run", streamTo: "parent", task: "..." })
- Codex completes the task (confirmed in gateway log)
- Parent session receives: Started codex session... then codex has produced no output for 60s... then nothing
- After 6 hours: codex stream relay timed out after 21600s without completion
Expected behavior
Expected: Parent session receives a completion event with Neo's final output/summary.
Actual behavior
Actual: Parent session never learns the task completed.
OpenClaw version
OpenClaw 2026.3.24, acpx plugin, Codex agent
Operating system
macOS 15.4 (Tahoe)
Install method
npm global
Model
Model: anthropic/claude-opus-4-6 (main session) + openai-codex/gpt-5.4 (ACP)
Provider / routing chain
openclaw -> acpx -> codex (ChatGPT Plus OAuth)
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Impact: High — the orchestrating agent cannot manage coding sub-agents effectively without manual log monitoring. This is documented in the troubleshooting table ("ACP session stalls indefinitely after completing work") but no dedicated issue exists.
Additional information
No response
Bug type
Behavior bug (incorrect output/state without crash)
Summary
Summary:
When spawning a Codex ACP session via sessions_spawn({ runtime: "acp", agentId: "codex", streamTo: "parent" }), the parent session receives the started event and no output for 60s stall warnings, but never receives the completion event when the harness finishes.
The gateway log shows the full completion output (including build results, file changes, etc.), but the stream relay to the parent session stops after the stall warning. The parent has no way to know Neo finished without manually grepping the gateway log.
Config: permissionMode: approve-all, nonInteractivePermissions: deny
Version: OpenClaw 2026.3.24, acpx plugin, Codex agent
OS: macOS Tahoe
Impact: High — the orchestrating agent cannot manage coding sub-agents effectively without manual log monitoring. This is documented in the troubleshooting table ("ACP session stalls indefinitely after completing work") but no dedicated issue exists.
Steps to reproduce
Steps to reproduce:
Expected behavior
Expected: Parent session receives a completion event with Neo's final output/summary.
Actual behavior
Actual: Parent session never learns the task completed.
OpenClaw version
OpenClaw 2026.3.24, acpx plugin, Codex agent
Operating system
macOS 15.4 (Tahoe)
Install method
npm global
Model
Model: anthropic/claude-opus-4-6 (main session) + openai-codex/gpt-5.4 (ACP)
Provider / routing chain
openclaw -> acpx -> codex (ChatGPT Plus OAuth)
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Impact: High — the orchestrating agent cannot manage coding sub-agents effectively without manual log monitoring. This is documented in the troubleshooting table ("ACP session stalls indefinitely after completing work") but no dedicated issue exists.
Additional information
No response