Choose the guide for your problem
Each pack gives you a calm path through one OpenClaw problem: what to do first, what to copy, what to verify, and when to stop.
Two paid downloads are ready for checkout today. Each one routes through the product page first, lists the included files before checkout, uses Stripe checkout, and sends you back to a scanner-safe confirmation/download page after purchase.
Fill the purchase-to-first-GREEN receipt, create and verify one named backup, then make a GREEN/YELLOW/RED go/no-go decision before the risky OpenClaw change.
Use the symptom-to-fix matrix, compare against a known-good example without copying secrets, run the smoke-test checklist, and fill the config-change proof card before normal work resumes.
you are about to update OpenClaw, edit config, expose the gateway, or run agents unattended and need a checked backup plus a restore drill first.
OpenClaw already feels broken after a config edit and you need known-good examples, permissions notes, smoke tests, and rollback notes.
- Plain-English setup paths for Windows, macOS, and Linux
- Copy/paste commands built around `openclaw backup create --verify` and `openclaw backup verify`
- Fallback notes for `--no-include-workspace`, `--only-config`, and non-standard installs
- before OpenClaw upgrades or CLI/tooling changes
- before skill installs, config edits, provider swaps, or workspace moves
- you only need to read the official backup command docs and are comfortable designing your own rollback routine
- you expect live 1:1 support, custom recovery, or remote access to your machine
- A simple way to get reliable answers to specific configuration questions
- Known-good minimal configs (with explanations)
- Profiles & permissions: what changes what (and how to revert)
- OpenClaw users whose file or tool access changed unexpectedly
- teams that need a known-good config before experimenting
- you already have a known-good config diff, smoke tests, and rollback note that your team actually uses
- you need someone to repair a private config for you instead of a self-serve worksheet
- Server blueprint: categories + channels that scale
- The 4‑channel project pattern (brief/agent/deliverables/status)
- Multi‑agent topology: project agents vs function agents (Researcher/Builder/Ops)
- multi-agent work that keeps bleeding into the wrong channel
- project teams that need cleaner brief, status, and deliverables surfaces
- you only have one private agent thread and can already find briefs, outputs, and approvals quickly
- you expect a custom Discord server buildout, bot hosting, moderation, or hands-on support
- Cron and gateway scheduling templates
- Single-agent recurring jobs (email checks, health checks, security audits)
- Multi-step workflow patterns (research → classify → write)
- safe recurring jobs that gather evidence while you sleep
- scheduled checks that must not auto-publish or mutate production
- you want unattended agents to publish, deploy, buy, message customers, or change production without a human approval stop
- you do not yet have one manual OpenClaw workflow that runs safely end-to-end while you are present