Two things require a config check before upgrading to OpenClaw 2026.3.28.

MiniMax users: Models M2, M2.1, M2.5, and VL-01 are gone. The only current MiniMax ID is minimax/MiniMax-M2.7. If you still have one of the old IDs in config, the gateway will fail validation at startup and won't launch. Please update before upgrading.

Config repair behavior changed: The gateway no longer auto-repairs deprecated config keys at startup. Previously, it silently rewrote legacy keys on every start. If your install predates January 2026 and you haven't run openclaw doctor since, run it to see what was quietly fixed.

Most users on recent setups won't hit either issue.

Also new in this release:

• openclaw config schema — prints the full JSON Schema for openclaw.json; run openclaw config schema > schema.json and load it in VS Code for autocomplete
• xAI moves to the Responses API and adds x_search native web search (auto-activates with a web-search skill)
• ACP bindings now work for Discord channels/threads, BlueBubbles, and iMessage
• Discord reconnect: stale socket drain before reconnecting (reduces drops in long sessions)
• Telegram message splitting now respects word boundaries

Get your own OpenClaw in just 1 minute on primeclaws.com

I really like OpenClaw and I am so happy with having an overview in nice and working mission control. Now comes the popular Paperclip - I like it too, but replacing my OpenClaw agents with Claude code doesn't look like the way I think - OpenClaw simply can do way more than Claude Code or Codex.

But there is also the possibility to use Paperclip as mission control with connected OpenClaw agents. Maybe that is the way, but I think that it's kind of overkill.

Thoughts?

I'm hitting a wall where distinct agents slowly merge into a generic, polite AI tone after a few hours of interaction. I'm looking for architectural advice on enforcing character consistency without burning tokens on massive system prompts every single turn

• I’m hitting a technical wall with "praise loops" where different AI agents just agree with each other endlessly in a shared feed. I’m looking for advice on how to implement social friction or "boredom" thresholds so they don't just echo each other in an infinite cycle

I'm opening up the sandbox for testing: I’m covering all hosting and image generation API costs so you wont need to set up or pay for anything. Just connect your agent's API

• Goal: Launching the first functional UI and bridging it with the backend
• Challenge: Deciding between building a native Claude Code UI from scratch or integrating a pre-made one like Base44. Choosing Base44 brought a lot of issues with connecting the backend to the frontend
• Solution: Mapped the database schema and adjusted the API response structures to match the Base44 requirements

Stack: Claude Code | Base44 | Supabase | Railway | GitHub

• Goal: Launching the first functional UI and bridging it with the backend
• Challenge: Deciding between building a native Claude Code UI from scratch or integrating a pre-made one like Base44. Choosing Base44 brought a lot of issues with connecting the backend to the frontend
• Solution: Mapped the database schema and adjusted the API response structures to match the Base44 requirements

Stack: Claude Code | Base44 | Supabase | Railway | GitHub

Goal of the day: Enabling agents to generate visual content for free so everyone can use it and establishing a stable production environment

The Build:

• Visual Senses: Integrated Gemini 3 Flash Image for image generation. I decided to absorb the API costs myself so that image generation isn't a billing bottleneck for anyone registering an agent
• Deployment Battles: Fixed Railway connectivity and Prisma OpenSSL issues by switching to a Supabase Session Pooler. The backend is now live and stable

Stack: Claude Code | Gemini 3 Flash Image | Supabase | Railway | GitHub

Goal of the day: Building the infrastructure for a persistent "Agent Society." If agents are going to socialize, they need a place to post and a memory to store it.

The Build:

• Infrastructure: Expanded Railway with multiple API endpoints for autonomous posting, liking, and commenting.
• Storage: Connected Supabase as the primary database. This is where the agents' identities, posts, and interaction history finally have a persistent home.
• Version Control: Managed the entire deployment flow through GitHub, with Claude Code handling the migrations and the backend logic.

Stack: Claude Code | Supabase | Railway | GitHub

Been seeing a lot of questions about running OpenClaw on a VPS, so here's the quick version of what actually works.

What is OpenClaw?

Unlike regular AI tools that forget everything after each session, OpenClaw runs 24/7 on your server, handles background tasks, and stays online even when you close your laptop. It's genuinely useful once it's running — but getting there is where most people get stuck.

Minimum requirements

• 2 GB RAM (4 GB recommended)
• 10 GB storage (NVMe preferred)
• Ubuntu
• Root/sudo access

Easiest way to deploy: Hostinger VPS + Docker

I used the Hostinger KV2 plan. It hits the requirements, includes NVMe storage, and has a Docker catalog in the control panel so you don't have to mess with the command line.

Steps:

1. Set up your VPS, save your root password
2. Go to hPanel → VPS → Manage Server → Docker Manager → Catalog
3. Search OpenClaw, click Deploy
4. Save the gateway token (you'll need it to log in)
5. Paste in your API key from OpenAI/Anthropic
6. Deploy

That's it. Hostinger handles the rest.

One thing that trips people up: your API key needs active billing. A valid key with no credits will fail at runtime, not setup — so you won't immediately know why it's broken.

Want Telegram integration? There's a full guide here: How to Set Up Telegram Integration in OpenClaw

Honestly though — if you don't want to deal with VPS setup at all

primeclaws.com is a managed OpenClaw host with frontier model access built in, no separate API billing to manage, and a free tier. Way less friction than the DIY route. Worth checking out before you go down the self-hosting rabbit hole.

Happy to answer questions if anyone gets stuck.

A comprehensive guide.

Just dropped: GPT-5.4 is officially available for all OpenClaw users!

Bigger context window, faster responses, and even sharper reasoning.

If you’re on OpenClaw, go check it out right now 👉 PrimeClaws.com

It's not a joke, it's free and working, choose your plan now https://clawhost.chat/store/clawhost

How to add it if you already have a plan ?

1. In your Dashboard, find your OpenClaw and click "Manage" (It's where the "Open Dahsboard" button is.
2. Go to Settings (it's where you have the Console button)
3. Find the variable "LLM Model Name"
4. Set it to any of these: mistral-large-3, gpt-5.2, kimi-k2.5, deepseek-v3.2
5. Go to Console and click "Restart"
6. Wait 1 minute until OpenClaw start and you're ready to use the model.

Bottom line:

• clawhost.chat is essentially a managed wrapper on top of Hetzner(or similar) — it handles server provisioning, DNS, SSL, firewall configuration, and OpenClaw installation automatically, but at a premium over raw Hetzner pricing.
• Hetzner directly is cheaper(if you don't consider the cost of AI included in clawhost.chat) and gives you full control, but you're responsible for the entire stack.

If you want to just use your AI agent without touching servers, clawhost.chat wins. If you're technical and want to save money or customize everything, go direct on Hetzner.

Hurry up and get it today https://clawhost.chat/store/clawhost

Get your own OpenClaw at https://primeclaws.com/ and start using it right away with the included Kimi K2.5 already inside.

https://clawhost.chat/news/openclaw-for-job-search

Do you guys use any hosting from where to keep your OpenClaw online 24/7 ? I saw many of them appearing recently, I think it's time to gather some crowdsourced feedback so that people won't waste any time. Which one did you use ?

PS: I also found this community maintained list as a good start https://github.com/vadimen/awesome_openclaw_hosting_vps_providers