2491f5c732
40 files demonstrating every major OpenClaw capability using Claude Code: - 3 agents (researcher, writer, reviewer) - 3 skills (daily-briefing, slack-message, web-research) - 2 security hooks (pre-tool-use blocker, post-tool-use logger) - 10 self-contained examples with copy-paste prompts - Complete feature map (20 capabilities, 11 full match, 7 different, 2 gap) - Security docs including NemoClaw comparison - Automation, messaging, browser, memory documentation Zero dependencies. Clone and run. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
57 lines
1.9 KiB
Markdown
57 lines
1.9 KiB
Markdown
# Example 06: Multi-Agent Orchestration
|
|
|
|
**Capability:** Claude Code can spawn sub-agents with distinct roles, run them in
|
|
parallel or in sequence, and combine their outputs into a final result.
|
|
|
|
**OpenClaw equivalent:** Sub-agents, agent-to-agent messaging, mesh workflows.
|
|
|
|
---
|
|
|
|
## Prerequisites
|
|
|
|
This example uses the agents defined in `.claude/agents/`:
|
|
- `researcher.md` - web research and source gathering
|
|
- `writer.md` - structured content drafting
|
|
- `reviewer.md` - accuracy and quality review
|
|
|
|
These agents load automatically when Claude Code opens this project.
|
|
|
|
---
|
|
|
|
## The Prompt
|
|
|
|
```
|
|
Use the researcher agent to find information about how Claude Code handles
|
|
agent isolation and worktree sandboxing (introduced in v2.1.49 and v2.1.50).
|
|
|
|
Then use the writer agent to draft a 300-word technical summary of the findings,
|
|
written for a developer audience. No jargon without explanation.
|
|
|
|
Finally, use the reviewer agent to check the draft for technical accuracy.
|
|
If the reviewer finds any issues, have the writer fix them before showing
|
|
me the final version.
|
|
```
|
|
|
|
---
|
|
|
|
## What Happens
|
|
|
|
Claude Code will:
|
|
|
|
1. Invoke the researcher agent via the Agent tool with the research task
|
|
2. Receive the research output and pass it to the writer agent
|
|
3. Invoke the writer agent to produce the 300-word draft
|
|
4. Invoke the reviewer agent with both the draft and source material
|
|
5. If the reviewer flags issues, loop back to the writer for a revision
|
|
6. Present the final reviewed draft
|
|
|
|
---
|
|
|
|
## Why This Matters
|
|
|
|
Agent Teams (v2.1.32) gives Claude Code a mesh model that matches OpenClaw's
|
|
sub-agent architecture. Worktree isolation (v2.1.50) means each agent gets
|
|
its own working directory, preventing file conflicts in parallel runs.
|
|
|
|
The researcher-writer-reviewer pattern is the same loop that produces articles
|
|
for `fromaitochitta.com`. The agents here are minimal versions of that pipeline.
|