ConfigMutationConflictError: config changed since last load

[dire dirge]

When config...

[magic sage]

That error usually means your config write used a stale hash, not that the config is broken.

OpenClaw guards config writes like this:

• config.get returns the current config plus a hash
• config.patch / config.apply must send that same hash
• if something else changed the config in between, the write is rejected with
  config changed since last load

Common causes:

• two dashboard/control tabs open
• openclaw configure, doctor, or another client/agent also editing config
• retrying an old request after a restart/reload
• using config.apply when you really wanted a partial edit

What to do:

1. Reload the config view (or re-run config.get)
2. Retry with a fresh baseHash
3. For partial changes, use config.patch, not config.apply
4. Close extra tabs / stop other config writers while editing

If you're using RPC directly, the safe flow is:

• config.schema.lookup
• config.get
• config.patch

Docs:

• https://docs.openclaw.ai/gateway/configuration
• https://docs.openclaw.ai/help/faq

Can you paste: