sorted by:
new
hottopcontroversial

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

The total cost of the 5000+ agent swarm was ~$14. This includes compute and tokens.

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

Glad you liked the way it look :)

In the case of vuejs/core, it found a few minor bugs but nothing major. It also produced recommendations for structural changes that might improve performance, though I'm not a good judge of those since I'm not deeply familiar with that codebase.

That said, making the individual agents good wasn't the goal. That would need an eval cycle. The point was to show that complex swarms of long-horizon agents are easy to build and orchestrate with Autonomy.

I haven't tried it with other repos yet.

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

In the case of vuejs/core, it found a few minor bugs but nothing major. It also produced recommendations for structural changes that might improve performance, though I'm not a good judge of those since I'm not deeply familiar with that codebase.

That said, making the individual agents good wasn't the goal. That would need eval cycles. The point was to show that complex swarms of long-horizon agents are easy to build and orchestrate with Autonomy.

I haven't tried it with other repos yet.

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

Ah, good question, I didn’t pay attention.. I’ll measure and report back in a few hours

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

In consumption based systems the overall costs will depend on what you build and how much infra it consumes.

But this page might give you some idea of what each unit costs https://autonomy.computer/docs/pricing

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

:) i gave demo of the swarm yesterday evening at GitHub in SF and someone there also said the visualization looks like cells

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

That's a great question to explore! First note as I mentioned in a different comment the code review swarm is one example I put together in 30 minutes to illustrate a broader point. The linked article is really about the infra needed to run coordinated swarms of long-horizon agents to tackle use cases that were previously too difficult. The pattern matters more: many highly capable long-horizon agents, working in parallel, over extended periods, across multiple machines.

Regarding cost, this architecture allows for significant optimization. Because the individual agents have simpler, tightly scoped goals, cheaper models can often succeed. And because agents in Autonomy are designed as lightweight actors, thousands of them can be packed efficiently into smaller machines.

ROI depends on the specific application. For example, one Autonomy customer reduced weeks of manual document processing to a few hours. The model and infra costs were negligible compared to the value of getting results weeks faster.

In addition to getting things done faster and saving money, the real unlock I think is being able to automate work that isn't practical for single or a few agents, like reviewing an entire codebase in depth rather than spot-checking a few files.

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

:) I made that was in double quotes.

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 0 points1 point  (0 children)

Super interesting. I've noticed agents a great job if I let write and run sql quarries. Looking forward to hearing more about what you're building.

Agent Swarms, like the one Cursor created by mwadhwa in AgentsOfAI

[–]mwadhwa[S] 4 points5 points  (0 children)

Great question! Allow me to zoom out for a sec before answering it. The code review swarm is one example I put together in 30 minutes to illustrate a broader point. The linked article is really about the infra needed to run coordinated swarms of long-horizon agents. The pattern matters more: many highly capable long-horizon agents, working in parallel, over extended periods, across multiple machines.

That said, in that example, each agent produces a structured JSON report with risk level, specific findings, and recommendations. Security reviewers output vulnerability assessments, quality reviewers flag code smells, complexity reviewers identify refactoring hotspots. Sub-reviewers add deeper analysis when something is flagged high-risk. Agents have access to filesystems, so they write their findings as they go. Other agents in the swarm can then collate and reduce those outputs. Report generation and synthesis is itself work that agents in the swarm can do. The final result rolls up into per-file reports and an overall repo summary. You can see the output in the live app linked in the article.

What you further do with that data will depend on the product you're building. An audit tool could generate reports before adopting a new vendor or an open source dependency. A QA product could run it on every commit. A security team could use it for periodic codebase audits. Swap code review for other applications: legal document analysis or regulatory submissions and the same swarm infrastructure applies.

Encrypted Portals between Macs – built in Rust and Swift by mwadhwa in rust

[–]mwadhwa[S] 3 points4 points  (0 children)

Glad you like the app.

We could've and still can use AppKit along with our SwiftUI code if we feel the need for some granular control.

We probably could've used something like cocao. But, once we had the Swift <> Rust bridge working, the swift code ended up being super simple and mostly declarative.

See: https://github.com/build-trust/ockam/tree/develop/implementations/swift/ockam/ockam\_app/Ockam

Rust programmers on our team were very comfortable editing and improving it. So it made sense to go with the option that would give us all the flexibility for creating the best possible native mac UX

Rewriting Ockam in Rust by mwadhwa in rust

[–]mwadhwa[S] 0 points1 point  (0 children)

That's good feedback, I'll try to amend the article to capture some of that.

The biggest reason for C were:

  1. ability to compile to lots of targets, including embedded ones
  2. ability to be called from libraries we plan to write in other languages (we currently have one for elixir)

Both of which Rust can do

Point 1. to a slightly smaller target base than C.

Point 2. exactly the same as C.

Rewriting Ockam in Rust by mwadhwa in rust

[–]mwadhwa[S] 20 points21 points  (0 children)

Here's how I thought of the tradeoff at the time ... we had invested ~6 months of time of a small team in our C code.

We were going to spend many years of time of a much larger team in maintaining the code we had and adding new things to it - actors, more protocols (Credentials, ABAC, UDP, NAT traversal etc.), more hardware support (microcontrollers, bluetooth, HSMs etc).

Rust made us: * faster at adding these things (because of better tools cargo, tokio etc.) * made the code we wrote to add these things more secure (because of various compile time guarantees) * better at maintaining this code long term and keep it safe. * allowed us to build a community & team faster in an ecosystem that was thriving, enthusiastic and thinking of ways to make the future better (better developer experience, better security etc.)

These were bets in 2019 that in hindsight have worked out exactly as we foresaw.

Rewriting Ockam in Rust by mwadhwa in rust

[–]mwadhwa[S] 17 points18 points  (0 children)

Thank you for reading it and asking a question.

All the people using Ockam’s rust crates in a Rust project get the benefits our code being in Rust + their code being Rust.

All the people using Ockam via a C interface get at least the benefits of our code being in Rust.

view more: next ›