Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feature]: broadcast inbound user messages as WebSocket events

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…

Gateway WebSocket events only broadcast assistant responses — inbound user messages from chat.send are not broadcast to other connected clients.

Error Message

only receives the assistant's response (delta/final/error) but has no way to know what question triggered it.

  • No breaking changes — existing clients that only handle delta/final/error states will simply ignore the new user state

Root Cause

Gateway WebSocket events only broadcast assistant responses — inbound user messages from chat.send are not broadcast to other connected clients.

Code Example

{
    "event": "chat",
    "payload": {
      "runId": "abc123",
      "sessionKey": "agent:main:main",
      "state": "user",
      "message": {
        "role": "user",
        "content": [{ "type": "text", "text": "Hello, what can you do?" }],
        "timestamp": 1741784981000
      },
      "sender": { "id": "cli", "displayName": "..." }
    }
  }

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