Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Regression] 4.22-4.29 significantly slower than 4.21 [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#75561•Fetched 2026-05-02 05:33:12
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
Zhang-hang-315Zhang-hang-315
Participants
clawsweeper[bot]clawsweeper[bot]Zhang-hang-315Zhang-hang-315
Timeline (top)
closed ×1commented ×1cross-referenced ×1

Code Example

npm install -g openclaw@2026.4.21
RAW_BUFFERClick to expand / collapse

Downgrading from 2026.4.29 to 2026.4.21 completely resolved the performance issue.

Problem: After upgrading to 2026.4.29 (and presumably 4.22-4.28), the system-prompt compilation stage became extremely slow, making responses very slow (~33 seconds per response on 4.29 vs ~1-3 seconds on 4.21).

Environment:

  • OpenClaw 2026.4.29 (beta.1) on macOS
  • Running as LaunchAgent (launchd)
  • Model: newapi/MiniMax-M2.7-highspeed

Trace data on 4.29 (before downgrade):

StageDuration
auth~5s
core-plugin-tools~5s
bundle-tools~5s
system-prompt~12s
stream-setup~10s
Total~33s

Trace data on 4.21 (after downgrade):

  • Response time returned to normal (~1-3 seconds)

Related issues:

  • #73501, #73298, #74192, #73353

Fix:

npm install -g [email protected]

Expected: 4.22+ should have the same performance as 4.21.

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.21 to resolve the performance issue.

Guidance

  • The performance issue is likely caused by a regression introduced in versions 2026.4.22-2026.4.29, specifically affecting the system-prompt compilation stage.
  • To verify the issue, compare the response times between versions 2026.4.21 and 2026.4.29 using the provided trace data.
  • The npm install -g [email protected] command can be used to downgrade to the working version.
  • Review related issues (#73501, #73298, #74192, #73353) for potential insights into the root cause.

Example

No code snippet is necessary in this case, as the issue is resolved through a version downgrade.

Notes

The exact cause of the performance issue is unknown, but downgrading to version 2026.4.21 has been confirmed to resolve the issue.

Recommendation

Apply workaround: Downgrade to version 2026.4.21, as it has been verified to restore normal performance.

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…
#api#task chaining#parallel task#integration issue#index setup

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 [Regression] 4.22-4.29 significantly slower than 4.21 [1 comments, 2 participants]