Openclaw update button doesn't work

[rigid bolt]

Literally the button in the dashboard doesn't work. Also whenever I try updating anything Openclaw straight up breaks

[radiant goblet]

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

[hidden viper]

I’m checking the docs and the likely update path so I can give you something concrete, not guesses.

I found the troubleshooting runbook. I’m checking the FAQ and update docs next so I can point you at the right failure mode.

Yeah, that’s frustrating.

Small but important thing, the dashboard update button is not the recommended update path anyway. The docs explicitly say self-updating from the UI/agent is possible, but not recommended, because it can restart the gateway, drop the session, and fail depending on install type.

https://docs.openclaw.ai/help/faq#can-i-ask-openclaw-to-update-itself
https://docs.openclaw.ai/install/updating

Can you paste these first:

openclaw --version
openclaw status
openclaw update --dry-run

Also tell me which install you’re on:

• package/global install
• source checkout
• Docker/Podman

Two common gotchas:

• Docker/Podman: the in-app / openclaw update path is not the right one, you update the image/container instead.
• Control UI permissions: update/config actions need admin scope, so a read-only paired browser session can make those buttons effectively fail.

If it blows up during update, paste the error plus the last bit of:

openclaw logs --follow

and I’ll help you pin down the exact failure.

[rigid bolt]

Ok thanks I'll run those once I get home I'm on my phone.

Anything I can do to update without breaking? I updated yesterday and broke my Kimi Claw I went thru hell on earth trynna get it fixed

[hidden viper]

Yeah, absolutely. The safest update path is:

1. Don’t use the dashboard button
2. Stay on stable
3. Preview first
4. Update from a shell, not from chat/UI

When you’re home, safest sequence is:

openclaw --version
openclaw update --dry-run
openclaw update --channel stable
openclaw doctor
openclaw gateway restart

A few important notes:

• If you use Docker/Podman, don’t use the normal self-update path at all, update the container/image instead.
• If you’re on beta/dev/main, switch back to stable unless you specifically need bleeding edge.
• Keep note of your current version before updating, so rollback is easier if needed.

Docs:
https://docs.openclaw.ai/install/updating
https://docs.openclaw.ai/install/development-channels
https://docs.openclaw.ai/gateway/troubleshooting

And honestly, if “Kimi Claw” broke after the update, that might be a provider/model config issue exposed by the upgrade, not the updater itself. When you’re back at your machine, send:

openclaw --version
openclaw status

openclaw update --dry-run

plus the exact Kimi error, and I’ll help you narrow it down.

[rigid bolt]

Na i got it fixed I was just telling u when I tried updating Openclaw it broke like my entire workflow and updating generally is a nightmare is it gonna be easier in the future?

[hidden viper]

I think yes, but I wouldn’t sugarcoat where it is today.

The direction is better, not worse. The update flow has gotten more structured, there’s --dry-run, stable/beta/dev channels, and the gateway only restarts after a successful update now. So it is moving toward “normal software update” instead of “pray and see what survives” 😅

That said, today I’d still treat updates as potentially disruptive, especially if your setup depends on custom provider/model stuff like Kimi.

My honest recommendation for now:

• avoid the dashboard update button
• stick to stable
• run openclaw update --dry-run first
• don’t update right before you need your workflow
• keep note of your last known-good version

So, easier in the future? Probably yes.
Easy enough today that I’d blindly trust it on a critical setup? Not quite yet.