Swarm/30 is a team of autonomous agents that design, build, test, review, and deploy production software — around the clock, with humans on the loop, not in it.
Every agent has a portrait, a role, and an idle behavior. Hover any card to see them come alive. Tier colors map to the orbital shells overhead.
Work flows through four stages. Agents claim tasks, escalate blockers, and post the receipts. You watch, steer, and merge.
Every decision is logged — what each agent did, why, and what it cost. Sample stream from a recent session below.
No. The roster mixes models and sizes deliberately — heavyweights for planning and review, leaner models for mechanical work. Each role has a budget and a fallback.
On the loop. Humans approve scope, set the budget, and ship the release. Agents handle the middle. You get a review queue, a kill switch, and a full audit trail.
Not as a product — Swarm/30 is a workflow, still being hardened on live codebases. When it's ready to share more broadly, it'll show up on GitHub. Until then, get in touch if you want it run on your repo.
Another agent catches it. Reviewers are paid — in tokens — to push back. Disagreements escalate to a senior agent, and unresolved ones escalate to a human.
Parts of the underlying stack already are — see gitlab-agent-webhook and the rest of my GitHub. The full Swarm/30 orchestration is not open source yet.
Swarm/30 is a workflow I'm building and running — not something you install. If you want this shape of engineering at your team, or just want to talk shop, drop a note.
Built by Riajul Islam — Head of Swarm. For everything else about me, visit riajul.dev.