OpenClaw Optimization Guide

Make your OpenClaw AI agent faster, smarter, cheaper, and actually safe to run in production.

July 2026 sweep. Stable baseline: OpenClaw 2026.6.11 (released 2026-06-30). This refresh covers the 2026.6.8–2026.6.11 trains — automatic fast mode, working failover, per-agent cost visibility, prompt-cache retention, cron fallback controls, and channel-delivery self-recovery — and corrects the previous revision, which referenced a "2026.6.4" release and several config keys that were never shipped. See the correction note in Part 33.

By Terp — Terp AI Labs

Start With The July 2026 Reality Check

The June trains (2026.6.8 → 2026.6.11) were about making OpenClaw dependable. If you last read this guide in mid-June, these are the new rules:

1. Claude subscription-era advice is dead. Anthropic's April 4 policy change broke the old "Claude Pro/Max covers OpenClaw" path. Treat Claude as paid API / Bedrock / provider-routed usage unless your own install proves otherwise.
2. Cost visibility is per-agent now. openclaw gateway usage-cost --agent <id> (or --all) shows spend per configured agent; cron it daily and treat spend jumps as context regressions. (There is no per-agent budget-cap config key — an earlier revision of this guide claimed one in error.)
3. Failover actually fires. Provider overloads are classified correctly, usage-limit responses route to fallbacks, and individual cron jobs can carry their own --fallbacks list (or run strict with --fallbacks ""). None of it helps without at least two configured lanes.
4. Fast mode is automatic. /fast auto (2026.6.10) runs short conversational turns in the provider's fast lane and returns to normal mode for longer work, with correct status through retries and fallback switches.
5. Long sessions got cheaper. Tool-heavy sessions now retain prompt-cache savings as results accumulate (2026.6.11) — one more reason to keep sessions long-lived and compaction healthy instead of resetting constantly.
6. Stuck channels self-recover. Telegram/WhatsApp queues that wedge after a crash or long-running task resume automatically in 2026.6.11. "Restart the gateway" should leave your runbooks.

Read Part 33 — June 2026 Field Guide first if you want the latest tricks before the deep dives.

The Harness Thesis

Most agent capability comes from the harness, not the weights.

The exact percentage is rhetoric. The operator lesson is concrete: model swaps help, but the big wins come from context budgets, memory discipline, tool permissions, flow control, provider routing, hooks, and verification loops.

flowchart LR
    subgraph Model["The Model (weights)"]
        M[Claude Opus 4.7<br/>or your choice]
    end
    subgraph Harness["The Harness (operator-controlled) — this guide"]
        direction TB
        Inst[Instructions<br/>SOUL/AGENTS/MEMORY/skills]
        Ctx[Context engineering<br/>budgets + progressive disclosure]
        Tools[Tools + approvals<br/>semantic categories]
        Guard[Guardrails<br/>hooks, Task Brain, redaction]
        Mem[Memory layer<br/>memory-core + LightRAG + dreaming]
        Orch[Orchestration<br/>5 coordination patterns]
    end
    Model -.-> Harness
    Harness -.-> Results[Production results]

You usually cannot change the weights. You can change everything else: context, memory, tools, approvals, verification, cost controls, and orchestration. The rest of this guide is that operator-controlled layer.

Jump straight to the payoff

File Hierarchy At A Glance

OpenClaw's file layout maps 1:1 to Karpathy's three-tier LLM Wiki pattern published April 10, 2026. If you only remember one diagram from this guide, make it this one:

flowchart TB
    subgraph Raw["Raw sources — immutable, agent read-only"]
        Vault["vault/*"]
        Daily["memory/YYYY-MM-DD.md"]
    end
    subgraph Curated["Curated summaries — injected on every message"]
        Soul["SOUL.md<br/>identity"]
        Agents["AGENTS.md<br/>operational rules"]
        Mem["MEMORY.md<br/>durable facts"]
        Dreams["DREAMS.md<br/>reflection diary"]
        Skills["skills/*<br/>on-demand playbooks"]
    end
    subgraph Artifacts["Generated artifacts — one-shot output"]
        PRs["PRs / commits"]
        Reports["Reports / transcripts"]
    end
    Raw -. memory_search .-> Agent((Agent))
    Curated --> Agent
    Agent --> Artifacts
    Agent -. Deep-phase promote .-> Mem
    Artifacts -. auto-capture .-> Daily

Full reasoning and update rules in Part 31 — The LLM Wiki Pattern In OpenClaw.

Who This Is For

• Running any OpenClaw agent in production. If your bot handles real work, the speed, memory, and security parts are non-optional.
• Just hit "why is my agent slow?" for the first time. Part 1 and Part 2 are where to start.
• Coming from v3.x or early v4.0. Start with Part 26 — Migration Guide, then Part 25 — Architecture Overview.
• Building multi-agent systems. Part 5 — Orchestration and Part 24 — Task Brain are your backbone.
• Already read half the guide and forget what's where. Jump to Part 27 — Gotchas & FAQ or the themed map below.

Start Here (In This Order)

1. Part 25 — Architecture Overview — 15-minute primer on what OpenClaw actually is under the hood (gateway, Task Brain, memory layer, skills, surfaces).
2. Part 14 — Quick Checklist — 30-minute setup checklist covering the 80/20.
3. Part 17 — The One-Shot Prompt — copy-paste prompt that automates the whole setup.
4. Part 27 — Gotchas & FAQ — keep this open while you work. Half your questions are here.

What You Get (Numbers From Our Production Deployment)

Full numbers in benchmarks/.

Companion resources shipped with the guide

Alongside the 33 parts themselves, this repo now includes the tooling that turns "I read the guide" into "I can audit and reproduce the results":

• SCORECARD.md — The OpenClaw Production Readiness Scorecard. 50 items across Speed / Memory / Orchestration / Security / Observability, 2 points each, max 100. Designed to be copy-pasted into your own repo and shared publicly.
• AWESOME.md — A curated, opinionated list of OpenClaw resources: skills worth installing, memory and orchestration tools, observability stacks,