Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: CLI Performance Regression: 20-40s hang after hook loading since v4.5+ [3 comments, 3 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#63242•Fetched 2026-04-09 07:56:25
View on GitHub
Comments
3
Participants
3
Timeline
13
Reactions
2
Author
Vksh07Vksh07
Participants
fortunafortunaopenclaw-barnacle[bot]openclaw-barnacle[bot]Vksh07Vksh07
Timeline (top)
subscribed ×5commented ×3mentioned ×3labeled ×2

Description: After upgrading from v4.2 to v4.5+, all OpenClaw CLI commands are extremely slow (~60s+ per command). The gateway responds quickly (8ms) but CLI commands timeout.

Root Cause

Description: After upgrading from v4.2 to v4.5+, all OpenClaw CLI commands are extremely slow (~60s+ per command). The gateway responds quickly (8ms) but CLI commands timeout.

Code Example

Logs:

Copy
15:47:01+00:00 [hooks] loaded 4 internal hook handlers
15:48:01+00:00 [ws] ← open ...  (60s gap)
...
15:48:37+00:00 ⇄ res ✓ chat.history 35927ms
15:48:37+00:00 ⇄ res ✓ models.list 35853ms
Regression: Fast in v4.2, slow in v4.5+
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Description: After upgrading from v4.2 to v4.5+, all OpenClaw CLI commands are extremely slow (~60s+ per command). The gateway responds quickly (8ms) but CLI commands timeout.

Steps to reproduce

Steps to Reproduce:

Run any CLI command: openclaw gateway status, openclaw sessions list, etc. Observe 60+ second delay before response

Expected behavior

Expected Behavior (like that of v4.2): Commands should complete in 10-15 seconds

Actual behavior

Actual Behavior (v4.5+):

60s hang between [hooks] loaded 4 internal hook handlers and WebSocket connection Massive RPC delays: chat.history: 35,927ms models.list: 35,853ms Direct gateway health check: 8ms (fast) CLI commands: 60s+ (slow) Environment:

OpenClaw version

OpenClaw: 2026.4.5+, Node: v22.22.2

Operating system

OS: WSL2 (Ubuntu)

Install method

npm

Model

All Models

Provider / routing chain

all model rioutes

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Logs:

Copy
15:47:01+00:00 [hooks] loaded 4 internal hook handlers
15:48:01+00:00 [ws] ← open ...  (60s gap)
...
15:48:37+00:00 ⇄ res ✓ chat.history 35927ms
15:48:37+00:00 ⇄ res ✓ models.list 35853ms
Regression: Fast in v4.2, slow in v4.5+

Impact and severity

User workflow disruption, unusability, Mental stress of hang

Additional information

need emergent fix. it gets unusable at times @steipete @vincentkoc @vignesh07

extent analysis

TL;DR

The most likely fix for the slow OpenClaw CLI commands is to investigate and address the massive RPC delays, specifically the chat.history and models.list requests, which are causing the 60-second hang.

Guidance

  • Verify the RPC delay times for chat.history and models.list requests to confirm they are the cause of the slow CLI commands.
  • Check the differences in configuration or implementation between v4.2 and v4.5+ that may be contributing to the RPC delays.
  • Investigate potential issues with the WebSocket connection, as indicated by the 60-second gap in the logs.
  • Consider temporarily downgrading to v4.2 to confirm that the issue is specific to v4.5+ and to gather more information about the regression.

Example

No specific code snippet is provided, as the issue is more related to configuration and implementation changes between versions.

Notes

The issue seems to be specific to the OpenClaw CLI and the RPC delays, and it's not clear what changes were made between v4.2 and v4.5+ that could be causing this regression. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by temporarily downgrading to v4.2, as it is known to work as expected, while investigating the root cause of the RPC delays in v4.5+. This will allow users to continue working with a functional version of OpenClaw while a more permanent fix is developed.

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

Expected Behavior (like that of v4.2): Commands should complete in 10-15 seconds

#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

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

Back to top recommendations

TRENDING