HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
desplega-ai
agent-swarm
TypeScript2025–2026
desplega-ai / agent-swarm

agent-swarm

Your Company Agentic Operating System

3Distinct people
18Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Your Company Agentic Operating System

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month18 dated mentions

Observed mentions: 2025-12-23 17:14:31 UTC to 2026-10-30 12:01:32 UTC.

0123452025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsDec 20252026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 20262026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC220
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC514
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC110
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC101
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC110
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC202
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC000
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC211
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC422

What Hacker News says

4 sources

Ask HN: How do you decide to cut scope when AI makes it so easy to add?

I've been having this conversation with my co-founder for months. It's so easy to add incremental features nowadays, and most seem useful. There's nothing obviously wrong with them. On top of that, people are using the software, and they appreciate how complete it is. The UX is cluttered, but 99% of interactions don't use it, so who cares. How do you decide to cut scope when in the current setup there's nothing to lose? Am I simply to old school? For context, this is the project: https://github.com/desplega-ai/agent-swarm
2 points · Open discussion
Hi there, 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 swar
Read the rest
m 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,
In Open Oncall: Open-Source Alternative to Devin Oncall

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.