openclaw - 💡(How to fix) Fix Memory wiki install error [1 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#63122Fetched 2026-04-09 07:58:14
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

openclaw wiki init and openclaw wiki status emit a Failed to read config error on OpenClaw 2026.4.8.

The wiki vault itself initializes and works correctly, but the Slack extension's legacyConfigRules crashes during config loading.

Error Message

Failed to read config at ~/.openclaw/openclaw.json TypeError: Cannot read properties of undefined (reading 't')
    at Object.get [as legacyConfigRules] (.../extensions/slack/contract-api.js:1:647)
    at resolvePluginDoctorContracts (.../config-DMMR1XE_.js:220:52)
    at listPluginDoctorLegacyConfigRules (.../config-DMMR1XE_.js:233:9)
    at resolveLegacyConfigForRead (.../config-DMMR1XE_.js:19138:82)
    at Object.loadConfig (.../config-DMMR1XE_.js:19203:29)

Root Cause

openclaw wiki init and openclaw wiki status emit a Failed to read config error on OpenClaw 2026.4.8.

The wiki vault itself initializes and works correctly, but the Slack extension's legacyConfigRules crashes during config loading.

Fix Action

Workaround

The wiki vault works correctly despite the error. The error appears to be cosmetic — originating from the Slack extension's legacy config rules, not from memory-wiki itself.

Code Example

Failed to read config at ~/.openclaw/openclaw.json TypeError: Cannot read properties of undefined (reading 't')
    at Object.get [as legacyConfigRules] (.../extensions/slack/contract-api.js:1:647)
    at resolvePluginDoctorContracts (.../config-DMMR1XE_.js:220:52)
    at listPluginDoctorLegacyConfigRules (.../config-DMMR1XE_.js:233:9)
    at resolveLegacyConfigForRead (.../config-DMMR1XE_.js:19138:82)
    at Object.loadConfig (.../config-DMMR1XE_.js:19203:29)
RAW_BUFFERClick to expand / collapse

Summary

openclaw wiki init and openclaw wiki status emit a Failed to read config error on OpenClaw 2026.4.8.

The wiki vault itself initializes and works correctly, but the Slack extension's legacyConfigRules crashes during config loading.

Error

Failed to read config at ~/.openclaw/openclaw.json TypeError: Cannot read properties of undefined (reading 't')
    at Object.get [as legacyConfigRules] (.../extensions/slack/contract-api.js:1:647)
    at resolvePluginDoctorContracts (.../config-DMMR1XE_.js:220:52)
    at listPluginDoctorLegacyConfigRules (.../config-DMMR1XE_.js:233:9)
    at resolveLegacyConfigForRead (.../config-DMMR1XE_.js:19138:82)
    at Object.loadConfig (.../config-DMMR1XE_.js:19203:29)

Steps to Reproduce

  1. Install OpenClaw 2026.4.8
  2. Enable Slack channel in openclaw.json
  3. Enable memory-wiki plugin in openclaw.json
  4. Run openclaw wiki init

Expected Behavior

openclaw wiki init should complete without config read errors.

Actual Behavior

Config read fails with TypeError: Cannot read properties of undefined (reading 't') in Slack extension's contract-api.js. Wiki vault initializes successfully despite the error.

Environment

  • OpenClaw: 2026.4.8 (9ece252)
  • OS: macOS (Darwin arm64)
  • Node: v25.8.2
  • Slack extension: enabled (socket mode)
  • Memory wiki: enabled (isolated mode)

Workaround

The wiki vault works correctly despite the error. The error appears to be cosmetic — originating from the Slack extension's legacy config rules, not from memory-wiki itself.

extent analysis

TL;DR

Disable the Slack extension or modify its legacyConfigRules to fix the Failed to read config error in OpenClaw 2026.

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