openclaw - 💡(How to fix) Fix Matrix config invalid after update: flat dmPolicy/allowFrom reintroduced in 2026.5.19

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…

On OpenClaw 2026.5.19, running openclaw update can leave Matrix channel config invalid by reintroducing flat DM fields that the external Matrix plugin schema rejects.

This appears related to the previously reported doctor metadata packaging issue in #71757, but the trigger here is the normal update flow on the released npm/global install, not an explicit openclaw doctor --fix run.

Root Cause

On OpenClaw 2026.5.19, running openclaw update can leave Matrix channel config invalid by reintroducing flat DM fields that the external Matrix plugin schema rejects.

This appears related to the previously reported doctor metadata packaging issue in #71757, but the trigger here is the normal update flow on the released npm/global install, not an explicit openclaw doctor --fix run.

Code Example

openclaw update

---

OpenClaw config is invalid
Problem:
  - channels.matrix: invalid config: must NOT have additional properties
  - channels.matrix: invalid config: must NOT have additional properties

---

{
  "channels": {
    "matrix": {
      "dmPolicy": "allowlist",
      "allowFrom": ["..."]
    }
  }
}

---

{
  "channels": {
    "matrix": {
      "dm": {
        "policy": "allowlist",
        "allowFrom": ["..."]
      }
    }
  }
}

---

channels.matrix.dm.policy
channels.matrix.dm.allowFrom
RAW_BUFFERClick to expand / collapse

Summary

On OpenClaw 2026.5.19, running openclaw update can leave Matrix channel config invalid by reintroducing flat DM fields that the external Matrix plugin schema rejects.

This appears related to the previously reported doctor metadata packaging issue in #71757, but the trigger here is the normal update flow on the released npm/global install, not an explicit openclaw doctor --fix run.

Environment

  • OpenClaw: 2026.5.19
  • Matrix plugin: @openclaw/matrix 2026.5.19
  • Install style: npm/global host install
  • Platform: macOS

What happened

After running:

openclaw update

OpenClaw reported:

OpenClaw config is invalid
Problem:
  - channels.matrix: invalid config: must NOT have additional properties
  - channels.matrix: invalid config: must NOT have additional properties

Inspecting the Matrix channel config showed that these two flat top-level properties had been written under channels.matrix:

{
  "channels": {
    "matrix": {
      "dmPolicy": "allowlist",
      "allowFrom": ["..."]
    }
  }
}

But the installed Matrix plugin schema accepts the nested form:

{
  "channels": {
    "matrix": {
      "dm": {
        "policy": "allowlist",
        "allowFrom": ["..."]
      }
    }
  }
}

Manually moving the values from:

  • channels.matrix.dmPolicy to channels.matrix.dm.policy
  • channels.matrix.allowFrom to channels.matrix.dm.allowFrom

and removing the flat keys made openclaw config validate pass again.

Evidence from installed package

The Matrix plugin setup surface uses nested config paths:

channels.matrix.dm.policy
channels.matrix.dm.allowFrom

The Matrix plugin schema is strict and exposes dm: buildNestedDmConfigSchema(...), so the flat top-level dmPolicy and allowFrom keys are rejected as additional properties.

Expected behavior

openclaw update should not rewrite Matrix DM policy/allowlist into flat top-level keys that are invalid for the installed @openclaw/matrix plugin schema.

If a config migration is needed, it should preserve or migrate to the nested Matrix shape.

Notes

This looks very close to #71757, where a maintainer explained that packaged doctor metadata could miss Matrix's nested-only mode and fall back to flat repair mode. This issue is to report that the same effective failure is still observable in the 2026.5.19 release after openclaw update.

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…

FAQ

Expected behavior

openclaw update should not rewrite Matrix DM policy/allowlist into flat top-level keys that are invalid for the installed @openclaw/matrix plugin schema.

If a config migration is needed, it should preserve or migrate to the nested Matrix shape.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING