Agent Swarm

An engine to make your company AI Native
_{Built by desplega.sh — by builders, for builders.}

[!TIP] This repo evolves every single day. Watch now →

_{▸ daily evolution · slack → pr · Making of}

agent-swarm.dev is an open-source operating system for AI work: a lead agent breaks goals into tasks, routes them to specialized workers such as Claude Code or Codex, runs each worker in an isolated container, and preserves shared memory, tools, schedules, and review gates so delegated work compounds across sessions.

AI-Native · Compounds · Presence · Harness & LLM-Agnostic · Your Infra · Your Memory ·

What it does

agent-swarm.dev runs a team of AI agents that coordinate autonomously. A lead agent receives tasks (from Slack, GitHub, GitLab, Linear, Jira, email, or the API), breaks them down, and delegates to worker agents running in isolated environments (Docker). Workers execute tasks, ship solutions, and write their learnings back to a shared memory so the whole swarm gets smarter every session.

You can run agents for Marketing, Product, UX, Engineering, Support, Operations, HR, Finance, or any role you can think of. A centralized Lead coordinates them, and they share the learnings horizontally. That's the true difference between AI First and AI Native.

agent-swarm.dev is the shared cloud brain and muscle that makes your whole company better every day.

Sometimes humans are the blocker. We can help you. Contact us contact@desplega.sh.

Learn more in the architecture overview.

flowchart LR
    subgraph IN["Tasks come in"]
        direction TB
        S["Slack"]
        G["GitHub / GitLab"]
        E["Email"]
        A["API / CLI"]
    end

    LEAD(["Lead Agent<br/>plans &amp; delegates"])

    subgraph WORKERS["Workers in Docker"]
        direction TB
        W1["Worker"]
        W2["Worker"]
        W3["Worker"]
    end

    subgraph BRAIN["Persistent brain"]
        direction TB
        MEM["Memory<br/>(vector search)"]
        ID["Identity<br/>(SOUL, CLAUDE.md)"]
    end

    subgraph OUT["Work ships"]
        direction TB
        PR["Pull Requests"]
        REPLY["Slack replies"]
        EMAIL["Email replies"]
    end

    IN --> LEAD --> WORKERS
    WORKERS -->|reads context| BRAIN
    WORKERS -->|writes learnings| BRAIN
    WORKERS --> OUT

Known Use Cases

Use cases that are used daily by ourselves and others. Each playbook contains: the agents, the tools & skills, and workflows & schedules behind it. Browse all playbooks →

• Feature Development — Integrated with Linear and GitHub to take feature requests from Slack and turn them into pull requests.
• Lead Prospecting — Integrate your prospecting tools with the swarm and let agents handle outreach, scheduling, and follow-up.
• Content Generation — Generate engagement tools, blog posts, manage social media presence, update your website, and more.
• UX Command Center — Agents that keep your product usable: record agentic sessions, enforce your design system, and mine user logs to detect and propose UX improvements.
• Proactive Customer Support — Agents that oversee your top accounts, prepare scheduled reports, and leverage everything they know about your platform to keep those accounts up to date.
• Code Health & Alert Management — Datadog, New Relic, Sentry, or any alerting tool can kick off fixes or new proposals. Monitor code health and propose improvements weekly, daily, or hourly.
• Reports from Multiple Sources — Integrate your data warehouse to generate tailored reports and answer the key questions your team has, with fresh data. Your BI tool may be a thing of the past.
• Self-Documenting & Release Reports — Update your docs and use frameworks like Remotion, qa-use, and browser-use to generate release videos and rich documentation in seconds, at the cadence you need.
• Do you have a cool playbook to share? Send us a PR!

The patterns that compound. Five recipes show up in nearly every playbook — they're how the swarm stays reliable as it scales: Litmus Tests (LLM-as-judge quality gates) · Drain Loops (one ticket → a chain of reviewable PRs) · HITL Gates (pause for human approval on irreversible steps) · Per-Customer Working Directories (context that compounds per account) · No-op Workflows (skip silently when nothing changed). See all patterns →

Check our templates for a quick start.

Highlights