openclaw doctor --show-values?

[mild slate]

Is there a way of getting openclaw doctor to show the values of changes it wants to do to the config?

I store my config is a kubernetes secret so doctor doesn't have write access to the secret/config.
How do I find out what vales to change for these openclaw doctor changes:

◇ Doctor changes │ Discord configured, enabled automatically. │ Telegram configured, enabled automatically. │ Slack configured, enabled automatically. │ google/gemini-3.1-flash-lite-preview model configured, enabled automatically. │ ollama/gpt-oss:20b model configured, enabled automatically. │ browser tool referenced, enabled automatically. │ acpx plugin config present, added to plugin allowlist. │ memory-core plugin config present, added to plugin allowlist.

[spiral moss]

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

[mild slate]

The same question to when doctor outputs:

Apply recommended config repairs now?

I'm guessing that it is referring to the auto enablement it wants to do?

[pure anvil]

I checked the current docs/source: I don’t see a doctor --show-values / diff-style option today.

For those exact doctor lines, the effective patch is roughly:

{
  channels: {
    discord: { enabled: true },
    telegram: { enabled: true },
    slack: { enabled: true },
  },

  plugins: {
    // if you use plugins.allow, append these:
    allow: [
      "discord",

      "telegram",
      "slack",
      "google",
      "ollama",
      "browser",
      "acpx",
      "memory-core",
    ],

    entries: {
      google: { enabled: true },
      ollama: { enabled: true },
      browser: { enabled: true }

      // acpx + memory-core: your entries already exist;

      // doctor is saying to add them to plugins.allow.
    }
  }
}

Important nuance: merge these into your existing config — don’t replace existing tokens/account settings.

A practical way to get the exact diff for Kubernetes-secret workflows is:

tmp="$(mktemp -d)"
cp /path/to/openclaw.json "$tmp/openclaw.json"

OPENCLAW_CONFIG_PATH="$tmp/openclaw.json" \

OPENCLAW_STATE_DIR="$tmp/state" \
openclaw doctor --fix

diff -u /path/to/openclaw.json "$tmp/openclaw.json"

Then copy the diff back into your Secret.

Docs: https://docs.openclaw.ai/gateway/doctor and https://docs.openclaw.ai/gateway/configuration-reference

Also, what openclaw --version are you on? Doctor behavior has been moving quickly, so worth checking.

Yep — your guess is right.

Apply recommended config repairs now? appears when doctor has built a pending config patch. In your case, that includes the auto-enable changes it just printed. If there were other Doctor changes sections earlier, those are included too.

It’s config-only at that prompt — not service restarts/sandbox/etc.

For your specific output, the repair is mainly:

channels.discord.enabled: true
channels.telegram.enabled: true
channels.slack.enabled: true

plugins.entries.google.enabled: true
plugins.entries.ollama.enabled: true
plugins.entries.browser.enabled: true

And because you seem to have a restrictive plugins.allow, append:

"discord", "telegram", "slack",
"google", "ollama", "browser",
"acpx", "memory-core"

There isn’t currently a nice doctor --show-values/diff mode, so the safest workflow is still: run doctor against a writable copy of the config, then diff it. That would be a reasonable GitHub issue/feature request IMO: https://github.com/openclaw/openclaw/issues

[mild slate]

Thanks. That should give me enough to work through the changes.

[pure anvil]

Glad that helped! 🎉

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it for future folks.