openclaw - 💡(How to fix) Fix [Bug]: Config-writing commands flatten existing $include-based config into openclaw.json [2 comments, 3 participants]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

I use $include in openclaw.json to split my config into separate files.

This works correctly when OpenClaw reads the config, but when I run a config-writing command like openclaw onboard, the root openclaw.json is rewritten as one flat merged config and the $include structure is lost.

Steps to reproduce

1. Create an openclaw.json that uses $include for separate config files.
2. Run openclaw onboard.
3. Check openclaw.json.

Expected behavior

I expected OpenClaw to preserve the existing $include structure.

Actual behavior

openclaw.json is rewritten as a flat merged config, and my split config layout is destroyed.

OpenClaw version

OpenClaw 2026.4.21 (f788c88)

Operating system

Windows 11 WSL2

Install method

global npm install

Model

GLM-5.1

Provider / routing chain

openclaw -> ollama cloud -> GLM 5.1

Additional provider/model setup details

No response

Logs, screenshots, and evidence

## Example config
json5
{
  "agents": { "$include": "./config/agents.json" },
  "models": { "$include": "./config/models.json" },
  "gateway": { "$include": "./config/gateway.json" },
  "channels": { "$include": "./config/channels.json" },
  "plugins": { "$include": "./config/plugins.json" },
  "auth": { "$include": "./config/auth.json" },
  "tools": { "$include": "./config/tools.json" },
  "bindings": { "$include": "./config/bindings.json" }
}

Impact and severity

Affected: everyone with $include in config

Additional information

• I am not a programmer, so I may not be able to answer deep implementation questions.
• I can confirm the behavior on my setup.
• I currently use a workaround script to split the config again after updates/config writes.
• I am reporting this because $include is already a supported feature, so I expected config-writing commands to respect it.