🦞 A framework for building collaborative AI agent teams on OpenClaw
ClawCrew is a framework for creating multi-agent teams that collaborate on tasks. Instead of one AI doing everything, you define specialized agents with focused roles, and an orchestrator coordinates their work.
Each agent evolves independently. You can train and tune each agent's capabilities separately — refine the designer's taste, sharpen the coder's style, improve the tester's coverage. They grow as individuals.
You're the manager. In Telegram (or any IM), you talk to the orchestrator and watch every agent work in real-time. Jump in anytime — give feedback, correct course, or let them run. Define team workflows and standards, then step back and let them deliver. It's like running a team or a company, except your employees are AI.
The magic: Each agent's capabilities are defined by its workspace — SOUL.md, AGENTS.md, skills, and tools. Change the workspace, change the agent.
Watch them work in real-time — right in your chat.
┌──────────────────────────────────────────────────────────────┐
│ ClawCrew Framework │
├──────────────────────────────────────────────────────────────┤
│ │
│ Orchestrator Agent (workspace_orca/) │
│ ├── SOUL.md → Personality & rules │
│ ├── AGENTS.md → Behavior guidelines │
│ ├── ClawCrew.md → Team structure & roles ⭐ │
│ └── skills/ → Available capabilities │
│ │
│ │ spawns │
│ ▼ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Agent A │ │ Agent B │ │ Agent C │ │
│ │ workspace_A/ │ │ workspace_B/ │ │ workspace_C/ │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ │
│ Each agent = unique workspace = unique capabilities │
│ │
└──────────────────────────────────────────────────────────────┘
📄 ClawCrew.md — The team definition file lives in the orchestrator's workspace.
It describes all roles, workflows, and standards for your agent team.
Key insight: The framework doesn't define what agents do — workspaces do.
🦑 OrcaBot (Orchestrator)
├── 🎨 DesignBot → API design, types, specs
├── 💻 CodeBot → Implementation
└── 🧪 TestBot → Testing, coverage
Use case: Automated code generation with quality gates
📚 ResearchLead (Orchestrator)
├── 🔍 SearchBot → Web research, data gathering
├── 📊 AnalystBot → Data analysis, insights
└── ✍️ WriterBot → Report writing, summaries
Use case: Deep research with structured output
🎬 ContentLead (Orchestrator)
├── 💡 IdeaBot → Brainstorming, concepts
├── ✏️ DraftBot → Writing first drafts
├── 🔍 EditorBot → Review, polish, fact-check
└── 📊 AnalyzerBot → Monitor engagement (clicks, replies, shares)
Use case: Blog posts, marketing copy, documentation with performance tracking
🎯 SupportLead (Orchestrator)
├── 🔍 TriageBot → Categorize, prioritize
├── 💬 ReplyBot → Draft responses
└── 📈 EscalateBot → Complex issue handling
Use case: Automated support ticket handling
This example shows a complete software development crew.
┌─────────────────────────────────────────────────────────┐
│ │
│ 🦑 OrcaBot │
│ (Orchestrator) │
│ │
│ "I break down tasks, delegate work, and ensure │
│ quality at every step." │
│ │
└─────────────────────────────────────────────────────────┘
│
┌───────────────┼───────────────┐
│ │ │
▼ ▼ ▼
┌───────────┐ ┌───────────┐ ┌───────────┐
│ │ │ │ │ │
│ 🎨 Design │ │ 💻 Code │ │ 🧪 Test │
│ Bot │ │ Bot │ │ Bot │
│ │ │ │ │ │
└───────────┘ └───────────┘ └───────────┘
| Agent | Role | Deliverables |
|---|---|---|
| 🦑 OrcaBot | Orchestrator | Task breakdown, quality gates, final delivery |
| 🎨 DesignBot | Architect | API specs, types, edge cases |
| 💻 CodeBot | Engineer | Implementation, docstrings |
| 🧪 TestBot | QA | Unit tests, coverage report |
USER REQUEST
│
▼
┌─────────────────────┐
│ PHASE 1: DESIGN │ OrcaBot → spawns → DesignBot
│ Output: API spec │ OrcaBot reviews → ✅
└─────────────────────┘
│
▼
┌─────────────────────┐
│ PHASE 2: CODE │ OrcaBot → spawns → CodeBot
│ Output: module.py │ OrcaBot reviews → ✅
└─────────────────────┘
│
▼
┌─────────────────────┐
│ PHASE 3: TEST │ OrcaBot → spawns → TestBot
│ Output: tests.py │ OrcaBot reviews → ✅
└─────────────────────┘
│
▼
┌─────────────────────┐
│ FINAL DELIVERY 🚀 │
│ • Code + Tests │
│ • 100% coverage │
│ • Documentation │
└─────────────────────┘
Prerequisites: OpenClaw already installed and configured. See OpenClaw docs for installation.
curl -sSL https://raw.githubusercontent.com/lanxindeng8/clawcrew/main/install.sh | bashThis will:
- Check and install dependencies (Python 3.10+, pip, jq)
- Install ClawCrew via pip
- Run the interactive setup wizard
pip install clawcrew
clawcrew initgit clone https://github.com/lanxindeng8/clawcrew
cd clawcrew
cp .env.example .env # Edit with your Telegram credentials
docker-compose up -dOnly need 1 bot for all agents.
- Message @BotFather →
/newbot - Get your bot token
- Important: Disable privacy mode
/mybots→ Select your bot → Bot Settings → Group Privacy → Turn off- This lets the bot see all messages in groups
- Create a group called "OpenClaw Dev" (or any name)
- Add your bot to the group
- Get the group's
chat_id
git clone https://github.com/lanxindeng8/clawcrew
cd clawcrew
./setup.sh# 1. Reload your shell (or restart terminal)
source ~/.profile # or ~/.zshrc depending on your shell
# 2. Configure ClawCrew (Telegram bot, OpenClaw settings)
clawcrew init
# 3. Start the system
clawcrew start
# 4. Verify everything is running
clawcrew statusOption 1: Telegram — Send a message in your Telegram group:
Create a Python module to calculate distance between two points
Option 2: CLI — Run agents directly:
# Chain multiple agents (auto context passing)
clawcrew chain "Create a distance calculator module" design code test
# Or run a single agent
clawcrew run design -t "Design a REST API for user authentication"OrcaBot will automatically coordinate DesignBot → CodeBot → TestBot to complete the task.
| Command | Description |
|---|---|
clawcrew init |
Interactive setup wizard |
clawcrew start |
Start the OpenClaw gateway |
clawcrew stop |
Stop the gateway |
clawcrew status |
Show system and agent status |
clawcrew agents |
List available agents |
# Run a single agent
clawcrew run design -t "Design a REST API for users"
# Run with context file
clawcrew run code -t "Implement the API" -c design.md -o api.py
# Chain multiple agents (auto context passing)
clawcrew chain "Create user authentication" design code testclawcrew github analyze --url https://github.com/user/repo
clawcrew github issues -r user/repo
clawcrew github read-issue -r user/repo -n 123
clawcrew github create-pr -r user/repo -t "Fix bug" -H fix-branchclawcrew show-memory -a design # Show agent's memories
clawcrew clear-memory -a design # Clear today's memories
clawcrew clear-memory -a design --all # Clear all memoriesCreate workspace-orchestrator/SOUL.md:
# SOUL.md
You are the team lead. When you receive a task:
1. Break it into phases
2. Spawn the right agent for each phase
3. Review each deliverable
4. Deliver final resultsCreate workspace-agent-a/SOUL.md:
# SOUL.md
You are a specialist in [SKILL].
When given a task:
1. Focus only on your expertise
2. Deliver high-quality output
3. Report back to the orchestratorSet up OpenClaw to route to your orchestrator.
Send a task and watch your custom team collaborate!
ClawCrew includes GitHubBot — a specialized agent for GitHub workflows.
| Feature | Description |
|---|---|
| Repository Analysis | Analyze repos to understand architecture, tech stack, and key files |
| Issue Management | List and read GitHub issues for development context |
| PR Workflow | Create, list, and read Pull Requests |
# Analyze a repo
./bin/agent-cli.py summarize-repo --url https://github.com/user/repo
# Read an issue
./bin/agent-cli.py read-issue -r user/repo -n 123 --comments
# Create a PR
./bin/agent-cli.py create-pr -r user/repo -t "Fix bug" -H fix-branchFull documentation: See workspace-github/SOUL.md for complete command reference and workflow examples.
- Multi-agent orchestration pattern
- Software Dev Team example
- Quality gates between phases
- Real-time chat visibility
Team Management
- Easy onboarding — add new agents with simple config
- Role templates — pre-defined SOUL.md for common roles
- Hot reload — update agent capabilities without restart
Team Collaboration
- Shared context — team members access common knowledge base
- Internal handoffs — structured data passing between agents
- Team memory — persistent learnings across sessions
Team Operations
- Workflow editor — define pipelines visually
- Progress tracking — see task status across agents
- Quality metrics — success rates, iteration counts, costs
- Team-to-team communication
- Shared resource pools
- Cross-team orchestration
- Organization-level policies
Since this is the most common use case for developers:
GitHub Integration
- Repo onboarding — Orca reads new repo, summarizes architecture, shares with team
- Issue → Task — GitHub issues automatically become team tasks
- PR workflow — CodeBot creates PR, TestBot validates, Orca merges
- Code review — team reviews external PRs
Dev Workflow
- Multi-file projects — coordinate changes across files
- Dependency awareness — understand imports and relationships
- Incremental builds — work on existing codebases
- CI/CD hooks — trigger builds, handle failures
MIT License — See LICENSE
- Website: clawcrew.md
- GitHub: github.com/lanxindeng8/clawcrew
- OpenClaw: openclaw.ai
- Discord: discord.gg/clawd
Built with 🦞 OpenClaw — Your personal AI assistant