by desplega-ai
Agent Swarm framework for AI coding agents and more!
# Add to your Claude Code skills
git clone https://github.com/desplega-ai/agent-swarmLast scanned: 5/19/2026
{
"issues": [
{
"type": "npm-audit",
"message": "@desplega.ai/localtunnel: Vulnerability found",
"severity": "high"
},
{
"type": "npm-audit",
"message": "@openfort/openfort-node: Vulnerability found",
"severity": "high"
},
{
"type": "npm-audit",
"message": "@openfort/shield-js: Vulnerability found",
"severity": "high"
},
{
"type": "npm-audit",
"message": "axios: Axios Cross-Site Request Forgery Vulnerability",
"severity": "high"
}
],
"status": "WARNING",
"scannedAt": "2026-05-19T07:46:19.022Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}No comments yet. Be the first to share your thoughts!
Agent Swarm is your Company's Compounding Intelligence Layer. A system of AI agents that remember, reason, act and get better with every task.
AI-Native · Compounds · Presence · Harness & LLM-Agnostic · Your Infra · Your Memory ·
Agent Swarm 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 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 & 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
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 →
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.
create_page MCP tool with public / authed / password modes, version history, view counters, diff helpers, and PDF export. MCP tools → PagesNeed help? Contact us at contact@desplega.sh.
Prerequisites: Docker and a Claude Code OAuth token (`claude setup-tok