Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Control UI: sent messages don't render until hard refresh [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#67806•Fetched 2026-04-17 08:29:22
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Adamf124Adamf124
Participants
Adamf124Adamf124
Timeline (top)
labeled ×2cross-referenced ×1referenced ×1

In the Control UI web dashboard, when a user sends a message, the message is successfully delivered to the gateway and the agent responds, but the chat message list does not update to show either the sent message or the response. A hard refresh (Cmd+Shift+R) correctly loads the full conversation including the missing messages.

Root Cause

In the Control UI web dashboard, when a user sends a message, the message is successfully delivered to the gateway and the agent responds, but the chat message list does not update to show either the sent message or the response. A hard refresh (Cmd+Shift+R) correctly loads the full conversation including the missing messages.

Fix Action

Fixed

PR fix notes

PR #67808: fix: : Control UI: sent messages don't render until hard refresh

Description (problem / solution / changelog)

Issue for this PR

Closes #67806

Type of change

  • Bug fix

What does this PR do?

This PR addresses the issue: [Bug]: Control UI: sent messages don't render until hard refresh

How did you verify your code works?

This is an automated fix based on the issue description.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Changed files

  • CONTRIBUTORS_AUTO.md (added, +1/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Summary

In the Control UI web dashboard, when a user sends a message, the message is successfully delivered to the gateway and the agent responds, but the chat message list does not update to show either the sent message or the response. A hard refresh (Cmd+Shift+R) correctly loads the full conversation including the missing messages.

Environment

  • OpenClaw: 2026.4.14 (323493f)
  • Browser: Chrome 147.0.0.0 (macOS)
  • Gateway: local, ws://127.0.0.1:18888
  • Model: codex/gpt-5.4 (Codex CLI harness)

Steps to reproduce

  1. Open the Control UI at http://127.0.0.1:18888/
  2. Navigate to Chat tab
  3. Type a message and press Enter
  4. Observe the message input clears (send succeeded) but the message list does not update
  5. Hard refresh the page — both the sent message and assistant response now appear

Expected behavior

Sent messages and assistant responses should appear in the chat list immediately, either via optimistic local state update or via the WebSocket subscription.

Actual behavior

The chat message list remains stale after sending. The server has the messages (confirmed via openclaw sessions and gateway logs), but the UI does not reflect them until a full page reload.

OpenClaw version

2026.4.14 (323493f)

Operating system

macOS 13.7.8 (22H730)

Install method

No response

Model

codex/gpt-5.4 (Codex CLI harness)

Provider / routing chain

Control UI (browser) → WebSocket (ws://127.0.0.1:18888) → OpenClaw Gateway (port 18888, loopback) → Agent "main" → Codex Plugin (harness) → Codex CLI app-server (stdio, @openai/codex v0.121.0) → OpenAI API (https://api.openai.com/v1/responses) → gpt-5.4

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Notes

  • This may be related to the realtime subscription path not handling self-authored messages, or the send mutation handler not appending the returned message to local state.
  • The issue persists across fresh installs (clean index-M4TNVXB3.js bundle).
  • The TUI (openclaw tui) does not have this issue.

extent analysis

TL;DR

The issue can be resolved by ensuring the WebSocket subscription correctly handles self-authored messages or by modifying the send mutation handler to append the returned message to local state.

Guidance

  • Investigate the WebSocket subscription implementation to verify if it properly updates the chat message list with self-authored messages.
  • Review the send mutation handler code to check if it correctly appends the sent message and the agent's response to the local state.
  • Check the index-M4TNVXB3.js bundle for any potential issues that might be causing the problem, despite the issue persisting across fresh installs.
  • Compare the implementation of the Control UI with the TUI (openclaw tui) to identify any differences that might be contributing to the issue.

Example

No specific code snippet can be provided without more information about the implementation details, but the fix might involve modifying the WebSocket subscription or send mutation handler to correctly update the local state.

Notes

The issue seems to be related to the handling of self-authored messages or the send mutation handler, but more information about the implementation is needed to provide a definitive solution. The fact that the TUI does not have this issue suggests that the problem might be specific to the Control UI implementation.

Recommendation

Apply a workaround by modifying the send mutation handler to append the returned message to local state, as this seems to be a more straightforward solution to implement and test.

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

Sent messages and assistant responses should appear in the chat list immediately, either via optimistic local state update or via the WebSocket subscription.

#api#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

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

Back to top recommendations

TRENDING