openclaw - 💡(How to fix) Fix [Bug]: v2026.4.1 Agents are working in secret; no actions are visible in the chat. [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#59265Fetched 2026-04-08 02:26:44
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
cross-referenced ×2labeled ×2commented ×1subscribed ×1

Agents and outputs are no longer visible in chat. This happened immediately after updating to v2026.4.1. No chats are currently being displayed in the OPC chat history. Additionally, Telegram messages are only partially displayed! You never know what your agent is up to.

Root Cause

Agents and outputs are no longer visible in chat. This happened immediately after updating to v2026.4.1. No chats are currently being displayed in the OPC chat history. Additionally, Telegram messages are only partially displayed! You never know what your agent is up to.

Code Example

no bad logs
21:50:09
info
gateway/ws
webchat disconnected code=1001 reason=n/a conn=41f42411-24eb-43af-87e7-2d2e86d12791
21:50:09
info
gateway/ws
webchat connected conn=d9af0f9f-3625-446f-a2fd-bbb06e349cf5 remote=127.0.0.1 client=openclaw-control-ui webchat vcontrol-ui
21:50:18
debug
cron
cron: timer armed
21:51:18
debug
cron
cron: timer armed
21:52:18
debug
cron
cron: timer armed
21:53:00
info
gateway/ws
webchat disconnected code=1001 reason=n/a conn=d9af0f9f-3625-446f-a2fd-bbb06e349cf5
21:53:00
info
gateway/ws
webchat connected conn=c5e6782a-addc-4f05-a068-f0c72b4e57bb remote=127.0.0.1 client=openclaw-control-ui webchat vcontrol-ui
21:53:18
debug
cron
cron: timer armed
21:54:18
debug
cron
cron: timer armed
21:55:18
debug
cron
cron: timer armed
21:56:18
debug
cron
cron: timer armed
21:57:18
debug
cron
cron: timer armed
21:58:18
debug
cron
cron: timer armed
21:58:22
info
gateway/ws
⇄ res ✓ config.schema 72ms conn=c5e6782a…57bb id=71e04de7…830f
21:58:23
info
gateway/ws
⇄ res ✓ config.get 166ms conn=c5e6782a…57bb id=a203c808…146d
21:58:26
info
gateway/ws
⇄ res ✓ config.schema 69ms conn=c5e6782a…57bb id=1fdca9d8…90fb
21:58:26
info
gateway/ws
⇄ res ✓ config.get 131ms conn=c5e6782a…57bb id=76d2ebe4…5803
21:58:27
info
gateway/ws
⇄ res ✓ config.schema 68ms conn=c5e6782a…57bb id=90cdc193…237e
21:58:27
info
gateway/ws
⇄ res ✓ config.get 92ms conn=c5e6782a…57bb id=1c3e30f3…7906
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Agents and outputs are no longer visible in chat. This happened immediately after updating to v2026.4.1. No chats are currently being displayed in the OPC chat history. Additionally, Telegram messages are only partially displayed! You never know what your agent is up to.

Steps to reproduce

Install the update and watch the chat!

<img width="1360" height="837" alt="Image" src="https://github.com/user-attachments/assets/92869700-1ddb-41fc-9a72-6b9ea2dd1dcb" /> <img width="1360" height="837" alt="Image" src="https://github.com/user-attachments/assets/f2bda0b1-6e0d-4da9-8d4f-fb15bebd5844" />

Expected behavior

v2026.4.1 Chat in main Panel

Actual behavior

no messages no TC Informations

OpenClaw version

v2026.4.1

Operating system

Win11

Install method

npm

Model

ollama/qwen3.5:27b

Provider / routing chain

chat

Additional provider/model setup details

No response

Logs, screenshots, and evidence

no bad logs
21:50:09
info
gateway/ws
webchat disconnected code=1001 reason=n/a conn=41f42411-24eb-43af-87e7-2d2e86d12791
21:50:09
info
gateway/ws
webchat connected conn=d9af0f9f-3625-446f-a2fd-bbb06e349cf5 remote=127.0.0.1 client=openclaw-control-ui webchat vcontrol-ui
21:50:18
debug
cron
cron: timer armed
21:51:18
debug
cron
cron: timer armed
21:52:18
debug
cron
cron: timer armed
21:53:00
info
gateway/ws
webchat disconnected code=1001 reason=n/a conn=d9af0f9f-3625-446f-a2fd-bbb06e349cf5
21:53:00
info
gateway/ws
webchat connected conn=c5e6782a-addc-4f05-a068-f0c72b4e57bb remote=127.0.0.1 client=openclaw-control-ui webchat vcontrol-ui
21:53:18
debug
cron
cron: timer armed
21:54:18
debug
cron
cron: timer armed
21:55:18
debug
cron
cron: timer armed
21:56:18
debug
cron
cron: timer armed
21:57:18
debug
cron
cron: timer armed
21:58:18
debug
cron
cron: timer armed
21:58:22
info
gateway/ws
⇄ res ✓ config.schema 72ms conn=c5e6782a…57bb id=71e04de7…830f
21:58:23
info
gateway/ws
⇄ res ✓ config.get 166ms conn=c5e6782a…57bb id=a203c808…146d
21:58:26
info
gateway/ws
⇄ res ✓ config.schema 69ms conn=c5e6782a…57bb id=1fdca9d8…90fb
21:58:26
info
gateway/ws
⇄ res ✓ config.get 131ms conn=c5e6782a…57bb id=76d2ebe4…5803
21:58:27
info
gateway/ws
⇄ res ✓ config.schema 68ms conn=c5e6782a…57bb id=90cdc193…237e
21:58:27
info
gateway/ws
⇄ res ✓ config.get 92ms conn=c5e6782a…57bb id=1c3e30f3…7906

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue with agents and outputs not being visible in chat after updating to v2026.4.1 may be resolved by checking the webchat connection and configuration.

Guidance

  • Verify the webchat connection by checking the logs for any disconnection events, such as webchat disconnected code=1001 reason=n/a.
  • Check the configuration settings for any changes that may have been introduced in v2026.4.1, specifically the config.schema and config.get requests.
  • Investigate the cron timer events to see if they are related to the issue.
  • Review the chat history and Telegram messages to see if there are any patterns or errors that can help identify the cause.

Example

No code snippet is provided as there is no clear indication of a specific code issue.

Notes

The issue may be related to a configuration change or a webchat connection issue, but more information is needed to determine the root cause.

Recommendation

Apply workaround: Check the webchat connection and configuration settings to see if any changes can be made to resolve the issue. This is recommended as the first step to try to resolve the issue before considering other options.

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

v2026.4.1 Chat in main Panel

Still need to ship something?

×6

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

Back to top recommendations

TRENDING