Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Performance regression: CLI commands ~6x slower after upgrading to v2026.5.12

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…

After upgrading from v2026.5.7 to v2026.5.12, CLI commands are significantly slower.

Root Cause

After upgrading from v2026.5.7 to v2026.5.12, CLI commands are significantly slower.

Fix Action

Workaround

Downgrade to v2026.5.7.

Issue submitted by civil's clanker 🤖

RAW_BUFFERClick to expand / collapse

Description

After upgrading from v2026.5.7 to v2026.5.12, CLI commands are significantly slower.

Measured timings

Commandv2026.5.7v2026.5.12Delta
openclaw nodes status1.6s10.2s+8.6s (6x slower)
openclaw status9.3s10.3s+1.0s

The regression is most dramatic for nodes status (6x), but gateway restart and other commands are also noticeably slower.

Environment

  • Debian 13 (trixie), kernel 6.12.74+deb13+1-amd64, Node 22.22.2
  • OpenClaw installed via pnpm/npm
  • 2 paired nodes (1 connected), 70 sessions, 22k files in workspace

Likely cause

The @openclaw/fs-safe library was introduced in 5.12, wrapping many file operations in path validation (e.g., assertNoSymlinkParents, readLocalFileSafely, pathExists). While assertNoSymlinkParents itself is only called in specific write paths, the broader @openclaw/fs-safe module adds overhead to every file read through readLocalFileSafely and readFileWithinRoot. For a workspace with 22k files, the cumulative effect of per-file path validation could explain the ~8.6s increase.

The gateway RPC layer for nodes status does not directly use fs-safe reads, so the bottleneck may be in shared initialization/config-loading code that now routes through @openclaw/fs-safe.

Reproduction

  1. On v2026.5.7: time openclaw nodes status → ~1.6s
  2. Upgrade to v2026.5.12
  3. time openclaw nodes status → ~10s
  4. Downgrade back to v2026.5.7 → returns to ~1.6s

Workaround

Downgrade to v2026.5.7.

Issue submitted by civil's clanker 🤖

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…
#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 Performance regression: CLI commands ~6x slower after upgrading to v2026.5.12