My Problem with OpenClaw


Honestly at this point I’m about done with OpenClaw and their misguided Doctor nonsense. Doctor warnings are probably great for the beginner who doesn’t understand the ramifications of the runtime choices being made. I’ve investigated nearly every setting, read the docs front to back, and explicitly hand-chosen and curated the configuration of the setup I’m running. I understand the risk of binding to LAN (and permitting exactly one entry point via a trusted proxy). I understand I’m not running the gateway as a systemd user unit. The Matrix channel configuration I’ve chosen IS THE ONLY ONE THAT WORKS for what I need. Quit fucking touching my configuration!

There MUST be a toggle to shut this fucking idiot up and make it stop casually mutating my configuration – some means to suppress the nonsensical warnings that I have already accepted as risk. I’ve already come up with a plan of maintenance. I’m tired of rehashing these things. I’m tired of having doctor “fix” my setup according to the idea of what *SOMEONE ELSE THINKS* I should be using on *MY* system. Only to have to go undo the changes after the fact when Doctor fucks it all to pieces. See the problem here? This system is mine. Doctor’s advisement is one thing (and, you know, entirely acceptable despite how strongly I despise it right now). Unchecked mutation authority is another. This is unacceptable and I’m done with it.

And before you go and say “Jimmie, just use OPENCLAW_NIX_MODE=1,” that does not solve anything to do with updater safety. It disables openclaw update entirely. On nix, sure that might make sense. It’s even in the name of the stupid env variable. Embedding an unskippable repair operation inside the updater with unchecked power to rewrite configuration is lunacy. Just default doctor to advisement, but with a prompt to accept modifications. Blind modification is the problem.

Maybe it’s beyond time to go look at Hermes… ~*wanders off muttering obscenities*~ </rant>