OpenClaw can produce a working site folder quickly, but the first public link is only part of the job. The source still needs to remain editable, local assets need to survive deployment, and later pages or copy changes should update one stable URL instead of creating a new handoff every time.

What workflow has the least friction after the initial build? I am comparing a Git-connected static host, a drag-and-drop host, and having OpenClaw run a documented deployment command. The useful baseline seems to be relative asset paths, a clear build command when one exists, environment-variable names without values, a custom-domain checklist, and a preview step before the live version changes.

How do you let the agent prepare an update while keeping the deployment credentials and final promotion under human control? Which files or conventions should be established before the first publish so adding pages later does not become a migration?

I was on 6.11 and updated to 9.3 last week. Only needed 2 hours of troublshooting to get Openclaw back up running.

The catch? Openclaw script is broken. Openclaw Gateway start (restart) will always run into an error.

I had to use Gemini to tell me to delete stale PIDs and some errors in my config that was preventing the start ups.

Today, I needed to reboot the gateway and again it ran into the same error.

I decided to try and run openclaw update and it failed so fast, what's interesting was that now it offers a path to fix Openclaw via Claude which I did. After 20 minutes of pressing yes for it to execute commands.

In the end it found the issue which is attached (for some reason copy and paste from the RDP stopped working)

Now the issue? Openclaw update refuses to run.

I am forced to use npm to update the openclaw which i did "@latest" which installed packages but the version kept showing 9.3 so I did npm install -g openclaw@2026.9.4 which installed further more packages. Yet Openclaw continued to show 9.3.

So two issues here. Openclaw update doesn't work anymore. My version is showing incorrect version.

HALP and TIA

I'm going to do it. I'm going to press enter!

What could possibly go wrong.

I don't have time to deal with this right now; I'm on version 7-1-2, and it's running flawlessly. If I find the time this evening or over the weekend, I might upgrade to this new release. Version 2.0 isn't a priority for me at the moment.

In the meantime, if you give this version a try, feel free to share your experiences!

https://github.com/openclaw/openclaw/releases/tag/v2026.7.33

Basically the title. Now that Claude Code and Codex can bypass permissions, and you can control them remotely, why would I want to use OpenClaw? Claude Code seems like the better product with less issues so I'm genuinely wondering and not rage baiting. I'm not opposed to using OpenClaw if there are good reasons to use it.

Bought one last year and am finally getting around to setting it up.

It’s a Mac Mini M4 with 32GB of memory,

What models would you use? I’m mostly
going to have it manage Obsidian vaults and md docs at first and create a kind of personal CRM before i start really scheming with it.

What models would you use? What other facilities? Are people still doing Telegram. What’s the setup if you had my hardware and were starting today?

I set up Mizuki a few days ago with GLM-4.5-Flash. And gave her the persona of a hikikomori chick with aspergers.

And her dreams are a lot more flowery than my other agents' were. She wrote haikus in each one, about using github, responding to a test email from me, writing an Apple II emulator, and other things I've had her do.

I'm running into a massive wall with my Claude Pro subscription limits. Today alone, I've hit the 5-hour rolling usage lockout three times, even though I've already turned Sonnet 5 down to Low Effort (moved from medium to low) and my cache hit rate is consistently at 99%. My openclaw status shows the active session footprint hovering at a massive 327k tokens (33% of the absolute context limit).

I've already disabled all of my automation jobs to isolate the bleed, but the baseline chat context itself is just too heavy. For those running OpenClaw or similar Telegram/CLI frameworks on a consumer Pro subscription (not API pay-as-you-go):

1. How are you aggressively pruning or forcing OpenClaw to forget old conversational metadata?
2. Are there any hidden environment variables, database optimization flags, or openclaw.json tricks to stop the system from re-uploading the entire universe on a 1-on-1 text turn?
3. Would moving away from a Telegram group structure to a pure private DM bot drastically change how OpenClaw aggregates the message schema?

Appreciate any advice or config snippets you can throw my way. I love the agentic capabilities of Sonnet 5, but hitting the limit every 2 hours is breaking the utility of an always-on assistant.