openclaw - 💡(How to fix) Fix Default openclaw status should avoid slow plugin/session/update work on the fast path [2 pull requests]

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…

Default openclaw status is intended to be a quick status command, but in a real configuration it can take more than 12 seconds. The slow path is not one single hang; it is cumulative cold-start and rendering overhead.

Observed major contributors:

  1. Plugin-aware config / secret target discovery during default fast status.
  2. Package update network check during default fast status.
  3. Text status summary hydrates model/runtime metadata for every historical session even though only recent rows are rendered.

Error Message

Before local fast-path changes:

Root Cause

Default openclaw status is slow because fast status still performs plugin-aware config work, update checks, and full historical session hydration

Fix Action

Fixed

Code Example

openclaw status: about 13.713.8s

---

openclaw status: about 10.410.8s
openclaw status --json: about 7.17.3s
openclaw gateway status: about 8.08.2s
openclaw --help: about 5.6s
RAW_BUFFERClick to expand / collapse

Issue/PR 2: default openclaw status should avoid slow plugin/session/update work

Title

Default openclaw status is slow because fast status still performs plugin-aware config work, update checks, and full historical session hydration

Affected version

  • OpenClaw CLI: 2026.5.22
  • Platform: Linux x64

Summary

Default openclaw status is intended to be a quick status command, but in a real configuration it can take more than 12 seconds. The slow path is not one single hang; it is cumulative cold-start and rendering overhead.

Observed major contributors:

  1. Plugin-aware config / secret target discovery during default fast status.
  2. Package update network check during default fast status.
  3. Text status summary hydrates model/runtime metadata for every historical session even though only recent rows are rendered.

Observed behavior

Before local fast-path changes:

openclaw status: about 13.7–13.8s

After applying local fast-path changes:

openclaw status: about 10.4–10.8s
openclaw status --json: about 7.1–7.3s
openclaw gateway status: about 8.0–8.2s
openclaw --help: about 5.6s

Timings are from one Linux host and should be treated as directional, not as benchmark guarantees.

Proposed changes

1. Recent-session fast path

For default openclaw status, only render recent session rows. Avoid hydrating model/runtime metadata for every historical session when only top-N recent rows are displayed.

Implementation idea:

  • Count sessions cheaply per store.
  • For each agent/store, sort/select recent N first.
  • Hydrate model/runtime metadata only for rows that will be displayed.
  • Compute total count from cheap counts, not from fully built rows.

2. Default status config fast path

For default openclaw status only, avoid channel plugin secret-target discovery during config resolution.

Keep the full plugin-aware path for:

  • openclaw status --deep
  • openclaw status --all
  • commands that intentionally inspect channel/plugin details

3. Skip package update check in default fast status

Default openclaw status should not perform package update network checks. Keep update checks for --deep, --all, or an explicit update/doctor command.

Expected result

  • Default openclaw status becomes consistently fast enough for routine diagnostics.
  • Deep/plugin-aware checks remain available through explicit flags.
  • The status command no longer surprises users with slow network/plugin work on the default path.

Privacy note

This report intentionally excludes:

  • user IDs, chat IDs, message IDs, sender IDs;
  • LAN IP addresses and private hostnames;
  • private file paths unrelated to generic OpenClaw installation examples;
  • credentials, account names, tokens, or private config values.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING