[{"data":1,"prerenderedAt":1880},["ShallowReactive",2],{"blog-post-openclaw-memory-fix":3,"related-posts-openclaw-memory-fix":473},{"id":4,"title":5,"author":6,"body":10,"category":447,"date":448,"description":449,"extension":450,"featured":451,"image":452,"meta":453,"navigation":454,"path":455,"readingTime":456,"seo":457,"seoTitle":458,"stem":459,"tags":460,"updatedDate":471,"__hash__":472},"blog/blog/openclaw-memory-fix.md","OpenClaw Memory Problems: Fix Memory Loss, OOM & Crashes (2026)",{"name":7,"role":8,"avatar":9},"Shabnam Katoch","Growth Head","/img/avatars/shabnam-profile.jpeg",{"type":11,"value":12,"toc":429},"minimark",[13,33,38,41,44,50,53,56,61,64,76,79,86,89,95,102,106,115,122,125,128,131,134,140,147,151,154,159,162,168,172,175,178,182,185,188,194,198,201,210,216,222,228,234,246,250,253,257,260,267,270,273,286,289,297,310,314,317,320,332,335,338,341,349,353,358,361,366,369,374,377,382,385,390,393,397],[14,15,16],"p",{},[17,18,19,20,24,25,28,29,32],"strong",{},"To fix OpenClaw memory loss, set ",[21,22,23],"code",{},"maxContextTokens"," to 80% of your model's limit, pin critical instructions with ",[21,26,27],{},"[PINNED]"," tags, disable automatic context compaction with ",[21,30,31],{},"compactMessageCount: -1",", and mount a persistent volume for Docker deployments. The root cause is GitHub bug #25633 — context compaction silently destroys active work mid-session.",[14,34,35],{},[17,36,37],{},"Your agent didn't forget. OpenClaw threw away its memory while it was still thinking.",[14,39,40],{},"I was three hours into a complex research task. My OpenClaw agent had been browsing competitor pricing pages, compiling data into a structured comparison, and was halfway through a summary when it just... stopped making sense.",[14,42,43],{},"It started repeating itself. Asked me for context I'd already given. Then it confidently summarized data it had never actually collected - hallucinating a competitor's pricing that didn't exist.",[14,45,46,47],{},"I checked the logs. That's when I saw it: ",[21,48,49],{},"Context compaction triggered. Summarizing prior messages.",[14,51,52],{},"OpenClaw had silently decided my context window was too full, compressed everything into a summary, and destroyed the actual data my agent was working with. Three hours of structured research - gone. Replaced by a lossy summary that kept the vibes but lost the facts.",[14,54,55],{},"I thought I'd misconfigured something. Turns out, I'd stumbled into one of the most frustrating open issues in the entire OpenClaw ecosystem.",[57,58,60],"h2",{"id":59},"github-issue-25633-the-bug-report-that-hit-a-nerve","GitHub Issue #25633: The Bug Report That Hit a Nerve",[14,62,63],{},"The issue is titled something innocuous. The reactions tell the real story.",[14,65,66,67,70,71,75],{},"Hundreds of developers reporting the same thing: ",[17,68,69],{},"OpenClaw's context compaction silently destroys active work mid-session."," Not old conversations from last week. Not stale memory files. The thing you're working on ",[72,73,74],"em",{},"right now",".",[14,77,78],{},"Here's what makes this particularly painful. Context compaction isn't a bug in the traditional sense - it's a design decision. When your conversation history gets too large for the model's context window, OpenClaw's runtime compresses older messages into a summary. The idea is sound. The execution is brutal.",[14,80,81,82,85],{},"The compaction algorithm doesn't know what's important to ",[72,83,84],{},"your current task",". It just sees tokens that need trimming. So your carefully structured data table gets compressed into \"the agent collected competitor pricing data.\" Your multi-step instructions get flattened into \"the user asked for a research summary.\"",[14,87,88],{},"The information that made your agent useful? Replaced by a description of that information.",[90,91,92],"blockquote",{},[14,93,94],{},"OpenClaw doesn't lose memory because it forgets. It loses memory because it summarizes - and summaries are lossy by design.",[14,96,97],{},[98,99],"img",{"alt":100,"src":101},"OpenClaw context compaction destroying active agent work mid-session, showing data loss during memory compression","/img/blog/openclaw-context-compaction.jpg",[57,103,105],{"id":104},"how-openclaw-memory-actually-works-and-where-it-falls-apart","How OpenClaw Memory Actually Works (And Where It Falls Apart)",[14,107,108,109,114],{},"To understand why this keeps happening, you need to understand ",[110,111,113],"a",{"href":112},"/blog/how-does-openclaw-work","how OpenClaw's memory architecture works"," under the hood.",[14,116,117,118,121],{},"OpenClaw stores everything as files on disk. Your agent's personality lives in ",[21,119,120],{},"SOUL.md",". Skills are YAML and Markdown files. And memory? Also Markdown files in your workspace directory.",[14,123,124],{},"When you start a conversation, the Agent Runtime assembles a context window. It packs in your system instructions, conversation history, relevant memories, tool schemas, active skills, and workspace rules. All of this gets sent to whatever LLM you've configured - Claude, GPT-4, or one of the 28+ supported providers.",[14,126,127],{},"Here's the problem. Frontier models have large context windows - 100K to 200K tokens. But OpenClaw's context assembly is aggressive. Between the Soul file, skill definitions, tool schemas, and conversation history, you can burn through 50K+ tokens before your agent even starts working on your actual request.",[14,129,130],{},"That leaves less room than you think.",[14,132,133],{},"And when the conversation fills up? Compaction kicks in. Silently.",[14,135,136,139],{},[17,137,138],{},"There's no warning."," No \"hey, I'm about to compress your conversation history.\" No option to choose what gets kept. The runtime just does it. And your agent continues responding as if nothing happened - except now it's working from a summary instead of the actual data.",[14,141,142,143,146],{},"This is the part that drives people crazy. The agent doesn't crash or throw an error. It ",[72,144,145],{},"seems"," fine. It keeps talking confidently. But its outputs are subtly wrong - based on compressed approximations of what it used to know.",[57,148,150],{"id":149},"the-three-ways-your-openclaw-agent-loses-its-mind","The Three Ways Your OpenClaw Agent Loses Its Mind",[14,152,153],{},"Context compaction is the most common culprit, but it's not the only way OpenClaw memory breaks. After spending weeks in the community forums and Discord, I've mapped out three distinct failure modes.",[155,156,158],"h3",{"id":157},"_1-context-compaction-mid-task","1. Context Compaction Mid-Task",[14,160,161],{},"This is GitHub issue #25633. Your agent is actively working, the context window fills up, and the runtime compresses the conversation history. Active data gets summarized. Structured outputs become vague descriptions. Your agent continues operating on degraded information without telling you.",[14,163,164,167],{},[17,165,166],{},"Who it hits hardest:"," Anyone running complex, multi-step tasks. Research workflows. Data analysis. Long coding sessions. Anything where the agent builds up context over time.",[155,169,171],{"id":170},"_2-memory-file-drift","2. Memory File Drift",[14,173,174],{},"OpenClaw's persistent memory lives in Markdown files that get \"compacted\" when the agent decides they're too large. Community member Nat Eliason documented this extensively - he built an elaborate three-layer memory system just to make retention reliable because the default memory pruning kept dropping important context.",[14,176,177],{},"The memory files are inspectable, which is great for transparency. But inspectable also means fragile. One bad compaction pass and your agent's long-term knowledge develops gaps. Worse - you might not notice for days, until the agent makes a decision based on something it no longer remembers correctly.",[155,179,181],{"id":180},"_3-infrastructure-resets","3. Infrastructure Resets",[14,183,184],{},"This one's unique to self-hosted deployments. Docker container restarts, OpenClaw updates, server reboots - any of these can wipe conversation state if your volume mounts aren't configured correctly. Community members on the DigitalOcean 1-Click deployment have reported losing entire agent histories after routine updates, with some noting broken self-update scripts and fragile Docker interaction issues.",[14,186,187],{},"Your memory files might survive on disk. But the active session context - the thing your agent is currently working with - lives in runtime memory. When the process restarts, it's gone.",[14,189,190],{},[98,191],{"alt":192,"src":193},"Three failure modes of OpenClaw memory: context compaction, memory file drift, and infrastructure resets","/img/blog/openclaw-memory-failure-modes.jpg",[57,195,197],{"id":196},"the-community-workarounds-and-why-they-only-get-you-halfway","The Community Workarounds (And Why They Only Get You Halfway)",[14,199,200],{},"The OpenClaw community is nothing if not resourceful. With 850+ contributors and one of the most active Discord servers in open source, people have built impressive workarounds for the memory problem.",[14,202,203,206,207,209],{},[17,204,205],{},"Explicit memory pinning."," Some users write critical information directly into their ",[21,208,120],{}," file - effectively hardcoding important context so it can't be compacted away. This works, but it eats into your base context budget. Every token in SOUL.md is a token not available for your actual conversation.",[14,211,212,215],{},[17,213,214],{},"Reduced skill loading."," Each active skill adds tokens to your context assembly. Users running 15+ skills often hit compaction within minutes. The workaround: only load the skills you need for each session. Effective, but defeats the purpose of having a multi-capable agent.",[14,217,218,221],{},[17,219,220],{},"Shorter sessions."," Some power users deliberately end and restart conversations before compaction triggers, manually carrying over key context. It works. It also turns an autonomous agent into a tool you babysit.",[14,223,224,227],{},[17,225,226],{},"Custom memory architectures."," Nat Eliason's three-layer system - with separate files for short-term, medium-term, and long-term memory - is genuinely clever. But it took him weeks to build and tune, and it's still fighting against OpenClaw's built-in compaction logic.",[14,229,230,231],{},"Every one of these workarounds has the same fundamental problem: ",[17,232,233],{},"you're patching around a design limitation that exists because OpenClaw treats memory as an afterthought.",[14,235,236,237,240,241,245],{},"The file-on-disk approach is beautiful for transparency. You can ",[21,238,239],{},"git diff"," your agent's entire personality. You can inspect every memory in a text editor. But transparency and reliability aren't the same thing. And when you're running an agent for ",[110,242,244],{"href":243},"/blog/best-openclaw-use-cases","real business use cases"," - client communications, daily briefings, project management - \"usually works\" isn't good enough.",[57,247,249],{"id":248},"watch-understanding-openclaws-architecture-and-memory-system","Watch: Understanding OpenClaw's Architecture and Memory System",[14,251,252],{},"If you want to see the full picture of how OpenClaw's Gateway, agent loop, and memory system interact - and why compaction triggers when it does - this 55-minute course from freeCodeCamp walks through the entire architecture. The memory management section starting around the 30-minute mark is particularly relevant to everything we've covered here.",[57,254,256],{"id":255},"the-real-problem-memory-shouldnt-be-your-job","The Real Problem: Memory Shouldn't Be Your Job",[14,258,259],{},"Here's what I kept coming back to while researching this article.",[14,261,262,263,266],{},"Every workaround I found - every custom memory layer, every SOUL.md hack, every session management strategy - required the ",[72,264,265],{},"user"," to manage their agent's memory. You're not just configuring an AI assistant. You're becoming its memory manager, its ops team, and its therapist.",[14,268,269],{},"That's backwards.",[14,271,272],{},"The entire point of an AI agent is that it handles the grunt work so you can focus on decisions. If you're spending 30 minutes per session making sure your agent doesn't forget what it's doing, you're not saving time. You're trading one kind of busy work for another.",[14,274,275,276,280,281,285],{},"Memory issues also compound your ",[110,277,279],{"href":278},"/blog/openclaw-api-costs","API costs"," - every compaction cycle wastes tokens re-establishing context. This is exactly why we built ",[110,282,284],{"href":283},"/","BetterClaw"," with a fundamentally different memory architecture. Instead of relying on Markdown files and hoping compaction doesn't eat your data, BetterClaw uses hybrid vector + keyword search backed by persistent storage that doesn't depend on your container's runtime state.",[14,287,288],{},"Your agent's memory survives restarts. It survives updates. It survives sessions. And because the search is vector-based, your agent doesn't need to stuff everything into the context window - it retrieves what's relevant for the current task, on demand.",[14,290,291,292,296],{},"No manual pinning. No three-layer workarounds. No crossing your fingers every time a long conversation gets deep. If you need ",[110,293,295],{"href":294},"/openclaw-hosting","managed OpenClaw hosting"," with this memory architecture built in, BetterClaw handles it out of the box.",[14,298,299,300,304,305,309],{},"If you've been fighting OpenClaw memory issues and want an agent that actually remembers what it's doing, ",[110,301,303],{"href":302},"/openclaw-alternative","BetterClaw is $29/month per agent"," with persistent memory built in. Already self-hosting? ",[110,306,308],{"href":307},"/migrate","Migrate in under an hour →",". Deploy in 60 seconds. Stop babysitting your agent's brain.",[57,311,313],{"id":312},"what-this-means-if-youre-running-agents-in-production","What This Means If You're Running Agents in Production",[14,315,316],{},"Let me be clear about something: OpenClaw is an extraordinary piece of software. Peter Steinberger built something that made autonomous AI agents accessible to regular developers. The 230,000+ GitHub stars aren't hype - they're earned.",[14,318,319],{},"But the memory architecture was designed for a different era of AI usage. When OpenClaw launched, most interactions were short. Ask a question, get an answer, move on. Context windows were smaller. Sessions were simpler.",[14,321,322,323,326,327,331],{},"Now people are running multi-hour research workflows. Building ",[110,324,325],{"href":243},"business operations around daily agent briefings",". Deploying agents that manage client communications across ",[110,328,330],{"href":329},"/compare/openclaw","multiple chat channels",". The workloads have outgrown the memory system.",[14,333,334],{},"GitHub issue #25633 has significant reactions because it's not an edge case anymore. It's the default experience for anyone pushing OpenClaw beyond simple Q&A.",[14,336,337],{},"The fix isn't a config change. It's an architectural one. And it's coming - the project's move to an open-source foundation with more contributors should accelerate improvements. But if you're running agents in production today, you need a memory system that works today.",[14,339,340],{},"The best agents aren't the ones with the largest context windows. They're the ones that remember the right things at the right time - without you having to manage what \"the right things\" are.",[14,342,343,344,348],{},"If you've been losing work to context compaction, spending hours on memory workarounds, or just tired of your agent forgetting what you told it ten minutes ago - ",[110,345,347],{"href":346},"/pricing","give BetterClaw a try",". $29/month per agent. Persistent memory that actually persists. Deploy in 60 seconds, and spend your time on the work your agent was supposed to handle in the first place.",[57,350,352],{"id":351},"frequently-asked-questions","Frequently Asked Questions",[14,354,355],{},[17,356,357],{},"What is OpenClaw memory and why does it break?",[14,359,360],{},"OpenClaw memory is a file-based system that stores your agent's knowledge as Markdown files on disk and loads conversation history into the LLM's context window. It breaks because of context compaction - when the conversation gets too long, OpenClaw silently summarizes and discards older messages, often destroying active work data in the process. GitHub issue #25633 documents this with significant community reaction.",[14,362,363],{},[17,364,365],{},"How does OpenClaw context compaction work?",[14,367,368],{},"When your conversation history exceeds what fits in the model's context window (after accounting for system instructions, skills, and tool schemas), OpenClaw's runtime automatically compresses older messages into a summary. This happens silently with no user warning. The summary preserves general themes but loses specific data - which is why agents start hallucinating or repeating themselves after compaction triggers.",[14,370,371],{},[17,372,373],{},"How do I fix OpenClaw memory loss in self-hosted deployments?",[14,375,376],{},"Common workarounds include pinning critical information in your SOUL.md file, reducing active skill count to free context space, running shorter sessions to avoid compaction triggers, and building custom multi-layer memory architectures. Each approach has tradeoffs. Managed platforms like BetterClaw solve this architecturally with hybrid vector + keyword search that retrieves relevant memory on demand instead of stuffing everything into the context window.",[14,378,379],{},[17,380,381],{},"Is OpenClaw memory reliable enough for business use?",[14,383,384],{},"With default settings, no. Context compaction can destroy active work mid-session, memory files can drift during pruning, and Docker restarts can wipe session state. For business use, you either need significant custom memory management (weeks of setup and ongoing maintenance) or a managed deployment with persistent memory infrastructure built in. BetterClaw provides this at $29/month per agent with memory that survives restarts, updates, and long sessions.",[14,386,387],{},[17,388,389],{},"How does BetterClaw handle OpenClaw memory differently?",[14,391,392],{},"BetterClaw replaces OpenClaw's default file-based memory with hybrid vector + keyword search backed by persistent storage. Instead of loading all memory into the context window (and compacting when it overflows), BetterClaw retrieves only the relevant memories for each interaction. This means your agent's memory survives container restarts, software updates, and long sessions - without manual pinning, custom architectures, or session babysitting.",[57,394,396],{"id":395},"related-reading","Related Reading",[398,399,400,408,415,422],"ul",{},[401,402,403,407],"li",{},[110,404,406],{"href":405},"/blog/openclaw-oom-errors","OpenClaw OOM Errors: Complete Fix Guide"," — Memory crashes that often trigger the issues described above",[401,409,410,414],{},[110,411,413],{"href":412},"/blog/openclaw-agent-stuck-in-loop","OpenClaw Agent Stuck in Loop: How to Fix It"," — Loops caused by agents losing context after memory compaction",[401,416,417,421],{},[110,418,420],{"href":419},"/blog/openclaw-not-working","OpenClaw Not Working: Every Fix in One Guide"," — Master troubleshooting guide covering all common errors",[401,423,424,428],{},[110,425,427],{"href":426},"/blog/openclaw-setup-guide-complete","OpenClaw Setup Guide: Complete Walkthrough"," — Get your memory configuration right from the start",{"title":430,"searchDepth":431,"depth":431,"links":432},"",2,[433,434,435,441,442,443,444,445,446],{"id":59,"depth":431,"text":60},{"id":104,"depth":431,"text":105},{"id":149,"depth":431,"text":150,"children":436},[437,439,440],{"id":157,"depth":438,"text":158},3,{"id":170,"depth":438,"text":171},{"id":180,"depth":438,"text":181},{"id":196,"depth":431,"text":197},{"id":248,"depth":431,"text":249},{"id":255,"depth":431,"text":256},{"id":312,"depth":431,"text":313},{"id":351,"depth":431,"text":352},{"id":395,"depth":431,"text":396},"Best Practices","2026-02-27","OpenClaw forgetting everything mid-conversation? Context compaction bug #25633 silently destroys your work. Copy these exact config changes to fix it. Tested on v2026.4.x.","md",false,"/img/blog/openclaw-memory-fix.jpg",{},true,"/blog/openclaw-memory-fix","12 min read",{"title":5,"description":449},"OpenClaw Memory Fix: Stop Context Loss and OOM Crashes (2026)","blog/openclaw-memory-fix",[461,462,463,464,465,466,467,468,469,470],"OpenClaw memory","OpenClaw memory fix","OpenClaw memory leak","OpenClaw memory loss","OpenClaw OOM","OpenClaw memory problems","OpenClaw context compaction","OpenClaw crash recovery","OpenClaw persistent memory","OpenClaw GitHub memory","2026-04-02","siJqiP7gH0M9I_c0KmCvrWF29MmkDSWKvQ_XjzFc4nk",[474,978,1469],{"id":475,"title":476,"author":477,"body":478,"category":447,"date":953,"description":954,"extension":450,"featured":454,"image":955,"meta":956,"navigation":454,"path":957,"readingTime":958,"seo":959,"seoTitle":960,"stem":961,"tags":962,"updatedDate":471,"__hash__":977},"blog/blog/best-openclaw-skills.md","15+ Best OpenClaw ClawHub Skills (Tested & Security-Vetted, 2026)",{"name":7,"role":8,"avatar":9},{"type":11,"value":479,"toc":941},[480,485,488,491,494,500,506,509,512,515,519,522,532,538,543,546,549,555,559,562,568,574,580,586,592,598,602,605,611,617,623,629,635,640,646,650,653,659,665,671,676,682,688,692,695,701,707,713,719,723,726,732,738,744,750,755,772,776,779,785,791,796,820,823,829,833,839,842,845,852,858,862,865,868,871,874,877,879,884,895,900,903,908,921,926,929,934,937],[14,481,482],{},[17,483,484],{},"With 5,700+ skills on ClawHub, most people install the wrong ones first. Here are the ones that actually matter, organized by what you're trying to get done. Last verified and updated: March 2026.",[14,486,487],{},"The first skill I ever installed on OpenClaw nearly leaked my Google credentials.",[14,489,490],{},"It had good documentation. Decent stars on ClawHub. The description sounded exactly like what I needed. But buried in the install flow was a dependency pull from an unverified mirror. Nothing flagged it. No warning. I only caught it because I read the source code before running it.",[14,492,493],{},"Most people don't do that.",[14,495,496,497],{},"And here's the uncomfortable truth about ClawHub in March 2026: there are over 5,700 community-built skills on the registry. Security researchers have flagged at least 341 malicious ones. Semgrep's analysis estimates the registry is roughly 10% compromised. That's not a typo. ",[17,498,499],{},"One in ten skills on the most popular AI agent marketplace might be trying to steal your data.",[14,501,502,503],{},"So when you search \"best OpenClaw skills,\" what you're really asking is: ",[72,504,505],{},"which ones can I actually trust, and which ones will make my agent genuinely useful?",[14,507,508],{},"That's what this guide is for.",[14,510,511],{},"We've spent weeks testing, vetting, and running OpenClaw skills across real workflows. Not just poking at them in a sandbox for five minutes. Actually running them in production agent deployments. What follows is our curated, opinionated list organized by what you're actually trying to accomplish.",[14,513,514],{},"But first, a quick refresher on something most guides get wrong.",[57,516,518],{"id":517},"skills-vs-tools-the-distinction-that-saves-you-from-yourself","Skills vs. Tools: The Distinction That Saves You From Yourself",[14,520,521],{},"Before you install anything, understand this:",[14,523,524,527,528,531],{},[17,525,526],{},"Tools are the muscles."," They determine what your agent can do. Read files. Execute commands. Browse the web. These are controlled by the ",[21,529,530],{},"tools.allow"," configuration.",[14,533,534,537],{},[17,535,536],{},"Skills are the playbook."," They teach your agent how to combine tools for specific tasks. The github skill teaches your agent how to manage repos. The obsidian skill teaches it how to organize notes. But without the right tools enabled, skills are just instructions with no hands.",[14,539,540],{},[17,541,542],{},"Key takeaway: Installing a skill does NOT automatically give your agent new permissions. You still control what tools are enabled. This is your primary safety lever. Use it.",[14,544,545],{},"Three conditions must be met for any skill to actually work: the tool must be allowed in config, the required software must be installed on your machine (or in the sandbox), and the skill must be loaded in your workspace. Miss any one of these, and nothing happens.",[14,547,548],{},"Now, let's get into the picks.",[14,550,551],{},[98,552],{"alt":553,"src":554},"OpenClaw skills vs tools diagram showing the distinction between tool permissions and skill playbooks","/img/blog/openclaw-skills-vs-tools.jpg",[57,556,558],{"id":557},"the-productivity-stack-your-agents-daily-operating-system","The Productivity Stack: Your Agent's Daily Operating System",[14,560,561],{},"These are the skills that turn OpenClaw from \"interesting experiment\" into \"I can't work without this.\"",[14,563,564],{},[98,565],{"alt":566,"src":567},"Productivity skills stack overview showing Google Workspace, Notion, Meeting Prep, and Task Prioritizer integrations","/img/blog/openclaw-productivity-stack.jpg",[14,569,570,573],{},[17,571,572],{},"Google Workspace (gog)"," This is the foundational productivity skill and probably the first one you should install. It gives your agent access to Gmail, Google Calendar, Google Docs, and Sheets. The real power shows up when you combine it with the heartbeat scheduler. Set your agent to check your calendar every morning and send you a briefing via WhatsApp before you've had coffee.",[14,575,576,579],{},[72,577,578],{},"Security note:"," This skill gets deep access to your Google account. Scope it carefully. Give read access to your calendar but limit write access to specific documents. Never give blanket Drive access.",[14,581,582,585],{},[17,583,584],{},"Notion Integration"," If your team runs on Notion (and in 2026, who doesn't?), this skill lets your agent create pages, update databases, query project boards, and manage documentation. The sweet spot is pairing it with meeting notes. Your agent joins a call summary, extracts action items, and drops them into your Notion project board. Automatically.",[14,587,588,591],{},[17,589,590],{},"Meeting Prep Agent"," This one changed my workflow more than any other. Before every meeting, it gathers relevant context: calendar details, past notes, related documents, email threads. It assembles a briefing you can skim in 90 seconds. No more scrambling to remember what you discussed last week.",[14,593,594,597],{},[17,595,596],{},"Task Prioritizer"," Uses AI to rank your to-do list based on deadlines, dependencies, and context from your other skills. It's not magic, but it's surprisingly good at surfacing the thing you should be doing right now instead of the thing that feels urgent.",[57,599,601],{"id":600},"the-developer-stack-skills-that-actually-ship-code","The Developer Stack: Skills That Actually Ship Code",[14,603,604],{},"If you're a developer, these are the skills that earn their keep.",[14,606,607],{},[98,608],{"alt":609,"src":610},"Developer skills stack showing GitHub, Cursor CLI, Docker, Vercel, and Sentry integrations for coding workflows","/img/blog/openclaw-developer-stack.jpg",[14,612,613,616],{},[17,614,615],{},"GitHub Integration"," Non-negotiable if you write code. Manage issues, pull requests, repos, and webhooks directly through your agent. The real unlock: set up a webhook listener so your agent gets notified on new PRs and can summarize changes before you review them. Pair it with the heartbeat to get a daily digest of repo activity.",[14,618,619,622],{},[17,620,621],{},"Cursor CLI Agent"," This skill bridges your OpenClaw agent to the Cursor AI coding assistant. If you're already using Cursor for development, this lets you trigger code generation, refactoring, and analysis tasks from any chat channel. Text your agent from Telegram, and it kicks off a Cursor session in the background. Updated for 2026 features with tmux automation support.",[14,624,625,628],{},[17,626,627],{},"Docker Manager"," For DevOps workflows, this skill lets your agent manage Docker containers, images, and compose stacks. Start, stop, inspect, and clean up containers through chat. Particularly useful if you're managing multiple environments and don't want to SSH into a server every time something needs a restart.",[14,630,631,634],{},[17,632,633],{},"Vercel Deployment"," If you deploy to Vercel, this skill turns deployments into conversational commands. Manage environment variables, configure domains, trigger releases. You go from \"I deploy when I decide to\" to \"the system deploys when conditions are met.\"",[14,636,637,639],{},[72,638,578],{}," This gives your agent production deployment rights. Start in a staging environment. Always.",[14,641,642,645],{},[17,643,644],{},"Sentry CLI"," Connects your agent to Sentry for error monitoring. Get notified about new errors through your messaging channels, query error details, and even trigger resolutions. When combined with the GitHub skill, your agent can spot an error, find the relevant PR, and create an issue with full context.",[57,647,649],{"id":648},"the-automation-stack-making-your-agent-proactive","The Automation Stack: Making Your Agent Proactive",[14,651,652],{},"These skills move your agent from reactive (\"do this when I ask\") to proactive (\"do this because you noticed something\").",[14,654,655],{},[98,656],{"alt":657,"src":658},"Automation skills stack showing Cron Job Manager, Web Browser, Tavily Search, and n8n workflow integrations","/img/blog/openclaw-automation-stack.jpg",[14,660,661,664],{},[17,662,663],{},"Cron Job Manager"," Create scheduled tasks using natural language. \"Remind me every Monday at 9 AM to review the sprint board.\" \"Check Hacker News every morning and send me the top 5 AI stories.\" The cron system is one of OpenClaw's most powerful features, and this skill makes it accessible without touching terminal syntax.",[14,666,667,670],{},[17,668,669],{},"Web Browser Automation"," A Rust-based headless browser skill that lets your agent navigate pages, click elements, fill forms, and capture screenshots. This is the backbone of any monitoring or scraping workflow. Want your agent to check competitor pricing every day? This is how.",[14,672,673,675],{},[72,674,578],{}," Browser automation skills can visit any URL your agent encounters. This is a significant prompt injection surface. Sandbox this aggressively.",[14,677,678,681],{},[17,679,680],{},"Tavily Search"," AI-optimized web search that's far more useful than having your agent use a basic search tool. Tavily returns structured, AI-ready results with summaries. Perfect for research tasks, competitive analysis, and keeping your agent informed about topics that matter to you.",[14,683,684,687],{},[17,685,686],{},"n8n Workflow Manager"," If you're running n8n for workflow automation, this skill connects your OpenClaw agent to your n8n instance. Activate workflows, check execution status, trigger manual runs. It turns your agent into a control panel for your entire automation stack.",[57,689,691],{"id":690},"the-smart-home-and-personal-stack","The Smart Home and Personal Stack",[14,693,694],{},"These are the skills that make OpenClaw feel less like a dev tool and more like an actual assistant.",[14,696,697],{},[98,698],{"alt":699,"src":700},"Smart home and personal skills showing Home Assistant, Sonos, and Weather integrations for everyday use","/img/blog/openclaw-smarthome-stack.jpg",[14,702,703,706],{},[17,704,705],{},"Home Assistant Integration"," Control lights, locks, thermostats, and other smart devices through your chat channels. The home automation community has embraced OpenClaw hard, and this skill is one of the most polished in the entire ecosystem. Text your agent to turn off the lights from bed. Or set up a heartbeat that adjusts your thermostat based on your calendar (leaving for work? Lower the heat).",[14,708,709,712],{},[17,710,711],{},"Sonos Control"," Manage your Sonos speakers through your agent. Play, pause, adjust volume, switch rooms. It's simple, but it's also the kind of thing that makes you realize you're living in the future when you text \"play lo-fi in the office\" from the other room.",[14,714,715,718],{},[17,716,717],{},"Weather + Solar"," Real-time weather data and solar weather monitoring. Useful on its own, but powerful when combined with heartbeats. \"If it's going to rain tomorrow, remind me tonight to bring an umbrella.\" Small quality-of-life automation that adds up.",[57,720,722],{"id":721},"the-skills-you-should-not-install-yet","The Skills You Should NOT Install (Yet)",[14,724,725],{},"Here's where we get opinionated.",[14,727,728],{},[98,729],{"alt":730,"src":731},"Warning signs for unsafe OpenClaw skills showing red flags to watch for on ClawHub","/img/blog/openclaw-skills-to-avoid.jpg",[14,733,734,737],{},[17,735,736],{},"Avoid skills from unverified authors with fewer than 100 installs."," The ClawHub registry's vetting process is still immature. Three independent reports can auto-hide a skill, but the removal process is slow. Stick to skills published in the official github.com/openclaw/skills repository or from authors you can verify.",[14,739,740,743],{},[17,741,742],{},"Be cautious with \"self-improving\" or \"auto-evolution\" skills."," Several highly-starred skills claim to make your agent \"continuously enhance its own capabilities.\" That sounds exciting. It's also exactly the kind of recursive, autonomous behavior that's hardest to audit and most likely to surprise you in production.",[14,745,746,749],{},[17,747,748],{},"Skip any skill that asks for broader permissions than its stated purpose."," If a calendar skill wants terminal access, that's a red flag. If a weather skill wants to read your files, walk away. Apply the principle of least privilege to every skill you install.",[14,751,752],{},[17,753,754],{},"Our rule of thumb: if you can't read and understand a skill's SKILL.md and source code in under five minutes, it's either too complex for its stated purpose or doing more than it claims.",[14,756,757,758,762,763,766,767,771],{},"For a full breakdown of every documented security incident, see our ",[110,759,761],{"href":760},"/blog/openclaw-security-risks","OpenClaw security risks guide",". If you're running skills on ",[110,764,765],{"href":346},"BetterClaw's managed OpenClaw platform",", this risk is significantly lower. Every agent runs in a Docker-sandboxed environment with AES-256 encrypted credentials, workspace scoping, and ",[110,768,770],{"href":769},"/#features","real-time health monitoring that auto-pauses on anomalies",". You still choose your skills, but the blast radius of a bad one is contained by default.",[57,773,775],{"id":774},"how-to-install-openclaw-skills-the-right-way","How to Install OpenClaw Skills (The Right Way)",[14,777,778],{},"The process is simple. Doing it safely takes a few extra steps.",[14,780,781,784],{},[17,782,783],{},"Step 1: Search before you install."," Use ClawHub's vector search to describe what you need in plain English. \"I need something that summarizes my emails every morning\" will return better results than keyword searching \"email summarizer.\"",[14,786,787,790],{},[17,788,789],{},"Step 2: Vet before you trust."," Check the skill's install count, last update date, and author. Read the source code. Check the VirusTotal report on the skill's ClawHub page. If anything looks off, skip it.",[14,792,793],{},[17,794,795],{},"Step 3: Install with one command.",[797,798,802],"pre",{"className":799,"code":800,"language":801,"meta":430,"style":430},"language-bash shiki shiki-themes github-light","clawhub install skill-name\n","bash",[21,803,804],{"__ignoreMap":430},[805,806,809,813,817],"span",{"class":807,"line":808},"line",1,[805,810,812],{"class":811},"s7eDp","clawhub",[805,814,816],{"class":815},"sYBdl"," install",[805,818,819],{"class":815}," skill-name\n",[14,821,822],{},"The skill downloads, validates, and activates. Start a new OpenClaw session to pick it up.",[14,824,825,828],{},[17,826,827],{},"Step 4: Scope your permissions."," After installing, review what tools the skill needs and only enable the minimum required. Don't give write access when read access will do. Don't enable exec when the skill only needs web access.",[57,830,832],{"id":831},"the-easier-path-skills-on-betterclaw","The Easier Path: Skills on BetterClaw",[14,834,835],{},[98,836],{"alt":837,"src":838},"BetterClaw managed platform showing secure skill deployment with sandboxed execution and encrypted credentials","/img/blog/betterclaw-skills-deployment.jpg",[14,840,841],{},"Everything we've covered in this article, the vetting, the permission scoping, the sandbox configuration, the tool management, is work you have to do yourself when self-hosting OpenClaw.",[14,843,844],{},"And it's worth doing if you want to learn the system deeply.",[14,846,847,848,851],{},"But if your goal is a production-ready OpenClaw agent with the best skills running securely across your team's chat channels, ",[110,849,850],{"href":283},"BetterClaw handles the infrastructure"," so you can focus on choosing the right skills for your workflow. One-click deploy. Sandboxed execution. Encrypted credentials. $29/month per agent, BYOK.",[14,853,854,855],{},"You pick the skills. We make sure they run safely. Already on self-hosted OpenClaw? ",[110,856,857],{"href":307},"Migrate to BetterClaw in under an hour →",[57,859,861],{"id":860},"start-with-three-then-expand","Start With Three, Then Expand",[14,863,864],{},"The biggest mistake I see new OpenClaw users make is installing 20 skills on day one. Don't do that.",[14,866,867],{},"Start with three. Pick the ones that solve a problem you actually have today. The Google Workspace skill for calendar and email. The GitHub integration if you're a developer. The cron job manager to make your agent proactive.",[14,869,870],{},"Run those for a week. Watch how your agent uses them. Get comfortable with the permission model and the heartbeat system. Then expand from there.",[14,872,873],{},"The best OpenClaw skills aren't the ones with the most stars. They're the ones you use every day without thinking about them. The ones that quietly handle the work you used to do manually. The ones that make you forget your agent is software and start treating it like a teammate.",[14,875,876],{},"That's when things get interesting.",[57,878,352],{"id":351},[14,880,881],{},[17,882,883],{},"What are OpenClaw skills and how do they work?",[14,885,886,887,890,891,894],{},"OpenClaw skills are modular text-based extensions (a ",[21,888,889],{},"SKILL.md"," file plus supporting files) that teach your AI agent how to perform specific tasks. They don't grant new permissions on their own. Skills work by combining the tools already enabled in your agent's configuration. You install them via the ClawHub registry using a single CLI command (",[21,892,893],{},"clawhub install skill-name","), and they activate on your next agent session.",[14,896,897],{},[17,898,899],{},"How do OpenClaw skills compare to ChatGPT plugins or Claude tools?",[14,901,902],{},"The key difference is that OpenClaw skills run locally on your machine and have access to your actual files, apps, and system. ChatGPT plugins and Claude's tools run server-side with limited, sandboxed capabilities. OpenClaw skills can chain together (GitHub webhook triggers a Docker build which triggers a Discord notification), while cloud-based plugins typically operate in isolation. The tradeoff is more power but more security responsibility.",[14,904,905],{},[17,906,907],{},"How do I install OpenClaw skills from ClawHub safely?",[14,909,910,911,914,915,917,918,920],{},"Search ClawHub using the vector search or CLI (",[21,912,913],{},"clawhub search \"what you need\"","), then vet the skill by checking its install count, author, last update, and VirusTotal scan. Install with ",[21,916,893],{},". After installation, scope permissions to the minimum required. For maximum safety, run new skills in a sandbox first. On managed platforms like ",[110,919,284],{"href":329},", sandbox isolation is built in by default.",[14,922,923],{},[17,924,925],{},"Is it worth paying for managed OpenClaw skill deployment?",[14,927,928],{},"If you're running OpenClaw for personal experimentation, self-hosting is fine and free. If you're running it for a team or business, the time spent on security auditing, permission management, Docker configuration, and monitoring adds up fast. BetterClaw at $29/month per agent includes sandboxed execution, encrypted credentials, and auto-pause monitoring, which effectively replaces hours of weekly ops work.",[14,930,931],{},[17,932,933],{},"Are OpenClaw ClawHub skills secure enough for business use?",[14,935,936],{},"Not all of them. Security researchers have identified hundreds of malicious skills on ClawHub, and the vetting process is still maturing. For business use, stick to official bundled skills and well-known community skills with high install counts and recent updates. Always review source code, apply least-privilege permissions, and run skills in sandboxed environments. Managed platforms like BetterClaw add enterprise-grade security layers (AES-256 encryption, Docker isolation, workspace scoping) that significantly reduce risk.",[938,939,940],"style",{},"html pre.shiki code .s7eDp, html code.shiki .s7eDp{--shiki-default:#6F42C1}html pre.shiki code .sYBdl, html code.shiki .sYBdl{--shiki-default:#032F62}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":430,"searchDepth":431,"depth":431,"links":942},[943,944,945,946,947,948,949,950,951,952],{"id":517,"depth":431,"text":518},{"id":557,"depth":431,"text":558},{"id":600,"depth":431,"text":601},{"id":648,"depth":431,"text":649},{"id":690,"depth":431,"text":691},{"id":721,"depth":431,"text":722},{"id":774,"depth":431,"text":775},{"id":831,"depth":431,"text":832},{"id":860,"depth":431,"text":861},{"id":351,"depth":431,"text":352},"2026-03-27","10% of ClawHub skills are compromised. These 15 passed our security audit and actually work. Ranked by category: productivity, dev tools, automation, smart home. One-line installs.","/img/blog/best-openclaw-skills.jpg",{},"/blog/best-openclaw-skills","15 min read",{"title":476,"description":954},"15 Best OpenClaw Skills on ClawHub (April 2026, Security Tested)","blog/best-openclaw-skills",[963,964,965,966,967,968,969,970,971,972,973,974,975,976],"best OpenClaw skills","best OpenClaw skills ClawHub 2026","best ClawHub skills 2026","OpenClaw skills to install","top OpenClaw ClawHub skills","popular OpenClaw skills","recommended OpenClaw skills","OpenClaw developer skills","OpenClaw productivity skills","OpenClaw skills list March 2026","safest OpenClaw skills","OpenClaw skills security vetted","OpenClaw GitHub skill","OpenClaw Google Workspace skill","iFvqRFBlMId_kiB-RoFyFYdEjloyr9yG6faKHaEekCs",{"id":979,"title":980,"author":981,"body":982,"category":447,"date":1451,"description":1452,"extension":450,"featured":451,"image":1453,"meta":1454,"navigation":454,"path":1455,"readingTime":958,"seo":1456,"seoTitle":1457,"stem":1458,"tags":1459,"updatedDate":1451,"__hash__":1468},"blog/blog/cheapest-openclaw-ai-providers.md","Cheapest OpenClaw AI Providers: 5 Alternatives to OpenAI That Cut Costs 80%",{"name":7,"role":8,"avatar":9},{"type":11,"value":983,"toc":1439},[984,989,992,995,998,1001,1004,1011,1014,1018,1021,1024,1027,1030,1033,1040,1046,1050,1056,1062,1065,1068,1078,1081,1084,1090,1094,1099,1102,1105,1108,1111,1114,1120,1124,1129,1132,1135,1138,1141,1147,1153,1160,1164,1169,1172,1175,1190,1199,1206,1209,1215,1226,1230,1235,1238,1244,1255,1261,1268,1274,1278,1281,1284,1288,1291,1298,1301,1307,1316,1321,1328,1332,1335,1341,1347,1356,1368,1371,1377,1386,1388,1393,1396,1401,1404,1409,1423,1428,1431,1436],[14,985,986],{},[72,987,988],{},"Your OpenClaw agent doesn't need GPT-4o for everything. Here are the providers that cost a fraction and work just as well.",[14,990,991],{},"My OpenAI dashboard showed $147. Fourteen days. One agent.",[14,993,994],{},"I'd set up my OpenClaw instance on a Friday, pointed it at GPT-4o because that's what every tutorial recommended, and let it run. Morning briefings. Email triage. Calendar management. A few research tasks. Nothing exotic.",[14,996,997],{},"Two weeks later, $147. For an AI assistant that mostly checked my calendar and summarized emails.",[14,999,1000],{},"I pulled up the token logs and did the math. GPT-4o at $2.50 per million input tokens and $10 per million output tokens sounds reasonable in isolation. But OpenClaw agents are hungry. Heartbeats every 30 minutes. Sub-agents spawning for parallel tasks. Context windows that grow silently as cron jobs accumulate history.",[14,1002,1003],{},"The tokens add up. Fast.",[14,1005,1006,1007,1010],{},"Here's the thing: the ",[17,1008,1009],{},"cheapest OpenClaw AI provider isn't always the worst one",". In 2026, there are models that cost 90% less than GPT-4o and perform just as well for the kind of work most agents actually do. Some of them are better at tool calling. Some have larger context windows. One of them is literally free.",[14,1012,1013],{},"This is the guide I wish I'd read before handing OpenAI $147 for two weeks of calendar checks.",[57,1015,1017],{"id":1016},"why-openai-is-the-default-and-why-thats-costing-you","Why OpenAI is the default (and why that's costing you)",[14,1019,1020],{},"OpenAI is the default recommendation in most OpenClaw tutorials for a simple reason: familiarity. Everyone has an OpenAI account. The API is well-documented. GPT-4o is genuinely good.",[14,1022,1023],{},"But \"good\" and \"cost-effective for an always-on agent\" are very different things.",[14,1025,1026],{},"OpenClaw agents don't work like a ChatGPT conversation. They run continuously. They process heartbeats (periodic status checks) every 30 minutes using your primary model. They spawn sub-agents for parallel work. They execute skills that require multiple model calls per task.",[14,1028,1029],{},"A single browser automation task can consume 50-200+ steps, with each step using 500-2,000 tokens. At GPT-4o pricing, that's $0.50-2.00 per complex task. Run a few of those daily and your monthly bill climbs past $100 easily.",[14,1031,1032],{},"The viral Medium post \"I Spent $178 on AI Agents in a Week\" captured this pain perfectly. Most of that spend was GPT-4o running tasks that didn't need GPT-4o.",[14,1034,1035,1036,1039],{},"For a deeper look at where OpenClaw API costs actually come from (and how they compound faster than you'd expect), we wrote a ",[110,1037,1038],{"href":278},"complete breakdown of OpenClaw API costs"," with real monthly projections.",[14,1041,1042],{},[98,1043],{"alt":1044,"src":1045},"OpenClaw API cost breakdown showing GPT-4o token usage across heartbeats, sub-agents, and daily tasks","/img/blog/openclaw-136k-token-overhead-1.jpg",[57,1047,1049],{"id":1048},"_1-anthropic-claude-the-agent-first-provider","1. Anthropic Claude: The agent-first provider",[14,1051,1052,1055],{},[17,1053,1054],{},"Pricing:"," Haiku 4.5: $1/$5 | Sonnet 4.6: $3/$15 | Opus 4.6: $5/$25 (per million tokens, input/output)",[14,1057,1058,1059,75],{},"Claude isn't cheaper than GPT-4o across the board. Sonnet at $3/$15 is actually more expensive per output token. But here's why it's on this list: ",[17,1060,1061],{},"Claude is better at the specific things OpenClaw agents need to do",[14,1063,1064],{},"Tool calling reliability. Long-context accuracy. Prompt injection resistance. Multi-step instruction following. These are the areas where OpenClaw community benchmarks consistently rank Claude above GPT-4o.",[14,1066,1067],{},"The real savings come from Haiku 4.5 at $1/$5. That's 60% cheaper than GPT-4o on input and 50% cheaper on output. And for heartbeats, calendar lookups, simple queries, and sub-agent tasks, Haiku handles them beautifully.",[14,1069,1070,1073,1074,1077],{},[17,1071,1072],{},"The smart setup:"," Sonnet as your primary model, Haiku for heartbeats and sub-agents, Opus available via ",[21,1075,1076],{},"/model opus"," for complex reasoning when you need it. This tiered approach typically costs $40-70/month compared to $100-200 with GPT-4o for everything.",[14,1079,1080],{},"Claude isn't the cheapest option. It's the option where you get the most capability per dollar on agent-specific tasks.",[14,1082,1083],{},"OpenClaw's founder, Peter Steinberger, recommended Anthropic models before joining OpenAI. That recommendation still holds for most serious agent workloads.",[14,1085,1086],{},[98,1087],{"alt":1088,"src":1089},"Claude model tiers showing Haiku, Sonnet, and Opus pricing with recommended OpenClaw task assignments","/img/blog/openclaw-routing-tiers.jpg",[57,1091,1093],{"id":1092},"_2-deepseek-the-028-option-that-actually-works","2. DeepSeek: The $0.28 option that actually works",[14,1095,1096,1098],{},[17,1097,1054],{}," DeepSeek V3.2: $0.28/$0.42 per million tokens (input/output)",[14,1100,1101],{},"This is where the cost math gets wild.",[14,1103,1104],{},"DeepSeek V3.2 costs roughly 10x less than GPT-4o on input tokens and 24x less on output tokens. For an always-on OpenClaw agent, that difference compounds dramatically. A workload that costs $150/month on GPT-4o drops to approximately $15-20/month on DeepSeek.",[14,1106,1107],{},"And it's not a toy model. Community reports from the OpenClaw GitHub discussions consistently mention DeepSeek alongside Claude as the two providers that work best for agent tasks. It's particularly strong at code generation and debugging.",[14,1109,1110],{},"The tradeoffs are real though. DeepSeek's tool calling is less reliable than Claude's on complex multi-step chains. Context tracking over very long conversations can degrade. And if you're processing sensitive data, the provider routes through Chinese infrastructure, which matters for some use cases.",[14,1112,1113],{},"For pure cost optimization on non-sensitive tasks, DeepSeek is hard to beat. Set it as your heartbeat and sub-agent model while keeping a more capable model as your primary, and your bill drops by 70-80%.",[14,1115,1116],{},[98,1117],{"alt":1118,"src":1119},"DeepSeek V3.2 cost comparison against GPT-4o and Claude showing 10-24x savings per million tokens","/img/blog/cheapest-openclaw-deepseek-comparison.jpg",[57,1121,1123],{"id":1122},"_3-google-gemini-free-tier-thats-surprisingly-capable","3. Google Gemini: Free tier that's surprisingly capable",[14,1125,1126,1128],{},[17,1127,1054],{}," Gemini 2.5 Flash free tier: $0 (1,500 requests/day) | Paid: $0.075/$0.30 per million tokens",[14,1130,1131],{},"Yes, free. Google AI Studio offers a free tier for Gemini 2.5 Flash with 1,500 requests per day and a 1 million token context window. No credit card required.",[14,1133,1134],{},"For personal OpenClaw use (morning briefings, calendar management, basic research), the free tier is often enough. 1,500 requests per day is surprisingly generous for a single-user agent.",[14,1136,1137],{},"Even the paid tier at $0.075 per million input tokens is absurdly cheap. That's 33x cheaper than GPT-4o. A moderate usage pattern that costs $100/month on OpenAI costs roughly $3 on Gemini Flash.",[14,1139,1140],{},"The limitation: Gemini's tool calling isn't as reliable as Claude or even GPT-4o for complex chains. It handles straightforward tasks well but can stumble on multi-step reasoning that requires precise instruction following.",[14,1142,1143,1146],{},[17,1144,1145],{},"Best used for:"," heartbeats, simple lookups, data parsing, and as a fallback model. Not recommended as your sole primary model for complex agent workflows.",[14,1148,1149],{},[98,1150],{"alt":1151,"src":1152},"Google Gemini free tier details showing 1500 daily requests and 1M token context window for OpenClaw","/img/blog/cheapest-openclaw-gemini-free.jpg",[14,1154,1155,1156,1159],{},"To understand which tasks need a powerful model versus which tasks can run on something cheap, our guide to ",[110,1157,1158],{"href":112},"how OpenClaw works under the hood"," explains the agent architecture and where model calls actually happen.",[57,1161,1163],{"id":1162},"_4-openrouter-one-api-key-200-models-automatic-routing","4. OpenRouter: One API key, 200+ models, automatic routing",[14,1165,1166,1168],{},[17,1167,1054],{}," Varies by model (typically 0-5% markup over direct provider pricing)",[14,1170,1171],{},"OpenRouter isn't a model provider. It's a routing layer. One API key gives you access to 200+ models across every major provider, and you can switch between them without managing separate API keys for each.",[14,1173,1174],{},"Here's why that matters for OpenClaw.",[14,1176,1177,1178,1181,1182,1185,1186,1189],{},"The ",[21,1179,1180],{},"/model"," command lets you switch models mid-conversation. With OpenRouter, you type ",[21,1183,1184],{},"/model deepseek/deepseek-v3.2"," and you're on DeepSeek. ",[21,1187,1188],{},"/model anthropic/claude-sonnet-4.6"," switches to Claude. No config file edits. No gateway restarts.",[14,1191,1192,1198],{},[110,1193,1197],{"href":1194,"rel":1195},"https://www.youtube.com/results?search_query=openclaw+openrouter+setup+model+switching+2026",[1196],"nofollow","Watch on YouTube: OpenClaw Multi-Model Setup with OpenRouter"," (Community content)\nIf you want to see how OpenRouter's model switching works in practice with OpenClaw (including the auto-routing feature that selects the cheapest capable model per request), this community walkthrough covers the full configuration and real-time cost comparison.",[14,1200,1201,1202,1205],{},"But the real savings feature is ",[21,1203,1204],{},"openrouter/auto",". Set this as your model and OpenRouter automatically routes each request to the most cost-effective model based on the complexity of the prompt. Simple heartbeats go to cheap models. Complex reasoning gets routed to capable ones. You save money without manually managing model tiers.",[14,1207,1208],{},"The tradeoff: a small markup on token prices (typically under 5%), and you're adding a routing layer which occasionally introduces latency. For most users, the convenience of one API key and automatic cost optimization is worth it.",[14,1210,1211],{},[98,1212],{"alt":1213,"src":1214},"OpenRouter auto-routing diagram showing automatic model selection based on task complexity","/img/blog/cheapest-openclaw-openrouter-routing.jpg",[14,1216,1217,1218,1221,1222,1225],{},"If you don't want to think about model routing at all, if you want automatic cost optimization with zero configuration and built-in anomaly detection that pauses your agent before costs spiral, ",[110,1219,1220],{"href":283},"Better Claw handles all of this"," at ",[110,1223,1224],{"href":346},"$29/month per agent",". BYOK, 60-second deploy, and you can point it at any of these providers.",[57,1227,1229],{"id":1228},"_5-ollama-local-models-0-per-month-forever","5. Ollama (local models): $0 per month, forever",[14,1231,1232,1234],{},[17,1233,1054],{}," $0 API cost. Hardware and electricity only.",[14,1236,1237],{},"Running models locally through Ollama eliminates API costs entirely. Llama 3.3 70B, Mistral, Qwen 2.5: they all run on your machine, fully private, with no token charges.",[14,1239,1240,1243],{},[17,1241,1242],{},"The math:"," A Mac Mini M4 with 16GB RAM runs 7-8B models at 15-20 tokens per second. That's fast enough for most agent tasks. Larger models (30B+) need more RAM or a dedicated GPU.",[14,1245,1246,1247,1250,1251,1254],{},"For OpenClaw specifically, the ",[21,1248,1249],{},"hermes-2-pro"," and ",[21,1252,1253],{},"mistral:7b"," models are recommended for tool calling reliability. They're not Claude or GPT-4o, but for heartbeats, simple queries, and privacy-sensitive operations, they're genuinely useful.",[14,1256,1257,1260],{},[17,1258,1259],{},"The honest reality:"," local models in 2026 still can't match cloud providers on complex multi-step reasoning, long-context accuracy, or sophisticated tool use. The community consensus in OpenClaw's GitHub discussions is clear: local models work for experimentation and privacy-first setups, but cloud models are better for production agent workflows.",[14,1262,1263,1264,75],{},"The sweet spot is hybrid: local models for heartbeats and simple tasks, cloud models for complex reasoning. OpenClaw supports this natively through its ",[110,1265,1267],{"href":1266},"/blog/openclaw-model-routing","model routing configuration",[14,1269,1270],{},[98,1271],{"alt":1272,"src":1273},"Ollama local model setup showing zero API cost with hardware requirements for different model sizes","/img/blog/cheapest-openclaw-ollama-local.jpg",[57,1275,1277],{"id":1276},"the-provider-nobody-talks-about-minimax","The provider nobody talks about: MiniMax",[14,1279,1280],{},"Quick honorable mention. MiniMax offers a $10/month plan with 100 prompts every 5 hours. Peter Steinberger himself recommended it during community discussions. It's not on the level of Opus, but community members describe it as \"competent enough for most tasks.\"",[14,1282,1283],{},"For budget-conscious users who want a flat monthly rate instead of per-token billing, it's worth testing. The predictability alone can be valuable when you're worried about runaway agent costs.",[57,1285,1287],{"id":1286},"the-real-problem-isnt-the-provider-its-the-architecture","The real problem isn't the provider. It's the architecture.",[14,1289,1290],{},"Here's what I've learned after months of optimizing OpenClaw costs across different providers.",[14,1292,1293,1294,1297],{},"Switching from GPT-4o to DeepSeek saves you money. Setting up ",[110,1295,1296],{"href":1266},"model routing"," (different models for different task types) saves you more. But the biggest cost driver in OpenClaw isn't the per-token price. It's uncontrolled context growth.",[14,1299,1300],{},"Cron jobs accumulate context indefinitely. A task scheduled to check emails every 5 minutes eventually builds a 100,000-token context window. What starts at $0.02 per execution grows to $2.00 per execution regardless of which provider you use.",[14,1302,1177,1303,1306],{},[110,1304,1305],{"href":455},"memory compaction bug in OpenClaw"," makes this worse. Context compaction can kill active work mid-session, and the workarounds require manual token limits in every skill config.",[14,1308,1309,1310,1250,1312,1315],{},"Set ",[21,1311,23],{},[21,1313,1314],{},"maxIterations"," in your skill configurations. Set daily spending caps on OpenRouter or your provider's dashboard. Monitor your token usage weekly. These operational habits matter more than which provider you choose.",[14,1317,1318],{},[17,1319,1320],{},"The cheapest provider in the world can't save you from a runaway agent loop burning tokens at 3 AM.",[14,1322,1323,1324,1327],{},"For a look at what tasks are worth running through a premium model versus which ones can safely run on the cheapest option available, our guide to the ",[110,1325,1326],{"href":243},"best OpenClaw use cases"," ranks workflows by complexity and cost.",[57,1329,1331],{"id":1330},"pick-your-fighter-a-practical-recommendation","Pick your fighter (a practical recommendation)",[14,1333,1334],{},"For most people reading this, here's what I'd actually recommend:",[14,1336,1337,1340],{},[17,1338,1339],{},"If you're just starting out:"," Gemini 2.5 Flash free tier. Zero risk. Learn how OpenClaw works without spending anything. Upgrade to a paid provider when you outgrow the free limits.",[14,1342,1343,1346],{},[17,1344,1345],{},"If you want the best quality-to-cost ratio:"," Claude Sonnet 4.6 as primary, Haiku 4.5 for heartbeats and sub-agents. This is what most serious OpenClaw users run. Expect $40-70/month.",[14,1348,1349,1352,1353,1355],{},[17,1350,1351],{},"If cost is the priority:"," DeepSeek V3.2 for everything except complex reasoning. Use Claude or GPT-4o on-demand via ",[21,1354,1180],{}," for the hard stuff. Expect $15-30/month.",[14,1357,1358,1361,1362,1221,1365,1367],{},[17,1359,1360],{},"If you don't want to think about any of this:"," OpenRouter auto-routing, or ",[110,1363,1364],{"href":283},"Better Claw",[110,1366,1224],{"href":346}," with BYOK and zero-config deployment.",[14,1369,1370],{},"The AI model market is getting cheaper every quarter. Opus 4.5 at $5/$25 is 66% cheaper than Opus 4.1 was at $15/$75. The trend is clear. But until prices hit zero (they won't), smart provider selection and model routing are the most impactful cost levers you have.",[14,1372,1373,1376],{},[17,1374,1375],{},"Stop paying GPT-4o prices for calendar checks."," Your agent will work just as well. Your wallet will thank you.",[14,1378,1379,1380,1385],{},"If you've been wrestling with API costs, config files, and model routing, and you'd rather just deploy an agent that works, ",[110,1381,1384],{"href":1382,"rel":1383},"https://app.betterclaw.io/sign-in",[1196],"give Better Claw a try",". It's $29/month per agent, BYOK with any of the providers above, and your first agent deploys in about 60 seconds. We handle the infrastructure, the model routing, and the cost monitoring. You focus on building workflows.",[57,1387,352],{"id":351},[14,1389,1390],{},[17,1391,1392],{},"What are the cheapest AI providers for OpenClaw agents?",[14,1394,1395],{},"The cheapest cloud providers for OpenClaw in 2026 are DeepSeek V3.2 at $0.28/$0.42 per million tokens and Google Gemini 2.5 Flash at $0.075/$0.30 (with a free tier offering 1,500 requests per day). For zero-cost operation, Ollama lets you run local models like Llama 3.3 and Mistral with no API charges. Claude Haiku 4.5 at $1/$5 offers the best balance of low cost and agent-specific reliability.",[14,1397,1398],{},[17,1399,1400],{},"How does Claude compare to GPT-4o for OpenClaw?",[14,1402,1403],{},"Claude models (particularly Sonnet and Haiku) consistently outperform GPT-4o on the tasks that matter most for OpenClaw: tool calling reliability, long-context accuracy, and prompt injection resistance. GPT-4o is faster on simple tasks and has broader community support. Claude Sonnet 4.6 at $3/$15 is more expensive per output token than GPT-4o at $2.50/$10, but the improved agent performance often means fewer retries and lower total cost.",[14,1405,1406],{},[17,1407,1408],{},"How do I switch AI providers in OpenClaw?",[14,1410,1411,1412,1415,1416,1418,1419,1422],{},"Edit your ",[21,1413,1414],{},"~/.openclaw/openclaw.json"," file to change the model provider and API key, then restart your gateway. For quick switching mid-conversation, use the ",[21,1417,1180],{}," command (for example, ",[21,1420,1421],{},"/model anthropic/claude-sonnet-4-6","). OpenRouter simplifies this further by giving you one API key for 200+ models. The switch takes seconds and doesn't require reinstallation.",[14,1424,1425],{},[17,1426,1427],{},"How much does it cost to run an OpenClaw agent per month?",[14,1429,1430],{},"Monthly costs vary by provider and usage: $80-200 with GPT-4o for everything, $40-70 with Claude Sonnet plus Haiku routing, $15-30 with DeepSeek for most tasks, or $0-5 with Gemini free tier or local models. These are API costs only. Hosting adds $5-29/month depending on whether you self-host on a VPS or use a managed platform like Better Claw. BYOK means you control the API spend regardless of hosting.",[14,1432,1433],{},[17,1434,1435],{},"Is DeepSeek reliable enough for production OpenClaw agents?",[14,1437,1438],{},"DeepSeek V3.2 is reliable for most standard agent tasks and excels at code generation. Community reports confirm it works well for daily operations. The tradeoffs: tool calling can be less precise than Claude on complex multi-step chains, and data routes through Chinese infrastructure, which matters for sensitive workloads. For heartbeats, sub-agents, and non-sensitive tasks, it's a solid budget choice. For critical workflows, pair it with a more capable model as your primary.",{"title":430,"searchDepth":431,"depth":431,"links":1440},[1441,1442,1443,1444,1445,1446,1447,1448,1449,1450],{"id":1016,"depth":431,"text":1017},{"id":1048,"depth":431,"text":1049},{"id":1092,"depth":431,"text":1093},{"id":1122,"depth":431,"text":1123},{"id":1162,"depth":431,"text":1163},{"id":1228,"depth":431,"text":1229},{"id":1276,"depth":431,"text":1277},{"id":1286,"depth":431,"text":1287},{"id":1330,"depth":431,"text":1331},{"id":351,"depth":431,"text":352},"2026-03-10","Stop overpaying for OpenClaw. DeepSeek at $0.28, Gemini free tier, Claude Haiku at $1. Five providers that cut your agent costs 50-90%.","/img/blog/cheapest-openclaw-ai-providers.jpg",{},"/blog/cheapest-openclaw-ai-providers",{"title":980,"description":1452},"5 Cheapest OpenClaw AI Providers (Save 80% vs OpenAI)","blog/cheapest-openclaw-ai-providers",[1460,1461,1462,1463,1464,1465,1466,1467],"cheapest OpenClaw AI provider","OpenClaw API costs","OpenClaw DeepSeek","OpenClaw Claude vs GPT","OpenRouter OpenClaw","reduce OpenClaw spending","OpenClaw model pricing","cheap AI agent hosting","Tn0D4W_7li98DRFGmX1caPGDxXWL0iclMIDGD5TlHj0",{"id":1470,"title":1471,"author":1472,"body":1473,"category":447,"date":1862,"description":1863,"extension":450,"featured":451,"image":1864,"meta":1865,"navigation":454,"path":1866,"readingTime":1867,"seo":1868,"seoTitle":1869,"stem":1870,"tags":1871,"updatedDate":1862,"__hash__":1879},"blog/blog/how-to-update-openclaw.md","How to Update OpenClaw Without Breaking Your Setup",{"name":7,"role":8,"avatar":9},{"type":11,"value":1474,"toc":1843},[1475,1480,1483,1486,1489,1492,1496,1499,1502,1505,1508,1511,1518,1522,1525,1529,1543,1547,1553,1557,1560,1570,1576,1580,1583,1586,1592,1595,1599,1602,1608,1619,1625,1631,1638,1642,1645,1649,1652,1658,1662,1665,1679,1683,1686,1691,1698,1702,1705,1708,1711,1714,1717,1720,1726,1730,1733,1736,1739,1745,1751,1754,1761,1763,1768,1778,1783,1786,1791,1794,1799,1802,1807,1810,1812],[14,1476,1477],{},[72,1478,1479],{},"Last time you updated, your cron jobs vanished. This time, you'll back up first, update safely, and know exactly how to roll back if anything goes wrong.",[14,1481,1482],{},"I updated OpenClaw on a Tuesday afternoon. By Tuesday evening, my customer support agent had stopped responding on Telegram, three cron jobs had silently deactivated, and my gateway was binding to a different port than before.",[14,1484,1485],{},"The update itself took 30 seconds. The debugging took four hours. The worst part: I could have prevented all of it with a 5-minute backup before hitting the update command.",[14,1487,1488],{},"OpenClaw releases multiple updates per week. Some are minor fixes. Some change config behavior without clear documentation. With 7,900+ open issues on GitHub and the project transitioning to an open-source foundation after Peter Steinberger's move to OpenAI, the pace of change is high and the communication about breaking changes is inconsistent.",[14,1490,1491],{},"Here's how to update OpenClaw safely every time. Bookmark this page. You'll need it again.",[57,1493,1495],{"id":1494},"check-your-current-version-first","Check your current version first",[14,1497,1498],{},"Before you update anything, know what version you're running right now. This matters for two reasons.",[14,1500,1501],{},"First, if something breaks after the update, you need to know which version to roll back to. If you don't know your current version, you can't roll back precisely. You're guessing.",[14,1503,1504],{},"Second, the changelog between your current version and the latest version tells you what changed. If a breaking change happened between your version and the new one, you'll know before you update instead of discovering it through broken behavior.",[14,1506,1507],{},"Run the version check command in your terminal. OpenClaw will report its current version number. Write it down or screenshot it. You'll need this if rollback becomes necessary.",[14,1509,1510],{},"Also check which version is the latest available. Compare the two. If you're one version behind, the risk is low. If you're ten versions behind, read the changelogs for each version in between. Multiple small breaking changes stack up.",[14,1512,1513,1514,1517],{},"For the ",[110,1515,1516],{"href":426},"complete OpenClaw setup sequence and where updates fit",", our setup guide covers the full installation and configuration flow.",[57,1519,1521],{"id":1520},"back-up-these-three-things-before-you-update","Back up these three things before you update",[14,1523,1524],{},"This takes 5 minutes. It saves hours of debugging if something goes wrong.",[155,1526,1528],{"id":1527},"your-personality-and-memory-files","Your personality and memory files",[14,1530,1531,1532,1534,1535,1538,1539,1542],{},"Copy your ",[21,1533,120],{},", ",[21,1536,1537],{},"MEMORY.md",", and ",[21,1540,1541],{},"USER.md"," (if it exists) to a safe location outside the OpenClaw directory. These files define your agent's personality, accumulated knowledge, and user preferences. They're the files you've spent the most time crafting. Losing them means recreating your agent's personality from scratch.",[155,1544,1546],{"id":1545},"your-config-file","Your config file",[14,1548,1531,1549,1552],{},[21,1550,1551],{},"openclaw.json"," (or wherever your configuration lives) to the same backup location. This file contains your model providers, API credentials, channel connections, gateway settings, and every customization you've made. If the update changes config key names or structure, you'll need the original to compare and migrate.",[155,1554,1556],{"id":1555},"your-installed-skills-list","Your installed skills list",[14,1558,1559],{},"Note which skills you have installed and where they came from. After an update, skills can go inactive or need reinstallation. If you don't know which skills you had, you won't notice they're missing until the agent fails to perform a task it used to handle fine.",[14,1561,1562,1563,1534,1565,1534,1567,1569],{},"The 5-minute backup rule: copy ",[21,1564,120],{},[21,1566,1537],{},[21,1568,1541],{},", and your config file to a separate folder before every update. This single habit prevents 90% of update disasters.",[14,1571,1572],{},[98,1573],{"alt":1574,"src":1575},"OpenClaw update backup checklist showing SOUL.md, MEMORY.md, USER.md, and config file in a safe location","/img/blog/how-to-update-openclaw-backup.jpg",[57,1577,1579],{"id":1578},"the-actual-update-process","The actual update process",[14,1581,1582],{},"Once you've backed up, the update itself is straightforward.",[14,1584,1585],{},"Run the npm global update command for OpenClaw. This pulls the latest version and replaces the OpenClaw binary. The process typically takes 30-60 seconds depending on your internet speed.",[14,1587,1588,1591],{},[17,1589,1590],{},"What \"success\" looks like:"," The terminal shows the new version number with no error messages. If you see warnings about deprecated dependencies, those are usually harmless. If you see actual errors (permission denied, EACCES, npm ERR!), the update didn't complete and you're still on the old version.",[14,1593,1594],{},"After the update completes, restart your gateway. The new version only takes effect after a gateway restart. If you update but don't restart, you're running the old code with the new binary sitting idle.",[57,1596,1598],{"id":1597},"what-to-check-immediately-after-updating","What to check immediately after updating",[14,1600,1601],{},"Don't assume the update worked just because the terminal didn't show errors. Check three things within the first 5 minutes.",[14,1603,1604,1607],{},[17,1605,1606],{},"Is your agent responding?"," Send a test message through your primary channel (Telegram, WhatsApp, whatever you use). If the agent responds normally, the core system is working.",[14,1609,1610,1613,1614,1250,1616,1618],{},[17,1611,1612],{},"Are your memory files intact?"," Check that ",[21,1615,120],{},[21,1617,1537],{}," are still present and contain the expected content. Some updates have been reported to reset or modify these files. If they've changed, restore from your backup.",[14,1620,1621,1624],{},[17,1622,1623],{},"Are your skills still installed and active?"," Ask your agent to perform a task that requires a specific skill (web search, file operation, calendar check). If the skill fails, it may have been deactivated by the update. Reinstall it.",[14,1626,1627,1630],{},[17,1628,1629],{},"Are your cron jobs still running?"," This is the one people miss. Cron jobs can silently deactivate after updates. Check your cron configuration and verify the schedules are still active. If your morning briefing doesn't arrive tomorrow, this is probably why.",[14,1632,1513,1633,1637],{},[110,1634,1636],{"href":1635},"/blog/openclaw-best-practices","seven practices every stable OpenClaw setup should follow",", our best practices guide covers ongoing maintenance including update hygiene.",[57,1639,1641],{"id":1640},"what-commonly-breaks-between-versions-and-the-quick-fix","What commonly breaks between versions (and the quick fix)",[14,1643,1644],{},"Three things break more often than everything else combined.",[155,1646,1648],{"id":1647},"config-key-renames","Config key renames",[14,1650,1651],{},"OpenClaw occasionally renames config keys between versions. A field that was called one thing in the old version might have a slightly different name in the new version. When this happens, the gateway either ignores the old key (silently dropping your setting) or throws a validation error.",[14,1653,1654,1657],{},[17,1655,1656],{},"Quick fix:"," Compare your backed-up config file with the default config for the new version. Look for keys that exist in your backup but not in the new default. They've probably been renamed. Update the key names and restart.",[155,1659,1661],{"id":1660},"skills-going-inactive","Skills going inactive",[14,1663,1664],{},"Updates can change how skills are loaded or validated. A skill that worked in the previous version might fail validation in the new one due to changed schema requirements, missing fields, or updated security checks.",[14,1666,1667,1669,1670,1674,1675,1678],{},[17,1668,1656],{}," Reinstall the affected skills. If reinstallation fails, check if the skill has been updated on ClawHub to match the new OpenClaw version. If not, the skill may need an update from its maintainer. For the ",[110,1671,1673],{"href":1672},"/blog/openclaw-skills-install-guide","skill vetting and installation guide",", our ",[110,1676,1677],{"href":957},"skills post"," covers the safe installation process.",[155,1680,1682],{"id":1681},"gateway-binding-changes","Gateway binding changes",[14,1684,1685],{},"Some updates change the default gateway binding behavior. If your gateway was bound to a specific port or address, an update might reset it to the default. This breaks channel connections and API access.",[14,1687,1688,1690],{},[17,1689,1656],{}," Check your gateway config after updating. Verify the bind address and port match what you had before. Restore from your backup if they've changed.",[14,1692,1693,1694,1697],{},"If managing updates, config migrations, and skill compatibility sounds like more maintenance than you want, ",[110,1695,1696],{"href":283},"BetterClaw handles updates automatically",". Your config is preserved. Your skills stay active. Your memory files are intact. $29/month per agent, BYOK. You never touch any of this.",[57,1699,1701],{"id":1700},"how-to-roll-back-if-something-goes-wrong","How to roll back if something goes wrong",[14,1703,1704],{},"This is the section you'll bookmark.",[14,1706,1707],{},"If the update broke something and you can't fix it quickly, rolling back to the previous version is the fastest path to a working agent.",[14,1709,1710],{},"Install the specific previous version of OpenClaw by specifying the exact version number in the npm install command. Use the version number you wrote down before the update. This replaces the new version with the old one.",[14,1712,1713],{},"After installing the old version, restore your backed-up config file and memory files. Restart the gateway. Your agent should be back to its pre-update state.",[14,1715,1716],{},"The rollback takes about 2 minutes if you have your backup. It takes much longer if you don't, because you'll be trying to recreate settings from memory. This is why the backup step isn't optional.",[14,1718,1719],{},"Rolling back is not failure. It's the smart response when an update introduces problems you can't fix immediately. Update again later when the community has identified and resolved the breaking changes.",[14,1721,1722],{},[98,1723],{"alt":1724,"src":1725},"OpenClaw rollback process showing version pinning, config restore, and gateway restart steps","/img/blog/how-to-update-openclaw-rollback.jpg",[57,1727,1729],{"id":1728},"the-update-schedule-that-actually-works","The update schedule that actually works",[14,1731,1732],{},"Here's what nobody tells you about updating OpenClaw: you don't need to update every time a new version drops.",[14,1734,1735],{},"OpenClaw releases multiple times per week. Most updates are minor. Unless the changelog specifically mentions a security fix (like the CVE-2026-25253 patch for the CVSS 8.8 vulnerability) or a feature you need, waiting a few days lets the community find breaking changes first.",[14,1737,1738],{},"Check the GitHub issues and Discord after a new release. If people report problems, wait for the fix. If the community is quiet, the update is probably safe.",[14,1740,1741,1744],{},[17,1742,1743],{},"Security updates are the exception."," When a CVE is published, update immediately. The one-click RCE vulnerability (CVE-2026-25253) demonstrated why: 30,000+ instances were found exposed without authentication. Delaying security patches creates real risk.",[14,1746,1177,1747,1750],{},[110,1748,1749],{"href":329},"managed vs self-hosted comparison"," covers how updates are handled across different deployment approaches, including which platforms apply security patches automatically.",[14,1752,1753],{},"For everything else, update weekly or biweekly. Back up first. Check after. Roll back if needed. That's the whole process.",[14,1755,1756,1757,1760],{},"If you'd rather never think about updates again, ",[110,1758,1384],{"href":1382,"rel":1759},[1196],". $29/month per agent, BYOK with 28+ providers. Updates are automatic. Config is preserved. Security patches land same-day. Your agent stays current while you focus on what it does, not how it runs.",[57,1762,352],{"id":351},[14,1764,1765],{},[17,1766,1767],{},"How do I update OpenClaw to the latest version?",[14,1769,1770,1771,1534,1773,1534,1775,1777],{},"Run the npm global update command for OpenClaw in your terminal. Before updating, back up your ",[21,1772,120],{},[21,1774,1537],{},[21,1776,1541],{},", and config file. After updating, restart the gateway and verify your agent is responding, memory files are intact, skills are active, and cron jobs are running. The update takes about 30-60 seconds. The backup and verification add 10 minutes of safety.",[14,1779,1780],{},[17,1781,1782],{},"What breaks when I update OpenClaw?",[14,1784,1785],{},"The three most common issues are: config key renames (your settings silently stop working), skills going inactive (changed validation requirements), and gateway binding changes (connection settings reset to defaults). All three are fixable by comparing your backed-up config with the new defaults and restoring any changed values. The backup before updating is what makes these fixable instead of catastrophic.",[14,1787,1788],{},[17,1789,1790],{},"How do I roll back an OpenClaw update?",[14,1792,1793],{},"Install the previous version by specifying the exact version number in the npm install command. Restore your backed-up config file and memory files. Restart the gateway. The rollback takes about 2 minutes if you have your backup ready. This is why writing down your current version before updating is essential. Without it, you're guessing which version to roll back to.",[14,1795,1796],{},[17,1797,1798],{},"How often should I update OpenClaw?",[14,1800,1801],{},"For most users, weekly or biweekly updates are sufficient. Wait a day or two after each release to let the community identify breaking changes. The exception is security updates: when a CVE is published (like CVE-2026-25253, a CVSS 8.8 vulnerability), update immediately. On managed platforms like BetterClaw, updates are applied automatically with config preservation, so you never need to manage this manually.",[14,1803,1804],{},[17,1805,1806],{},"Is it safe to skip OpenClaw updates?",[14,1808,1809],{},"Skipping non-security updates for a few weeks is generally fine. Skipping security updates is risky. With 30,000+ exposed instances found without authentication and the ClawHavoc campaign targeting 824+ malicious skills, running outdated versions increases your exposure. The safest approach: apply security patches immediately, delay feature updates by a few days to let the community test them first.",[57,1811,396],{"id":395},[398,1813,1814,1819,1825,1831,1837],{},[401,1815,1816,1818],{},[110,1817,427],{"href":426}," — Full installation and configuration flow",[401,1820,1821,1824],{},[110,1822,1823],{"href":1635},"OpenClaw Best Practices"," — Seven practices for ongoing maintenance and stability",[401,1826,1827,1830],{},[110,1828,1829],{"href":957},"Best OpenClaw Skills (Tested & Vetted)"," — Safe skill installation after an update breaks them",[401,1832,1833,1836],{},[110,1834,1835],{"href":760},"OpenClaw Security Risks Explained"," — Why security patches can't be delayed",[401,1838,1839,1842],{},[110,1840,1841],{"href":329},"BetterClaw vs Self-Hosted OpenClaw"," — How updates are handled across deployment approaches",{"title":430,"searchDepth":431,"depth":431,"links":1844},[1845,1846,1851,1852,1853,1858,1859,1860,1861],{"id":1494,"depth":431,"text":1495},{"id":1520,"depth":431,"text":1521,"children":1847},[1848,1849,1850],{"id":1527,"depth":438,"text":1528},{"id":1545,"depth":438,"text":1546},{"id":1555,"depth":438,"text":1556},{"id":1578,"depth":431,"text":1579},{"id":1597,"depth":431,"text":1598},{"id":1640,"depth":431,"text":1641,"children":1854},[1855,1856,1857],{"id":1647,"depth":438,"text":1648},{"id":1660,"depth":438,"text":1661},{"id":1681,"depth":438,"text":1682},{"id":1700,"depth":431,"text":1701},{"id":1728,"depth":431,"text":1729},{"id":351,"depth":431,"text":352},{"id":395,"depth":431,"text":396},"2026-04-06","Back up 3 files, run the update, check 4 things after. If it breaks, roll back in 2 minutes. Here's the safe OpenClaw update process.","/img/blog/how-to-update-openclaw.jpg",{},"/blog/how-to-update-openclaw","10 min read",{"title":1471,"description":1863},"How to Update OpenClaw Without Breaking Anything","blog/how-to-update-openclaw",[1872,1873,1874,1875,1876,1877,1878],"how to update OpenClaw","OpenClaw update guide","update OpenClaw safely","OpenClaw breaking changes","OpenClaw rollback","OpenClaw new version","OpenClaw upgrade 2026","l9UswB_BvIUuoS63MMS1HwEoRWAx-KGeN0AXTt6h3uU",1776341557322]