Most people install OpenClaw and get one agent doing one thing. That's fine for personal use. But what if you want an entire team? A COO, a social media manager, a video editor, a newsletter writer, an analytics scraper, an intelligence crawler, and a community manager. All running on one Mac Mini. All coordinated. All working while you sleep.

The 13-Agent Team: Every AI Agent and Its Role

Every agent has a single job. No overlap. No confusion.

AgentRoleWhat They Do
MarcCOOCoordinates everything. Dispatches tasks. Makes decisions. Talks to me on Telegram.
BobOpsHealth checks every 2 hours. Monitors all crons. Fixes or escalates.
DanX GrowthManages @profitfounder. 3 posts/day via Typefully API.
JimmyYouTubeMonitors for new episodes. Extracts clips. Maintains transcript archive.
TylerNewsletterWrites drafts from transcripts. Pushes to Notion. Teasers only.
ClaudeCopy EditorScans transcripts for clip moments. Writes posts. Quality scores 1-10.
AdrienVideo EditorWhisper transcription, smart cuts, silence removal, subtitle burn-in.
Mona LisaSponsorshipResearches targets. Personalized X DM outreach. Pipeline in Notion.
LoopAnalyticsDaily scrape of YT, X, IG, Skool, Beehiiv. Weekly correlation analysis.
CrawlyIntelligenceDaily web crawl: Reddit, HN, YouTube, X. READ ONLY.
BillyCommunityScans Skool daily. Content gaps. Module drafts. Churn tracking. READ ONLY.
ArianeNotionDaily cleanup. Moves misplaced pages. Archives stale items.
AlfredPersonalReal-life tasks. Contractors, errands, local services.

How OpenClaw Multi-Agent Coordination Works

You don't run 13 separate OpenClaw instances. You run one gateway with one main agent. (Need to set up the hardware first? See our Mac Mini setup guide or VPS setup guide.) (Marc). Marc spawns sub-agents when work needs to happen.

Florian (human)
  |
  Marc (main agent, COO)
  |
  +-- Bob (dispatcher)
  |     +-- monitors all other agents
  |     +-- health checks every 2 hours
  |
  +-- Content Pipeline
  |     +-- Jimmy (YouTube / clips)
  |     +-- Claude (copy editor)
  |     +-- Adrien (video editing)
  |     +-- Dan (X posting)
  |     +-- Tyler (newsletter)
  |
  +-- Growth & Revenue
  |     +-- Mona Lisa (sponsorship)
  |     +-- Loop (analytics)
  |     +-- Billy (Skool community)
  |
  +-- Operations
        +-- Crawly (intelligence)
        +-- Ariane (Notion)
        +-- Alfred (personal)

The pattern: Marc never does the work himself. He delegates to the right agent, checks the output, and reports back to me. Bob watches everything and alerts Marc if something breaks.

How to Spawn OpenClaw Sub-Agents

When Marc needs Jimmy to check for new episodes, he spawns a sub-agent session:

sessions_spawn({
  task: "Check YouTube for new podcast episodes...",
  model: "anthropic/claude-opus-4-6",
  runTimeoutSeconds: 600
})

The sub-agent runs in isolation, does its job, and reports back. Marc gets the result and decides what to do next.

OpenClaw Agent SOPs: How to Write Standard Operating Procedures

Every agent has a file in sops/[agent-name].md. Without SOPs, agents drift, forget rules, and overlap with each other.

Every SOP contains:

Example:

# SOP: Adrien - Video Editor Agent

## Role
Processes raw clips into polished, subtitled videos.

## Responsibilities
- Whisper transcription of raw clips
- Smart cuts (filler word removal)
- Silence removal
- Clean subtitle burn-in
- Compress for Telegram delivery

## Hard Rules
- Source clips MUST be h264
- Subtitles: 4-5 words per line max
- Never clip from the intro

OpenClaw Agent Permission System: Who Can Access What

AgentCan Write ToCannot Touch
DanX, TypefullyNotion deletions, memory files
JimmyTranscripts folderAny external platform
CrawlyNothing (READ ONLY)All platforms
BillyNotion drafts onlySkool (never posts)
TylerNotion drafts onlyBeehiiv send (I send)
MarcMemory, coordinationSocial media, email

Why this matters: The first time an agent accidentally deleted something, I built the access matrix. You don't want your analytics agent posting to X or your newsletter agent wiping Notion pages.

The Full 24-Hour OpenClaw Cron Schedule

TimeAgentTask
12:30 AMCrawlyIntelligence crawl (Reddit, HN, YouTube, X)
12:45 AMCrawlyTeam brief → Telegram
1:00 AMJimmyNight research + episode check
2:00 AMClaudeScan transcripts for clips
4:00 AMBobClip QA gate
5:50 AMLoopUsage cost tracker
6:00 AMArianeNotion cleanup + War Room
6:30 AMLoopDaily analytics scrape
7:00 AMMarcMorning brief → Telegram
8:00 AMBillySkool community scan
9:00 AMBillyChurn monitor
1:00 PMJimmyYouTube research
7:00 PMBobWar Room
7:30 PMMarcEvening brief
11:00 PMArianeDaily backup + Notion sync

Plus recurring: Git auto-backup every 30 min. Billy member count every 4h. Bob health check every 6h.

OpenClaw Shared Memory Architecture for Multiple Agents

13 agents need to share context without stepping on each other.

FilePurposeWho Writes
MEMORY.mdLong-term curated memoryMarc only
memory/YYYY-MM-DD.mdDaily notes / raw logsMarc, Bob
memory/regressions.mdFailure guardrailsAny agent
memory/friction-log.mdInstruction contradictionsAny agent
memory/predictions.mdDecision calibrationAny agent
memory/context-holds.mdTemporary priorities with expiryMarc

Key principle: Every session, every agent reads the relevant memory files. A fresh session can reconstruct the full context from files alone. Nothing lives only in memory.

Master Rules: The Constitution for All OpenClaw Agents

On top of individual SOPs, master-rules.md applies to ALL agents:

What Running 13 AI Agents Actually Costs

ItemCost
Mac Mini M4$700 one-time
Claude Opus API~$100-150/month
Electricity~$3/month
Total monthlyUnder $155/month

Compare that to hiring even one freelancer.

Lessons After Running 13 OpenClaw Agents for 2 Months

  1. Start with one agent. Add slowly. I started with Marc, added Bob, then specialists as I understood the workflows.
  2. SOPs prevent chaos. Write the SOP before spawning the agent.
  3. Permissions matter. Build the access matrix before something gets accidentally deleted.
  4. The dispatcher pattern is key. Marc → Bob → everyone else. Without this layer, the main agent gets overwhelmed.
  5. Memory files are your continuity. If it's not written down, it doesn't exist.
  6. Crons are the real power. Having agents work on a schedule without you asking is transformative.

Get the Complete Multi-Agent Template Pack

Inside OpenClaw Lab, members get the complete template pack: every SOP, the access matrix, the cron schedule, the memory architecture, and the coordination playbook. Copy-paste it, swap in your business context, and you have a 13-agent team running in an afternoon.

New to OpenClaw? Start with installopenclawnow.com to get your first agent running.

I share the exact playbooks, skill files, and workflows behind this system inside OpenClaw Lab. Weekly lives and AMAs with experts.

Join OpenClaw Lab →