Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Codex harness: project live tool calls as Control UI / WebChat tool cards [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#75641•Fetched 2026-05-02 05:32:26
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Author
ygc3817922006-sketchygc3817922006-sketch
Participants
clawsweeper[bot]clawsweeper[bot]ygc3817922006-sketchygc3817922006-sketch
Timeline (top)
commented ×1

When using the Codex harness (codex/* model refs) from Control UI / WebChat, tool execution appears to run correctly, but the UI does not show Codex-style live tool-call cards or tool progress. The user only sees assistant text updates and the final response, which makes long tool-using runs feel opaque compared with Codex App.

Error Message

  • A Codex harness run can perform tool work successfully.
  • The final assistant reply is delivered.
  • The chat surface does not expose the intermediate tool call lifecycle as cards, e.g. tool started, args, output/progress, success/failure.
  • Users must infer progress from assistant preambles or inspect logs/session history separately.

Root Cause

When using the Codex harness (codex/* model refs) from Control UI / WebChat, tool execution appears to run correctly, but the UI does not show Codex-style live tool-call cards or tool progress. The user only sees assistant text updates and the final response, which makes long tool-using runs feel opaque compared with Codex App.

RAW_BUFFERClick to expand / collapse

Summary

When using the Codex harness (codex/* model refs) from Control UI / WebChat, tool execution appears to run correctly, but the UI does not show Codex-style live tool-call cards or tool progress. The user only sees assistant text updates and the final response, which makes long tool-using runs feel opaque compared with Codex App.

Why this seems like an OpenClaw projection/parity gap

The public docs suggest the pieces should exist:

  • Control UI advertises Chat support for streaming responses with live tool-call output.
  • TUI docs say tool calls show as cards with args/results and partial updates stream into the same card, via agent tool events.
  • Codex Harness docs say OpenClaw still builds the tool list and receives dynamic tool results from the harness, while text/media/approvals/tool output continue through the normal OpenClaw delivery path.

However, in Control UI / WebChat with Codex harness, those dynamic tool events do not appear as visible tool cards/progress in the chat surface.

Observed behavior

  • A Codex harness run can perform tool work successfully.
  • The final assistant reply is delivered.
  • The chat surface does not expose the intermediate tool call lifecycle as cards, e.g. tool started, args, output/progress, success/failure.
  • Users must infer progress from assistant preambles or inspect logs/session history separately.

Expected behavior

For Codex harness runs, Control UI / WebChat should render the same kind of tool-call cards/progress that OpenClaw already exposes for native agent tool events, at least for OpenClaw gateway tools invoked through the harness.

A useful first version would be:

  • emit/render a tool-call start card with tool name and compact args;
  • stream or append tool output/progress into that card;
  • mark completion/failure;
  • preserve assistant text blocks before/between/after tools without duplication.

Implementation question

Is Codex harness currently dropping or not projecting native Codex/app-server tool lifecycle events into the standard OpenClaw agent event stream used by Control UI / WebChat?

If this is already intended to work, please document the required config/version flags. If it is not currently supported, this would be a useful Codex harness parity enhancement.

Related issues found before filing

  • #66251 tracks Codex harness stability work, but appears broader than this UI/event projection gap.
  • #71183 covered final assistant event rendering for Codex-provider runs, but not live tool-card parity.
  • #72341 covers text/tool/text duplicate rendering in WebChat / Control UI, which may be relevant to preserving text blocks around tool cards.
  • #59405 covers Telegram dropping tool output for a Codex model, potentially related but channel-specific.

extent analysis

TL;DR

The issue can be resolved by ensuring Codex harness projects native tool lifecycle events into the standard OpenClaw agent event stream used by Control UI / WebChat.

Guidance

  • Verify if Codex harness is currently dropping or not projecting native Codex/app-server tool lifecycle events into the standard OpenClaw agent event stream.
  • Check the configuration and version flags required for Codex harness to project tool lifecycle events into the OpenClaw agent event stream.
  • Investigate related issues (#66251, #71183, #72341, #59405) to see if they are relevant to the current problem.
  • Consider implementing a workaround to render tool-call cards/progress in the chat surface, such as emitting a tool-call start card with tool name and compact args, streaming or appending tool output/progress into that card, and marking completion/failure.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be related to a parity gap between Codex harness and OpenClaw, and resolving it may require changes to the Codex harness or the OpenClaw agent event stream.

Recommendation

Apply a workaround to render tool-call cards/progress in the chat surface, as the issue seems to be related to a missing feature in the Codex harness.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

For Codex harness runs, Control UI / WebChat should render the same kind of tool-call cards/progress that OpenClaw already exposes for native agent tool events, at least for OpenClaw gateway tools invoked through the harness.

A useful first version would be:

  • emit/render a tool-call start card with tool name and compact args;
  • stream or append tool output/progress into that card;
  • mark completion/failure;
  • preserve assistant text blocks before/between/after tools without duplication.
#indexing error#inference speed#output truncation#response parsing#generation error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Codex harness: project live tool calls as Control UI / WebChat tool cards [1 comments, 2 participants]