openclaw - 💡(How to fix) Fix Codex command executions lose streamed output when aggregatedOutput is empty [1 pull requests]

Summary

OpenClaw's Codex app-server event projector currently uses commandExecution.aggregatedOutput as the only output source for final command tool results. Some Codex command runs emit stdout through item/commandExecution/outputDelta, but the final commandExecution snapshot can still have aggregatedOutput: null or an empty value.

When that happens, OpenClaw records a completed bash tool result with no output. In the UI this can look like the run is stuck at Tool: bash or like it completed successfully with No output, even though stdout was streamed earlier.

Reproduction shape

1. Run a Codex-backed OpenClaw session.
2. Execute a command that emits stdout through item/commandExecution/outputDelta.
3. Have the final commandExecution item arrive with aggregatedOutput: null.
4. Build the final transcript/result snapshot.

Actual behavior

The final command tool result/transcript output is empty because OpenClaw only reads aggregatedOutput for commandExecution items.

Expected behavior

OpenClaw should preserve streamed outputDelta text and use it as a fallback final output when aggregatedOutput is missing or empty.

Impact

The user and subsequent agent context can lose the actual command output. This makes successful commands look empty and can make the UI appear stuck around Tool: bash, especially for commands whose useful result is printed to stdout.

Version check

I checked the current published stable package, the current npm beta, and upstream main; the issue still appears to be present in all of them.

Related work

#70966 improved verbose Codex tool logs, but it does not cover the final transcript/result fallback when aggregatedOutput is empty.