Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Real-time message & task status desync between Local Dashboard and Feishu Bot [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#53786•Fetched 2026-04-08 01:23:24
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
JoeDu-12JoeDu-12
Participants
JoeDu-12JoeDu-12zelixagzelixag
Timeline (top)
labeled ×2commented ×1

Chat messages and task status don't sync in real time between my local OpenClaw dashboard and the Feishu bot channel.

Root Cause

Chat messages and task status don't sync in real time between my local OpenClaw dashboard and the Feishu bot channel.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

Chat messages and task status don't sync in real time between my local OpenClaw dashboard and the Feishu bot channel.

Steps to reproduce

  1. Set up and enable the Feishu integration in OpenClaw.
  2. Open the local OpenClaw web dashboard in my browser.
  3. Send a message to the bot from the Feishu app.
  4. Notice: The new message never shows up in the local dashboard.
  5. Send a message from the local dashboard to the bot.
  6. Notice: The Feishu side either gets no reply or a very delayed one.

Expected behavior

I expect all messages and task status changes to show up instantly on both the local dashboard and Feishu, just like they do in normal chat apps. Both sides should have the exact same conversation history at all times.

Actual behavior

Messages sent from Feishu don't appear in my local dashboard at all. Messages I send from the dashboard either don't show up in Feishu or come through much later. The conversation history looks totally different on each end, so I can't keep track of context properly.

OpenClaw version

2026.3.13

Operating system

Windows 11

Install method

pnpm dev (local self-hosted, connects to cloud LLM models)

Model

glm-4.7-flash

Provider / routing chain

openclaw -> zhipuai -> glm-4-7-flash

Additional provider/model setup details

Local OpenClaw instance routes all LLM requests to ZhipuAI's cloud model glm-4-7-flash, no local model used.

Logs, screenshots, and evidence

Impact and severity

Affected users/systems: Local OpenClaw instance with Feishu (Lark) channel Severity: Annoying (blocks real-time chat sync between dashboard and Feishu) Frequency: Always (happens every time I test message sending) Consequence: Can't maintain consistent conversation context across both ends

Additional information

No response

extent analysis

Fix Plan

To resolve the real-time chat sync issue between the local OpenClaw dashboard and the Feishu bot channel, we need to implement a WebSocket-based solution for bidirectional communication.

  • Step 1: Establish WebSocket Connection
    • Set up a WebSocket connection between the local OpenClaw dashboard and the Feishu bot channel.
    • Use a library like ws in Node.js to create a WebSocket server and client.
  • Step 2: Handle Incoming Messages
    • On the OpenClaw dashboard side, handle incoming messages from the Feishu bot channel using the WebSocket connection.
    • Update the conversation history in real-time when a new message is received.
  • Step 3: Handle Outgoing Messages
    • On the OpenClaw dashboard side, handle outgoing messages to the Feishu bot channel using the WebSocket connection.
    • Send the message to the Feishu bot channel and update the conversation history in real-time.

Example Code

// OpenClaw dashboard side (using Node.js and ws library)
const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 8080 });

wss.on('connection', (ws) => {
  console.log('Client connected');

  // Handle incoming messages from Feishu bot channel
  ws.on('message', (message) => {
    console.log(`Received message: ${message}`);
    // Update conversation history in real-time
    updateConversationHistory(message);
  });

  // Handle outgoing messages to Feishu bot channel
  ws.on('send', (message) => {
    console.log(`Sending message: ${message}`);
    // Send message to Feishu bot channel
    ws.send(message);
    // Update conversation history in real-time
    updateConversationHistory(message);
  });
});

// Feishu bot channel side (using WebSocket client library)
const WebSocket = require('ws');
const ws = new WebSocket('ws://openclaw-dashboard:8080');

ws.on('open', () => {
  console.log('Connected to OpenClaw dashboard');
  // Send message to OpenClaw dashboard
  ws.send('Hello from Feishu bot channel!');
});

ws.on('message', (message) => {
  console.log(`Received message: ${message}`);
  // Update conversation history in real-time
  updateConversationHistory(message);
});

Verification

To verify that the fix worked, test the real-time chat sync between the local OpenClaw dashboard and the Feishu bot channel by sending messages from both sides and checking that the conversation history is updated in real-time on both ends.

Extra Tips

  • Make sure to handle errors and disconnections properly to ensure a robust WebSocket connection.
  • Consider implementing a message queue to handle messages that are sent while the WebSocket connection is offline.
  • Use a

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

I expect all messages and task status changes to show up instantly on both the local dashboard and Feishu, just like they do in normal chat apps. Both sides should have the exact same conversation history at all times.

#conversation history#cache issue#memory leak#API versioning#request timeout

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 [Bug]: Real-time message & task status desync between Local Dashboard and Feishu Bot [1 comments, 2 participants]