openclaw - 💡(How to fix) Fix plugin runtime config.loadConfig() is deprecated warning [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#73507Fetched 2026-04-29 06:19:03
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
Timeline (top)
closed ×1commented ×1

The following deprecation warning appears in the logs:

plugin runtime config.loadConfig() is deprecated (runtime-config-load-write); use config.current().

This warning comes from OpenClaw's core plugin runtime code, not from user-installed plugins.

Root Cause

The following deprecation warning appears in the logs:

plugin runtime config.loadConfig() is deprecated (runtime-config-load-write); use config.current().

This warning comes from OpenClaw's core plugin runtime code, not from user-installed plugins.

Code Example

plugin runtime config.loadConfig() is deprecated (runtime-config-load-write); use config.current().
RAW_BUFFERClick to expand / collapse

Description

The following deprecation warning appears in the logs:

plugin runtime config.loadConfig() is deprecated (runtime-config-load-write); use config.current().

This warning comes from OpenClaw's core plugin runtime code, not from user-installed plugins.

Source

The warning appears to originate from internal OpenClaw modules:

  • /dist/audit-extra.async-*.js
  • /dist/status.scan-overview-*.js

Both have a loadConfigModule() function that uses the deprecated loadConfig() method.

Expected Behavior

Use config.current() instead of config.loadConfig() to load configuration.

Environment

  • OpenClaw version: 2026.4.26
  • Node.js: v22.22.2
  • OS: Linux

extent analysis

TL;DR

Update the loadConfigModule() function in the affected OpenClaw modules to use config.current() instead of the deprecated loadConfig() method.

Guidance

  • Identify and update the loadConfigModule() functions in /dist/audit-extra.async-*.js and /dist/status.scan-overview-*.js to use config.current().
  • Verify that the deprecation warning is resolved by checking the logs after applying the update.
  • Consider updating OpenClaw to a version where this issue is fixed, if available.
  • Review the OpenClaw documentation for any additional guidance on migrating from loadConfig() to config.current().

Example

// Before
function loadConfigModule() {
  const config = config.loadConfig();
  // ...
}

// After
function loadConfigModule() {
  const config = config.current();
  // ...
}

Notes

The fix assumes that config.current() is a direct replacement for loadConfig() in the affected modules. Additional testing may be necessary to ensure the updated code functions as expected.

Recommendation

Apply workaround: Update the loadConfigModule() functions to use config.current(), as this is a targeted fix for the deprecation warning and does not require upgrading OpenClaw.

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

openclaw - 💡(How to fix) Fix plugin runtime config.loadConfig() is deprecated warning [1 comments, 2 participants]