A comprehensive guide to mastering OpenClaw — from basic gateway setup to advanced multi-agent architectures with sophisticated memory systems.
- Single-user operators wanting to understand the platform deeply
- Developers transitioning from single-user to multi-user deployments
- Power users building custom agents, skills, and plugins
| Module | Topic | Time | Key Outcome |
|---|---|---|---|
| 01 | Gateway Fundamentals | 30 min | Running gateway with Telegram |
| 02 | Session Management | 45 min | Multi-user safe configuration |
| Module | Topic | Time | Key Outcome |
|---|---|---|---|
| 03 | Memory Systems | 90 min | Hybrid search + curation workflow |
| 04 | Sub-Agents | 45 min | Task delegation patterns |
| Module | Topic | Time | Key Outcome |
|---|---|---|---|
| 05 | Skills & Plugins | 60 min | Custom capabilities |
| Module | Topic | Time | Key Outcome |
|---|---|---|---|
| 06 | Group Chat Handling | 45 min | Multi-user chat etiquette + access control |
| 07 | Farcaster Setup | 60 min | Decentralized social integration |
~/.openclaw/
├── openclaw.json # Main configuration (JSON5)
├── workspace/ # Default agent workspace
│ ├── MEMORY.md # Long-term curated memory
│ └── memory/ # Daily logs (YYYY-MM-DD.md)
├── agents/ # Per-agent directories
│ └── <agentId>/
│ ├── sessions/ # Session transcripts
│ └── agent/ # Agent-specific config
└── memory/ # Vector index storage
└── <agentId>.sqlite # Embeddings database
// ~/.openclaw/openclaw.json
{
// Gateway basics
gateway: { port: 18789 },
// CRITICAL for multi-user: isolate sessions by sender
session: { dmScope: "per-channel-peer" },
// Telegram channel
channels: {
telegram: {
enabled: true,
botToken: "YOUR_TOKEN",
dmPolicy: "pairing",
},
},
// Memory search with hybrid (vector + keyword)
agents: {
defaults: {
memorySearch: {
provider: "gemini", // or "openai", "local"
query: {
hybrid: {
enabled: true,
vectorWeight: 0.7,
textWeight: 0.3,
},
},
},
},
},
}# Start gateway
openclaw gateway
# Check status
openclaw status
# Telegram pairing
openclaw pairing list telegram
openclaw pairing approve telegram <CODE>
# View logs
openclaw logs --follow
# Configuration validation
openclaw doctor
openclaw doctor --fixLearn to install, configure, and run the OpenClaw gateway with Telegram integration.
Topics:
- Installation and first run
- Configuration file structure (JSON5)
- Hot reload and restart behavior
- Telegram bot setup via BotFather
- Essential CLI commands
Understand session isolation — critical for transitioning from single-user to multi-user deployments.
Topics:
- Session keys and lifecycle
- The
dmScopesetting (whymainis unsafe for multi-user) - Migration patterns: single → multi-user
- Security considerations and context leak prevention
Deep dive into OpenClaw's memory architecture — from markdown files to vector search to hybrid retrieval.
Topics:
- Memory file layout (
MEMORY.md, daily logs) - Vector embeddings setup (Gemini, OpenAI, local)
- Hybrid search (BM25 + vector)
- Advanced tuning: MMR (diversity), temporal decay (recency)
- QMD backend for BM25 + reranking
- Memory curation workflow (agent-suggested, human-curated)
- Experimental: session transcript indexing
Learn to delegate tasks to specialized sub-agents for complex workflows.
Topics:
sessions_spawnbasics- One-shot runs vs persistent sessions
- Orchestrator patterns and
maxSpawnDepth - Case study: Coach as ephemeral sub-agent
Extend OpenClaw with custom instructions (skills) or new capabilities (plugins).
Topics:
- Skills:
SKILL.mdformat, prompt injection - Plugins: TypeScript modules, tool registration
- Decision framework: when to use which
- Case study: Coach skill implementation
Navigate multi-user conversations with grace — when to participate, when to stay silent, and how to enforce access control.
Topics:
- Participation principles ("participate, don't dominate")
- Response triggers vs silence signals
- Access control patterns (owner vs public)
- Multi-agent coordination in groups
Integrate your agents with Farcaster, the decentralized social protocol, using the Neynar API.
Topics:
- Neynar API setup (keys, signers, environment)
- Posting casts, threads, embeds, and quote-casts
- Reading feeds, channels, and search
- Engagement workflows (replies, reactions, context)
- Node.js 20+ (22+ recommended)
- A Telegram account (for channel setup)
- API key for at least one LLM provider (OpenAI, Anthropic, Google, etc.)
- Optional: API key for embeddings (Gemini, OpenAI, Voyage, or local GGUF model)
These tutorials are designed for a specific learning journey:
- From single-user to multi-user — You're running a personal bot but want to open it up safely
- Telegram-focused — Examples use Telegram, but patterns apply to other channels
- Memory-centric — Emphasis on building effective long-term memory systems
- Practical patterns — Based on real-world implementations (Coach system, curation workflows)
Each module includes:
- Annotated configuration snippets
- Full working examples
- "Why this matters" explanations
- Common mistakes to avoid
- Your specific use case highlighted
Last updated: 2026-03-18