OpenClaw on Windows: the install was never the hard part
For an old dog like me — someone who hasn't touched a command line in years — the pain points of installing OpenClaw are painfully obvious: dependencies, hoops, sources, mirrors. One wrong step and you start over. I was on the verge of giving up on OpenClaw and switching to another agent assistant when Windows Hub came along. So I pressed my puffy old face right up against it — and by then it was too late. Checked the box, got the green toast, restarted, nothing had changed. Deleted configs were still running. Stuck on a spinner with no error. Only after the install did I find out which step had failed. Individually none of it is fatal. Together, it can turn a quick flex in front of a girl into a small hell of embarrassment.
Later I went through filesystems, containers, stacks, headless and remote one by one, and only then did I understand why Linux is OpenClaw's real home. So I dropped Windows Hub, brought OpenClaw back home — to WSL — and built Rheia: a project that needs nothing more than a double-click on the Windows side.
To get there, I gave up most of the object-oriented thinking I had held onto for over a decade. At its core, Rheia is driven by declarations rather than code, so it can follow upstream instead of inventing yet another “installer” — which is how it stays aligned with the official definition of OpenClaw.
So if you have a moment to try it: your coffee may still be warm when a nearly full-strength OpenClaw shows up on your machine. And if OpenClaw is already deployed, remember to tick “OpenClaw already installed — install Rheia as a manager only”. Your digital assets can be priceless.
Think of Rheia as a shell — that's what I've always called it. I like to joke that it's Tony Stark's armour: with it on, OpenClaw is Iron Man in the Mark V, always ready. To make the armour fit OpenClaw better, we added “shell self-healing”: the shell follows the current version instead of clinging to its own shape.
It has flaws — you're the user, so I won't hide them.
The screen flicker is PySide6's chronic disease.
PySide6 runs on QtWebEngine (Chromium). On some GPU and driver combinations that stack repaints over and over: the same page is fine in Chrome and flickers inside QtWebEngine. The cause is in Chromium's compositor, not in application code — so it isn't a bug you patch away, it's the price of this technical path.
I tried GPU flags, the D3D11 backend, dialling down animations. They suppress part of it, never all of it. That isn't laziness — this is simply where this road ends. There are only two real fixes: rewrite the interface in another language, or buy a commercial Qt licence and use a different renderer. Both are on the roadmap, because both cost money and time. Talk is cheap.
If that bothers you, you can also use Rheia purely to deploy OpenClaw and keep typing openclaw dashboard in bash. That said, Rheia is more than flicker: live Gateway diagnostics, initial-setup backup, restore and conversation export, mainstream Chinese channels, a Provider console, a memory panel. And it isn't an empty shell — it's a ready-to-use, near-full-strength set: skill vetting, skill discovery, web search, persistent memory, Office document read and write, browser automation, long-text summarisation, self-improvement. We install those skills and plugins quietly in the background. Configure a model and it will surprise you quickly. Space is limited — whether it's any good, you'll have to find out.
As of writing, Rheia still has zero stars. There's nothing to dress up: a repository that just launched is supposed to be at zero. I'm writing this down because I'm tired of the “overnight success” narrative.
So
Old programmer or complete beginner, nobody should be held back from exploring by command lines and version dependencies. I've stepped in every pit for you; I've twisted every ankle for you too. Well — my cup is empty, time to brew another pot.
May you have fun with this little lobster, every day.