#Failed to start CLI: ConfigMutationConflictError: config changed since last load

5 messages · Page 1 of 1 (latest)

chrome thicket
#

Failed to start CLI: ConfigMutationConflictError: config changed since last load while changing provider

tidal oracleBOT
craggy jasperBOT
#

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

blazing nestBOT
#

That usually means something else changed your config between load and save. In practice, it’s often another OpenClaw process, the dashboard/onboarding flow, or two CLI commands touching config at once.

Please paste these 3 things first:

openclaw --version
openclaw status --all

and also the exact command that triggers the error.

Quick things to try before retrying:

  • close any OpenClaw dashboard / onboarding / config-editing tab
  • stop any other openclaw command that might still be running
  • then run the command again once
  • if it still fails, run: