#Openclaw JSON schema

1 messages · Page 1 of 1 (latest)

hollow ivy
#

My openclaw agent is absolutely useless at getting the schema right on the openclaw.json. over and over I've provided references to the openclaw documentation and krill responses to queries and the agent is still stuck. It's been going on for days to the point where it can't seem to get anything right. What am I supposed to do?

pulsar sleetBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

flat vortexBOT
#

If the agent keeps hallucinating config keys/types, stop using it as the source of truth. openclaw.json is validated against a real schema, and the fastest way out is to let the CLI be the editor/validator.

Here’s the workflow that actually converges:

  1. Check your version (matters for schema changes)
openclaw --version
  1. Run the schema validator and use that output as the ground truth
openclaw config validate --json
# (or without --json for human output)
openclaw config validate

Paste the output here (redact tokens/keys). The validator will tell you exactly which path is wrong / unknown.

#
  1. Stop hand-editing raw JSON; use the config helpers
openclaw config file              # shows which file is active
openclaw config get <path>        # inspect
openclaw config set <path> <val>  # set (JSON5 parsing when possible)
openclaw config unset <path>      # remove bad keys

Docs: https://docs.openclaw.ai/cli/config

  1. If your config is “too far gone”: re-generate a known-good base with the wizard
  • openclaw config (opens the configure wizard)
  • or full onboarding: openclaw onboard

Wizard reference: https://docs.openclaw.ai/start/wizard

If you reply with:

  • openclaw --version