openclaw - 💡(How to fix) Fix [Bug]: Feishu plugin: only last message visible after tool call when streaming output is enabled

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

I had previously submitted this issue, and the response at that time was that it had been fixed, but after using the new version, I found that it had in fact not been fixed. The old issue is https://github.com/openclaw/openclaw/issues/83180

When using the Feishu plugin with OpenClaw:

• With streaming output enabled: Only the messages from the last tool call are visible in Feishu. Messages sent before that tool call disappear.
• Without streaming output: Feishu only displays the last message from OpenClaw once OpenClaw finishes responding. All previous messages during the response are not visible.

This causes incomplete conversation history in Feishu, especially when multiple messages or tools are involved.

Steps to reproduce

1. Enable the Feishu plugin in OpenClaw.
2. Optionally enable streaming output.
3. Send multiple normal messages or prompts.
4. Trigger one or more tool calls.
5. Observe in Feishu:

• With streaming enabled: only messages from the last tool call are visible.
• Without streaming: only the last OpenClaw message is displayed after it finishes responding.

Expected behavior

All messages generated by OpenClaw, including pre-tool call messages, should appear in Feishu in the correct order, regardless of streaming mode.

Actual behavior

• Streaming mode: only last tool call messages appear
• Non-streaming mode: only the last OpenClaw message appears after completion.

OpenClaw version

2026.5.18

Operating system

Ubuntu 22.04 LTS

Install method

npm global

Model

deepseek v4 pro

Provider / routing chain

openclaw (self-hosted) -> deepseek/deepseek-v4-pro

Additional provider/model setup details

Self-hosted OpenClaw running on my own cloud server.

The Feishu plugin sends user messages to OpenClaw, and OpenClaw calls the model provider directly through the official DeepSeek API.

Effective routing chain:

• openclaw self-hosted server -> official DeepSeek API -> deepseek-v4-pro

• No extra model router, reverse proxy, or third-party AI gateway is used for the model request path.

• Streaming is enabled in the Feishu integration. The issue appears related to how Feishu receives or updates OpenClaw responses before and after tool calls. Sensitive values such as API keys, gateway tokens, and auth credentials are omitted.

Logs, screenshots, and evidence

There are two images in the previous input box.

Impact and severity

Affected users/systems/channels: Users interacting with OpenClaw via the Feishu plugin, especially when streaming output is enabled.

Severity: Blocks workflow / conversation continuity — pre-tool-call messages disappear, making it hard to follow the conversation in Feishu.

Frequency: Always — reproducible every time streaming output is enabled and a tool call occurs.

Consequence: Missed messages: messages sent before a tool call are not visible in Feishu, leading to incomplete conversation history and potential confusion in workflow.

Additional information

No response