Production-ready multi-agent team configurations. Each team ships with agents, skills, shared context, and a one-line installer — deploy locally on macOS/Linux, to a DigitalOcean droplet, or as a fleet via Ansible.
Free · you bring an Anthropic API key · ~5 minutes to first agent
Choose your install path ↓brew install node@22.Three supported paths. Pick the one that matches where you want the team to run.
You already have OpenClaw installed (or want to install it locally). Run a team's setup.sh directly and you're done. Best for trying it out.
Bootstrap a fresh Ubuntu 24.04 droplet: hardening, Node.js, Caddy with Let's Encrypt, then deploy your team. Three commands.
Declarative inventory, repeatable rebuilds. Two playbooks mirror the shell flow so every host ends up in the same state.
Seven self-contained teams, each with four agents mapped to the DISC behavioral model — Red leads, Yellow creates, Green operates, Blue reviews.
operatorproduct-builderdevmodernizeraccountantrecruiterreal-estateDesign, build, and operate an autonomous business that generates recurring revenue.
Build products from idea to production using spec-first development and CI/CD.
Autonomous engineering team that ships GitHub issues by spawning Claude Code subagents.
Modernize legacy apps through a phased, compliance-aware pipeline: LEARN, PLAN, EXECUTE.
AI-powered back-office accounting — categorize, reconcile, report, and track taxes.
AI-powered recruiting — source, screen, interview, and hire with built-in bias detection.
AI deal desk — comps, financial review, due diligence, and pipeline management.
Three commands take a bare Ubuntu 24.04 droplet from zero to a hardened, TLS-terminated, production-ready instance. Step 4 makes the team yours.
Run as root on a fresh Ubuntu 24.04 droplet. Handles everything from security hardening to TLS termination.
Run as the openclaw user after installing OpenClaw. Deploys any team in a single command.
Hardens the server, creates users, installs Node.js, and provisions TLS via Caddy. Pass --domain for Let's Encrypt, or omit for self-signed.
Switch to the openclaw user and run the official installer. Onboarding walks you through channel setup, tokens, and API keys.
Pick any team and deploy it. The script clones the repo, runs setup, and deploys agent workspaces and skills. It also applies the OpenClaw 3.2 systemd workaround and reloads the gateway automatically — no separate patch step.
The team is on disk but dormant until you tell it what it's working on. Edit ~/.openclaw/shared/VISION.md (the team's mission), then any agent's USER.md (your name, timezone, GitHub username — they're all identical, edit one and copy). Set ANTHROPIC_API_KEY in ~/.openclaw/.env if you didn't pass --api-key. Then start:
Already have OpenClaw installed, or want to try a team without a droplet. Skip the server steps and run the team's setup.sh directly.
Same official installer used on the droplet — works on macOS and Linux with Node.js 22+.
Clones the repo to /tmp, runs the team's setup.sh, lands files in ~/.openclaw/. Same idempotent script as the DigitalOcean path.
Edit ~/.openclaw/shared/VISION.md and any agent's USER.md. Put your ANTHROPIC_API_KEY in ~/.openclaw/.env. Then openclaw start.
For many droplets, declarative inventory, or repeatable rebuilds — the same flow, mirrored as two playbooks.
Hardens each droplet, creates the openclaw and claude users, installs Node.js 22, and provisions Caddy with TLS — for every host in -l droplets.
Runs the team's setup.sh as the openclaw user on every host, applies the systemd workaround, and reloads the gateway. Pass -e anthropic_api_key=… to set the key in one shot.
Playbook source and variable reference in
ansible/.
Need secrets out of .env or periodic state backups? See
Advanced setup.
Once configured, every 30 minutes the agents do a quick standup — each posts what they finished, what's next, and any blockers. Here's a realistic excerpt from the Dev team.
Every team follows the same battle-tested patterns.
Four agents per team — Red (Dominance), Yellow (Influence), Green (Steadiness), Blue (Conscientiousness) — for balanced decision-making.
Every script is safe to re-run. Users are checked before creation, configs are merged not replaced, and existing data is preserved.
Agents persist context across sessions through daily memory files and a curated MEMORY.md. No external database required.
UFW firewall, fail2ban, SSH key-only auth, non-standard usernames, and TLS termination — all configured automatically by bootstrap.sh.
STANDARDS.md governs session boot, memory management, safety rules, and group chat behavior. Consistent across every team.
BOOTSTRAP.md walks through VISION.md and USER.md setup on first run, then self-deletes. Zero manual configuration.
Every team follows this layout. Learn one, understand them all. See _template/ for the canonical skeleton.