HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
parruda
claude-swarm
HISTORICAL RECORD2025–2025
parruda / claude-swarm · Not publicly available

claude-swarm

Discover this repository through its Hacker News conversations.

2Distinct people
3Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

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, 5:04:15 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 hour3 dated mentions

Observed mentions: 2025-07-25 16:11:34 UTC to 2025-07-26 04:50:42 UTC.

012025-07-25 16:00:00 UTC to 2025-07-25 17:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 25, 16:002025-07-25 17:00:00 UTC to 2025-07-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-25 18:00:00 UTC to 2025-07-25 19:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-07-25 19:00:00 UTC to 2025-07-25 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-25 20:00:00 UTC to 2025-07-25 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-25 21:00:00 UTC to 2025-07-25 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-25 22:00:00 UTC to 2025-07-25 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 25, 22:002025-07-25 23:00:00 UTC to 2025-07-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-26 00:00:00 UTC to 2025-07-26 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-26 01:00:00 UTC to 2025-07-26 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-26 02:00:00 UTC to 2025-07-26 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-26 03:00:00 UTC to 2025-07-26 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-26 04:00:00 UTC to 2025-07-26 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 26, 04:00

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
Jul 25, 16:002025-07-25 16:00:00 UTC2025-07-25 17:00:00 UTC101
Jul 25, 17:002025-07-25 17:00:00 UTC2025-07-25 18:00:00 UTC000
Jul 25, 18:002025-07-25 18:00:00 UTC2025-07-25 19:00:00 UTC110
Jul 25, 19:002025-07-25 19:00:00 UTC2025-07-25 20:00:00 UTC000
Jul 25, 20:002025-07-25 20:00:00 UTC2025-07-25 21:00:00 UTC000
Jul 25, 21:002025-07-25 21:00:00 UTC2025-07-25 22:00:00 UTC000
Jul 25, 22:002025-07-25 22:00:00 UTC2025-07-25 23:00:00 UTC000
Jul 25, 23:002025-07-25 23:00:00 UTC2025-07-26 00:00:00 UTC000
Jul 26, 00:002025-07-26 00:00:00 UTC2025-07-26 01:00:00 UTC000
Jul 26, 01:002025-07-26 01:00:00 UTC2025-07-26 02:00:00 UTC000
Jul 26, 02:002025-07-26 02:00:00 UTC2025-07-26 03:00:00 UTC000
Jul 26, 03:002025-07-26 03:00:00 UTC2025-07-26 04:00:00 UTC000
Jul 26, 04:002025-07-26 04:00:00 UTC2025-07-26 05:00:00 UTC101

What Hacker News says

1 sources
I've made a few attempts at manually doing this w/ mcp and took a brief look at "claude swarm" https://github.com/parruda/claude-swarm - but in the short time I spent on it I wasn't having much success - admittedly I probably went a little too far into the "build an entire org chart of agents" territory the main problem I have is that the agents just aren't used For example, I set up a code reviewer agent today and then asked claude to review code, and it went off and did it by itself without using the agent in one of anthropic's own examples they are specifically telling claude which agents to use which is exactly what I don't want to have to do: > First use the code-analyzer sub agent to find performance issues, then use the optimizer sub agent to fix them My working theory is that while Claude has been extensively trained on tool use a
Read the rest
nd is often eager to use whatever tools are available, agents are just different enough that they don't quite fit - maybe asking another agent to do something "feels" very close to asking the user to do something, which is counter to their training but maybe I just haven't spent enough time trying it out and tweaking the descriptions
In Claude Code introduces specialized sub-agents

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.