openclaw - ✅(Solved) Fix Control UI: tool call result payload missing from expanded block [1 pull requests, 1 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#70746Fetched 2026-04-24 05:54:07
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
cross-referenced ×1

When expanding a tool call block in the Control UI chat view, the tool name and inputs are visible but the result payload is not displayed — the expanded block is empty.

Root Cause

When expanding a tool call block in the Control UI chat view, the tool name and inputs are visible but the result payload is not displayed — the expanded block is empty.

Fix Action

Fixed

PR fix notes

PR #70789: fix(ui): fix tool result pairing for sequential same-name tool calls

Description (problem / solution / changelog)

Summary

Fixes #70746 - tool call result missing from expanded block in Control UI.

Root Cause

findLatestCard iterated in reverse (newest first). When multiple tool calls shared the same name (e.g. two read calls in sequence), the first result incorrectly paired with the second call (found first in reverse iteration), and the second result had no card to attach to - creating a standalone result card that doesn't render in the expanded tool call UI.

Fix

Renamed findLatestCardfindFirstUnmatchedCard and iterate forward (oldest first). Now sequential same-name calls pair with their results in correct order:

  • result 1 → call 1
  • result 2 → call 2
  • result 3 → call 3

Changes

  • ui/src/ui/chat/tool-cards.ts - Changed iteration direction in findLatestCard (now findFirstUnmatchedCard) and updated the call site

Testing

  • Added test case with multiple sequential tool calls of the same name to verify correct result pairing

Changed files

  • ui/src/ui/chat/tool-cards.ts (modified, +13/-5)
RAW_BUFFERClick to expand / collapse

Description

When expanding a tool call block in the Control UI chat view, the tool name and inputs are visible but the result payload is not displayed — the expanded block is empty.

Steps to Reproduce

  1. Open the Control UI chat at http://127.0.0.1:19178
  2. Trigger any tool call (e.g. a Read file operation)
  3. Click the collapsed Tool call → block to expand it
  4. Observe: tool name and file path inputs are shown, but no output/result content is rendered

Expected Behavior

Expanded tool call block should show both inputs and the result payload returned by the tool.

Actual Behavior

Result payload is missing. Only the tool name and inputs render. The conversation continues correctly (gateway has the output), so this is purely a frontend rendering issue.

Environment

  • OpenClaw version: 2026.4.22 (00bd2cf)
  • OS: macOS 26.4.1 (Apple Silicon)
  • Install method: pnpm
  • Channel: stable

Additional Context

Confirmed working in openclaw chat (terminal TUI) — full tool outputs display correctly there. Issue is isolated to the Control UI web frontend.

extent analysis

TL;DR

The issue is likely due to a frontend rendering problem in the Control UI web frontend, and verifying the result payload data in the backend or checking the frontend code for rendering issues may help resolve the problem.

Guidance

  • Verify that the result payload is being received correctly by the frontend by checking the network requests or the backend logs.
  • Inspect the frontend code responsible for rendering the expanded tool call block to ensure it is correctly handling the result payload data.
  • Compare the rendering code with the openclaw chat terminal TUI implementation to identify any differences.
  • Check for any browser console errors or warnings that may indicate a JavaScript issue preventing the result payload from being rendered.

Example

No code example is provided as the issue does not include specific code details.

Notes

The issue seems to be isolated to the Control UI web frontend, and the fact that it works in the openclaw chat terminal TUI suggests a potential difference in how the result payload is handled or rendered between the two interfaces.

Recommendation

Apply a workaround by inspecting the network requests or backend logs to verify the result payload data, and then investigate the frontend code to identify and fix the rendering issue, as upgrading to a fixed version is not clearly implied in the provided information.

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…

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 - ✅(Solved) Fix Control UI: tool call result payload missing from expanded block [1 pull requests, 1 participants]