Hey all, we've updated the installation guide in the classroom to include a A-Z walkthrough with screenshots, examples, and all troubleshooting steps. If you're new here, starting with OpenClaw, and/or want to fortify your agent setup, this is where to start --> go to Classroom - Install Zo Computer (VPS) - Install OpenClaw on Zo - How to Connect Openrouter LLMs to Your OpenClaw - Setup Telegram and Launch OpenClaw We've also updated the guides on running health and security checks, optimising your agents, connecting Zo workspace to Telegram, and testing and optimising your LLMs directly. Keep building and ping either Peter or myself with any questions.

Hey all, just posted an updated troubleshooting guide in the Classroom. This covers all the common errors when installing, running, and maintaining your OpenClaw with Zo Computer setup. I've personally tested all of these and have run into almost every type of setup and maintenance error. However, if you come across a new error not listed or have been struggling with any strange OpenClaw maintenance and runtime issues, share them here for other to see and I can triage them. Keep building https://www.skool.com/moltbot-builders-club-7244/classroom/14b4d86d?md=c0aff4632107409babc9b9ba1811b928

OpenClaw 4.5 is one of the biggest updates yet with video and music gen directly inside agent conversations. This is huge for SMM, AI media gen sandboxes, and scaling content/data. The second big feature is the new Dreaming memory system, a background memory system with three phases that runs automatically while you work (or sleep). The 3 Phases: - Light: handles short-term recall - Deep: promotes important information into long-term memory - REM: surfaces 'lasting truths', things the agent determines you’ll always need to know with light, deep, and REM phases to build smarter long-term recall. Agents and agentic infra is leaning hard into memory recall and scaling. This will always be a massive part of smart systems so get yourself familiar with memory, context window, and token usage. We just published the updates on SS: https://open.substack.com/pub/moltbot/p/openclaw-just-dropped-video-music?utm_campaign=post-expanded-share&utm_medium=web Drop below what you're working on now that requires good long-term memory recall and what systems you have in place to crank this. P.S. I run an AI second brain using Obsidian + Notion system that's self learning and auto organises my notes into a directory. It's separate from my OpenClaw setups but useful for better integrating your note taking and thinking by leveraging AI.

Did you know you can set and run custom automations from Zo Computer that execute in the background for you? Set the time interval, provide the instructions, run the automation in the background. Get research reports, status updates, run regular health checks ... We run a an automation that executes regular health checks on your OpenClaw gateway. Try the below setup yourself and have AI do your heavy lifting for you to ensure your agents are always running without hiccups. Happy building and ping us with your questions. *** Set up a custom automation to regularly check the connection to you OpenClaw sessions (gateway). This runs in the background for you, ensures you’re always connected, and will send regular session status reports for your email via your Zo workspace account e.g. **`<your-workspace@zo.computer>`** To set this up: 1. In Zo > Automations > click the ‘+’ for a new automation 2. Name your automation e..g **`openclaw-gateway-health`** 3. Set the schedule to Interval > Every 60 minutes 4. Paste the below system prompt into the prompt window, then Save. ``` “Check OpenClaw gateway health and restart if needed. 1. First check if gateway is responding via HTTP: curl -s --max-time 10 http://localhost:18789/health 2. If HTTP returns 200, check detailed health: openclaw health (timeout 20s) 3. If gateway is down or unresponsive: Kill any existing processes: pkill -9 -f "openclaw-gateway" Clear lock file: rm -f /root/.openclaw/.gateway.lock Load env: export $(grep -v '^#' /root/.openclaw/.env | xargs) Restart: nohup openclaw gateway --force >> /tmp/openclaw-gateway.log 2>&1 & Wait 15 seconds then verify with openclaw health 4. If restart fails, try again once more 5. Log all actions to /tmp/openclaw-agent-monitor.log 6. Report status: only when check failed, if restart was needed, and current health status” ```

Since many are using Openclaw already, just curious where you guys run it?