User
Write something
Connecting OpenRouter to OpenClaw — one command, done
If you're running OpenClaw and haven't connected it to OpenRouter yet, you're either spending more than you need to on API calls or you just haven't tried it yet. OpenRouter lets you route requests across dozens of models (including Qwen 3.6 Plus, which is currently free with a 1M token context) from a single API key. Here's the command to get it set up: openclaw onboard --install-daemon --auth-choice apiKey --token-provider openrouter --token "sk-or-your-key-here" Replace sk-or-your-key-here with your actual OpenRouter API key (grab one at openrouter.ai if you don't have one — takes about 60 seconds). A few things to check if it doesn't work first time: Your key starts with sk-or- — OpenRouter keys have that prefix. OpenAI keys start with sk- and won't work here. OpenClaw is installed globally and current: npm install -g openclaw@latest The daemon has permission to run — on macOS you may need to approve it the first time. Once connected, you can switch models per-command or set Qwen 3.6 Plus as your default to keep costs near zero while you're experimenting. What models are you routing through OpenRouter? Drop yours below — always curious what the community's running for different tasks.
Setting up your first skill in OpenClaw, a 4-step walkthrough
Skills are how you teach OpenClaw to do specific things consistently. Once you've got one wired up, you can call it from any agent, on any channel, with the same predictable behaviour. Here's the fastest way to set up your first one. Step 1. Create the skill directory. Inside your OpenClaw install, head to the skills/ folder and make a new directory named after what your skill does. Keep it lowercase and hyphen-separated. Example: skills/weekly-summary/. Step 2. Add a SKILL.md file. This is the brain of the skill. At the top, drop in YAML frontmatter with at least name and description. The description matters, it's what your agent uses to decide when to trigger the skill, so be specific about the situations it should fire in. Below the frontmatter, write the instructions in plain English. Treat it like a one-page brief for a junior teammate. Step 3. Drop in any helper files. If your skill needs a template, reference doc, or prompt fragment, put it alongside the SKILL.md in the same folder. The agent can pull from anything in there at runtime. Step 4. Reload the daemon. Restart your OpenClaw daemon so it picks up the new directory. The skill should show up in your agent's available toolkit on the next invocation. Once you've built one or two, the pattern becomes muscle memory. ClawHub (clawhub.ai) is also a good place to browse community-built skills for inspiration before rolling your own. What's the first skill you'd want to build for your agent? Drop it below.
How to give your agent memory that survives restarts
If you've been using OpenClaw and noticed your agent forgets everything between sessions, you're missing one of the most useful features in the platform: persistent memory. Out of the box, every conversation starts fresh. The agent doesn't remember your project, your preferences, or what you discussed yesterday. For one-off tasks that's fine. For an agent you actually rely on, it's painful. Here's how to fix it in about 5 minutes. Step 1 — Find your MEMORY.md file Every OpenClaw install has a MEMORY.md file in its config directory. This is where persistent agent knowledge lives across sessions. If you've never edited it, it's probably empty. Step 2 — Add the things your agent should always know Open MEMORY.md and write things like: - Who you are and what you do - - Projects or clients the agent helps with - - Tone and writing style preferences - - Tools, accounts, or services it should know about Plain English works fine. No special syntax needed. Step 3 — Use it Next time you start a session, the agent reads MEMORY.md automatically. Ask it something it should now "remember" — like "what's my tone of voice for client work?" — and you'll see the difference instantly. Step 4 — Update it as you go When you tell your agent something useful, ask it to add that fact to MEMORY.md. Over time you build up an agent that actually knows you, instead of one that resets every morning. This is the single biggest upgrade most people miss. What's the first thing you'd put in your MEMORY.md? Drop it below.
OpenClaw vs Claude Code
So what can you do in OpenClaw that you can't in Claude Code? PS: I'm aware I can ask ChatGPT this question, but it will likely give me outdated answers, given that this is so new.
Why am I getting duplicate messages.
Every chat I send in through the web UI sends as 2 and I receive two responses every time. Any solutions?
1-30 of 59
OpenClaw Users
skool.com/openclawusers
Free community for OpenClaw users to install, build, break, fix and share wild AI agent ideas together.
Leaderboard (30-day)
Powered by