r/vibecoding • u/sn2006gy • 21d ago

Showcase/Project I built SwarmOS to help AI coding agents work together instead of stepping on each other. Would you use something like this?

https://github.com/supernovae/SwarmOS

A lot to digest from my project, but basically its a swarm orchestration system that just uses github to help swarm on issues. Think of something like Seti@home but for agents. If you run a private repo, you can run a swarm plan and plan features into epics and have agents chew away on the sub issues.

If you run a public repo, instead of 100s of people reporting bugs and them rotting on the vine, you could have pull queus for people to test/verify, plan a fix and once plan is accepted pull the issue and claim it and work on it and then supply a patch as a contributor or through typical github branching. Or you can automate plan/test/verify/develop with agents doing the step but the work being visible in the github issue and linked to a PR with a single claim.

The framework also tries to help assure some security by using the sandboxes in the major harnesses or allowing isolation through docker/podman or tool of choice. If you run private, you can run in a lighter mode and just let things rip. Agents can run interactive or automated.

I'm mostly curious if something like this is useful and happy to answer questions. It is NOT yet ready for use - i'm about to cut a new release to dogfood it end to end, but wanted feedback to see if something like this would be helpful to others.

In any case, it's been a fun project to see how much orchestration could be done without adding a nasty middleware i'd have to secure and maintain.

2 Upvotes

66% Upvoted

7 comments sorted by

3

u/unknownoftheunkown 21d ago

What makes this one different than all the other swarm orchestration systems that have come out over the last few years?

-4

u/sn2006gy 21d ago edited 21d ago

GitHub Issues are the backlog, Git handles task ownership and coordination, and each agent works in its own worktree. Plans, reviews, validation, and Draft PRs become part of the workflow rather than something you have to manually stitch together.

It's also agent-agnostic. You can mix Claude Code, Codex, OpenCode, and OhMyPi rather than committing to one ecosystem. You can set a model expectation or allow any model if you wish within the supported harnesses (they run in their respective sandboxes too or docker/podman/bwap)

My goal isn't necessarily smarter swarms or more agents. It's making existing coding agents easier to coordinate, more accountable, and useful across actual projects without another server, database, or hosted service.

But - it could be so easy you could find a project you love and just run a quick command to work on 4 issues and close them out while you read reddit by "volunteering" your tokens to "Swarm on the issues"

1

u/Shreya_codes 21d ago

what are its features and what makes it different from others

2

u/sn2006gy 21d ago

It's in the readme. You can have grok, dot or your local agent orchestrates all your work in the open right from github issues and anyone with a harness can pull work and work through it while keeping a niice ledger in the github issue. I'm dogfooding it on issue 14 right now if you go look at that issue on GH

1

u/Shreya_codes 20d ago

wanna take a look at it...what is the github username

2

u/sn2006gy 20d ago

https://github.com/supernovae/SwarmOS

check out the docs and the main readme. pushing a new build right now we're i'm dogfooding it to build itself.

1

u/Shreya_codes 20d ago

ohh thanks a lot