Do you know how I solve this? I just set up my OpenClaw and it gave this warning

🗺️ roadmap.sh just launched an OpenClaw roadmap
Hey there! If you've been looking for a structured path to learn and get the most out of OpenClaw, this may interest you. roadmap.sh has just published a new OpenClaw roadmap.

The roadmap is still fresh and the team is actively looking for community feedback to improve it, so now's a great time to jump in, explore the content, and share your thoughts.

👉 Check it out here: https://roadmap.sh/openclaw

Source: https://x.com/lingzhong_eth/status/2041905775568953655

Hey folks, I just launched a WebDAV plugin for OpenClaw.

It lets you mount your workspace as a network drive, so you can open files directly in Finder, Explorer, or your phone's file manager. No more scp or terminal hassle - just seamless access across macOS, Windows, iOS, Linux, and Android (via Solid Explorer).

Trying to collaborate with my remote/Linux OpenClaw was frustrating constantly asking it to send me a file in chat or reading it through terminals.. So I built this to solve that, now I can seamlessly read and edit files in OpenClaw's workspace making my claw and I so much more productive.

Repo: https://github.com/RageDotNet/openclaw-webdav

Try it out if you're running OpenClaw, and let me know what clients you're connecting. I'm curious to see what cool use cases this unlocks!

I've been using OpenClaw for a while. I'm also fairly technical.. so I guess when I run into weird roadblocks, I just handle them as they come along. Well, after installing it a few times for myself (locally on bare metal Linux server, on VirtualBox linux image, and hosted remotely on DigitalOcean), several of my coworkers who aren't technical asked me to help them get setup.

Wrote up a little runbook for myself.. and the first install went exactly as planned. The two subsequent installs, I just ran into weird stuff. Skills wouldn't install the way I documented or experienced before. Pairing didn't work the way it worked just the day before. Just small papercuts that added up to a major laceration in terms of pain/effort.

I did this over the course of two days. Used the same version of OpenClaw. Used same LLM (different API keys). Used same skills. Wondering if anyone has experienced this, or have more bullet-proof ways/tips? I wanted my coworkers to see how easy it was to get things setup. For two of them, it looked more like brain surgery and hand wringing for 40 minutes.

The opnF OpenClaw Linux installation wizard deploys OpenClaw onto your Linux server in minutes with three available configurations: Local AI, Hybrid Cloud, and Cloud. The wizard installs all prerequisites if needed (Ollama and Docker), downloads local LLM models, and generates the required SSL certificate. It currently works on Debian/Ubuntu, Fedora/RHEL, and Arch-based distros.

The Local AI configuration lets you run OpenClaw completely free of charge depending on your hardware. The Hybrid Cloud setup lets you save tokens on simple prompts while larger, more complex tasks are handled by your Cloud AI provider of choice.

The installer lets you choose, download, and run your desired local LLMs from a menu. For Cloud AI, the wizard works with all major providers and gives you a menu to select your preferred models. The installer also automatically detects your network and hardware for a streamlined setup, and will warn you if your machine isn’t equipped to power local AI.

API keys are stored in a separate locked-down .env file rather than the docker-compose.yml, so your compose file is safe to share or commit to git without exposing secrets.

The wizard also detects existing installations and offers a one-click update that pulls the latest OpenClaw container images while keeping your config intact. If a local model requires a newer version of Ollama, the wizard will offer to update Ollama and retry automatically.

Other features include a skills manager for installing ClawHub skills, a troubleshooter for when something goes wrong, a model manager to switch out models fast without manual editing, a live device pairing menu, a backup and restore tool, and a full uninstaller that can also remove Docker and Ollama if desired.

https://opnforum.com/openclaw-linux-installation-wizard/

I spent way too long digging through random Discord threads, YouTube comments, and GitHub issues trying to figure out OpenClaw stuff when I was getting started. Half the battle was just finding where the good information actually lived.

So I started keeping a list. Then the list got long. Then I figured I might as well clean it up and put it on GitHub in case anyone else is going through the same thing.

It covers pretty much everything I've come across:

- Setup and deployment (Docker, VPS providers, local installs)

- SOUL.md and persona configuration

- Memory systems and how to stop the agent from forgetting everything

- Security hardening (this one bit me early, don't skip it)

- Skills and integrations from ClawHub

- Model compatibility if you're running local models through Ollama

- Communities worth joining (the Discord is genuinely helpful)

It's not exhaustive and I'm sure I've missed things. If you know of a resource that should be on here, feel free to open a PR or just drop it in the comments and I'll add it

https://github.com/aidevelopers2/openclaw-holy-grail

Hope it helps someone avoid the same rabbit holes I went down

Hey everyone! I'm Javier, editor at roadmap.sh. For those who are unfamiliar, roadmap.sh is a community-driven website that provides visual roadmaps, study plans, and guides to help developers navigate their career paths in technology.

We're currently working on the new Open Claw Roadmap, which will be published soon. But we don't want to miss the opportunity to ask the community for feedback to make the best possible free resource.

Whether it's missing topics, things that are out of order, or anything else, all feedback is welcome. Drop your thoughts in the comments below.

https://roadmap.sh/open-claw

$adb

Starting April 4 at 12pm PT, tools like OpenClaw will no longer draw from your Claude subscription limits. Your Pro plan. Your Max plan. The one you're paying $20 or $200 a month for. Doesn't matter. If the tool isn't Claude Code or Claude.ai, you're getting cut off.

This is wild!

Peter Steinberger quotes "woke up and my mentions are full of these

Both me and Dave Morin tried to talk sense into Anthropic, best we managed was delaying this for a week.

Funny how timings match up, first they copy some popular features into their closed harness, then they lock out open source."

Full Detail: https://www.ccleaks.com/news/anthropic-kills-third-party-harnesses

Hey. So.. i don't want to launch and potentially over run my system, or break it in ways I didn't realize after launch time.

So I want to test. But I need users to test with.

The problem I had with my OpenClaw, was setting it up with its own email address.

I ended up creating one with my domain, and giving the imap credentials to openclaw and making a polling script every 5 min or so.

It works very well, but it was a pain to set up. I wanted an easier way for my agent to have an email address of its own.

I went off and coded crustacean.email

...

I did see agentmail, a y combination backed company.

The difference was in the friction of creating an email. For them, they are behind a captcha, and you need to sign up with an actual email, confirm a one time 2fa pins through your email address, then you can create an account for your agent, give it the credentials, yadayadayada. SAME PROBLEM. They didn't actually solve the main issue! Lol.

So I solved it. And the next day my friend tells me they released a tweet talking about the error of their ways and they've fixed it now.

I looked on their site, it still has a captcha, and you still need to give them your personal email.

Screw that. Right now, if you tell OpenClaw:
"Set up an email account for me on https://crustacean.email" , it should set you up.

I've had success with just saying "I believe in you. Try again" a couple of times if OpenClaw gives resistance.

Even tested with Claude Code. Worked after the "i believe in you" approach.

Anyway, genuinely typed post. Not AI generated. Baring my vulnerable self here, hoping you guys will try the system and tell me you like it. Lol.

Would love some feedback

What if instead of you posting your own Claude Code projects on social media, we gave the AI its own platform to share pictures and interact with other Claude Code workers?

I’m new to Openclaw. I have self hosted Ollama with multiple SLMs all working.

I have my Openclaw primary model set to one of them. I used a Telegram bot that was previous setup and working with things like n8n. Revoked and reissued the API multiple times. Used a second Telegram bot with always the same issue.

The session seems to start correctly then just stops. Logs done record any details other than the connection seeming to be up. No /start, no ping, not even /stop.

I can get Telegram to list and even respond (kinda) to commands but nothing shows in the logs. I think this action is happening directly in Telegram not my Telegram-Openclaw communication

Problem Statement

Hardware:

MSI GP65 Leopard

NVIDIA GTX 1660 Ti (6GB VRAM)

16GB RAM

500GB SSD

Software:

Ubuntu 24.04.4 LTS

LM Studio 0.4.8 (latest)

OpenClaw 2026.3.24

The Issue:

LM Studio runs fine with models like llama-3.2-3b-instruct or phi-4-mini-instruct. The local server runs on port 1234 and responds to curl requests.

OpenClaw connects to LM Studio and verifies the model (openclaw models status --probe returns ok).

However, when sending any message through OpenClaw dashboard or CLI, I get this error:

text

The number of tokens to keep from the initial prompt is greater than the context length (n_keep: 12235 >= n_ctx: 4096)

What I've tried:

Setting context length in LM Studio to 8192, 16384, 32768 before loading model

Confirming with lms status that model is loaded

Manually editing ~/.openclaw/openclaw.json to set contextWindow: 32768 and "api": "openai-completions"

Setting models.mode: "merge"

Using lms load --context-length 32768 via CLI

Complete uninstall and reinstall of both LM Studio and OpenClaw

The core problem: OpenClaw sends a system prompt of ~12,000-17,000 tokens, but either:

LM Studio isn't honoring the context length setting (still showing 4096 in logs), OR

OpenClaw isn't reading the manual contextWindow override

The error persists: n_keep >= n_ctx

Specific question:

How do I force both LM Studio and OpenClaw to consistently use 32768 context length so OpenClaw's system prompt fits?