Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: connection drops between gateway and OpenCL Control + unable to stop running task with /stop and button disapear [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#70991•Fetched 2026-04-24 10:37:00
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
alexandre-lengalexandre-leng
Participants
alexandre-lengalexandre-leng
Timeline (top)
labeled ×2renamed ×1

The connection between the gateway and the OpenClaw Control page drops during long tasks and prevents stopping the model, even when using /stop

Root Cause

This is pretty frustrating in practice, especially when the model starts going in the wrong direction and there’s no way to stop it after the connection drops. the fact that even /stop does nothing makes it much worse, because there is literally no fallback to interrupt the process. it really feels unstable under longer workloads

Code Example

no logs available right now but the issue is easily reproducible during normal usage with long tasks
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The connection between the gateway and the OpenClaw Control page drops during long tasks and prevents stopping the model, even when using /stop

Steps to reproduce

start a long coding task in OpenCLaw let it run (often happens more when verification tasks are also running) observe that the connection drops between the gateway and the control page in the browser reload the page notice the stop button is gone, and the task is still running try using /stop and see that it does not stop the process

Expected behavior

the connection should remain stable even during long tasks and the stop button should always be available to stop the model properly, including via /stop command

Actual behavior

The connection drops without warning, forcing a page reload, then the stop button disappears even when using /stop, it does not stop the process at all the model keeps generating code anyway, sometimes going completely off track with no way to regain control, which is really problematic

OpenClaw version

OpenClaw 2026.4.22 (00bd2cf)

Operating system

Windows 11

Install method

default windows

Model

kimi 2.6

Provider / routing chain

kimi 2.6

Additional provider/model setup details

No response

Logs, screenshots, and evidence

no logs available right now but the issue is easily reproducible during normal usage with long tasks

Impact and severity

affects normal usage during long-running tasks severity is quite high since it becomes impossible to stop execution, even when explicitly sending /stop happens fairly often with longer runs consequence: complete loss of control over the model, wasted time, and generation of irrelevant or incorrect code that cannot be interrupted

Additional information

This is pretty frustrating in practice, especially when the model starts going in the wrong direction and there’s no way to stop it after the connection drops. the fact that even /stop does nothing makes it much worse, because there is literally no fallback to interrupt the process. it really feels unstable under longer workloads

extent analysis

TL;DR

The connection drop between the gateway and the OpenClaw Control page during long tasks can be mitigated by investigating the stability of the connection protocol and the handling of long-running tasks.

Guidance

  • Investigate the connection protocol between the gateway and the OpenClaw Control page to identify potential issues that cause the drop during long tasks.
  • Review the task management system to ensure it can handle long-running tasks without interrupting the connection.
  • Verify if the /stop command is properly implemented and if there are any specific conditions under which it fails to stop the process.
  • Consider implementing a heartbeat or keep-alive mechanism to maintain the connection during long tasks.

Example

No specific code snippet can be provided without more information on the implementation details.

Notes

The issue seems to be related to the stability of the connection and the handling of long-running tasks. Without access to logs or more detailed information about the implementation, it's challenging to provide a definitive solution.

Recommendation

Apply a workaround by implementing a connection keep-alive mechanism or a more robust task management system to mitigate the connection drop issue, as the root cause is not immediately clear and may require further investigation.

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

the connection should remain stable even during long tasks and the stop button should always be available to stop the model properly, including via /stop command

#index setup#retrieval issue#search optimization#API routing#API middleware

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]: connection drops between gateway and OpenCL Control + unable to stop running task with /stop and button disapear [1 participants]