Comments URL: https://news.ycombinator.com/item?id=50289812

Points: 2

# Comments: 0

We've been trying to grow the project for months, and it's lowkey growing in stars and adoption. But it's linear.

We see other projects do big jumps and hit thousands of stars in days. Going viral in HN, X, etc.

We believe that real adoption might not come from one day to another, and the teams using us are happy and want to use us more.

Now, I hate to spam in places like hn or other forums, but what strategies have you found working? Specially in the realm of AI.

Obviously if you ask ai, it's always: launch in HN, PH, etc, etc.

We post a lot on x, linkedin and such, but would love to push the adoption curve up.

Any help welcome!

Cheers,

Won't spam my project here, if you want to check it it's on gh -> desplega-ai/agent-swarm

Comments URL: https://news.ycombinator.com/item?id=50242424

Points: 6

# Comments: 15

Comments URL: https://news.ycombinator.com/item?id=50130599

Points: 1

# Comments: 3

Disclaimer: the blog should be glanced high-level as human, read the below instead. You can point your agents to it tho.

We've been working on agent-swarm (https://github.com/desplega-ai/agent-swarm) as an oss MIT project for a while.

One of the core principles on why we believe in is that when you adopt AI internally in your company, you should be free and not tied to a single provider (e.g. Devin).

Yesterday Devin introduced the Devin Oncall, and we wanted to replicate the feature in the swarm, but with one thing in mind: what if Devin is down?

As the swarm is built on top of a set of building blocks (not only agents), we created a set of workflow, deterministic scripts, and ui so that when a Pagerduty (or any other) comes it will handle it with automatic provider failover.

It's a simple thing really. In the blog post our swarm created explaining how to set it up you can see the high-level wf, and sub-wf.

If for some reason you have a swarm running point it to it. If you have some other system, do it too, as it might give you the high-level arch. to replicate it.

Cheers,

Comments URL: https://news.ycombinator.com/item?id=50116757

Points: 2

# Comments: 4

We've been building the swarm for almost a year now, and I'm super excited that our vision to build this oss (MIT) and harness agnostic is more relevant than ever.

I wanted to share the project again, as some of the latest things we did that I believe are relevant:

1. Scripts that allow you to code-mode like experience in a safe way 2. agent-fs integration, imagine like gdrive, but re-built from first principles for agents (oss MIT too) 3. Pages & apps -> baascially artifacts. We've seen a company building a lovable inside an app (lol) 4. Extensions -> pi-mono like scripts that let you modify how the system works (e.g. we have jev reviewing the swarm replies to adhere to comms style)

What do you think about it? Do you think our vision makes sense? Roast me! :D

Cheers,

Comments URL: https://news.ycombinator.com/item?id=50021629

Points: 1

# Comments: 3

A few weeks ago, Boris posted how formal verification helped fix issues in their codebase (https://x.com/bcherny/status/2102543349102338309) and I definitely wanted to try it out in the swarm codebase.

The idea was simple:

1. Go over the codebase and fine most critical parts that could be modelled 2. Pick the first few and try to model them based on main code 3. Find counterexamples 4. Generate failing tests for them (single tests file diff pr) 5. Go over each of them and fix them + add the counterexamples in the repo for reference

I think this pattern is super nice tbh, and it helps a lot on reasoning around the code and implementation, specially when AI was involved.

The main issue: we had to add a daily wf to check for any updates to the spec, so that we keep it in sync (price you pay when the language can not be expressive enough, e.g. js).

Another win was that for the heartbeat system, which I wanted to refactor for a while, it managed to propose a simplification from 1.3M states to only ~4k (lol).

I believe it can be used for complex systems refactoring, while keeping the same functionalities.

Blog post about it (beware AI generated, but it contains some of the prompts we used during the session, just point your agent to the link and let it cook) -> https://www.agent-swarm.dev/blog/tla-plus-races-agent-swarm

I've been wanting to use tla+ for years, but always struggled w the syntax when working on something non-trivial. AI generating the specs and explaining the reasoning behind them helped a lot!

If you curious about the specs -> https://github.com/desplega-ai/agent-swarm/blob/main/specs/t...

Cheers,

Comments URL: https://news.ycombinator.com/item?id=49894642

Points: 1

# Comments: 1

I did a re-write of the post to remove the sloppy parts and making more clear some of the estimates and assumptions we made in the post.

Also linked this thread in there, so that anyone getting to that post can see all the interesting pieces mentioned in here.

Till the next on HN!!1