Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code's new hidden feature: Swarms

twitter.com

Post reply on HN
Print view View original

161–170 of 351 posts

Re: Claude Code's new hidden feature: Swarms

#161

Post by idontwantthis »

atonse wrote: post #118
idontwantthis wrote: post #70

Earlier quoted context omitted.

I just can’t get with this. There is so much beyond “works” in software. There are requirements that you didn’t know about and breaking scenarios that you didn’t plan for and if you don’t know how the code works, you’re not going to be able to fix it. Assuming an AI could fix any problem given a good enough prompt, I can’t write that prompt without sufficient knowledge and experience in the codebase. I’m not saying t…

I don’t know what your stack is, but at least with elixir and especially typescript/nextJS projects, and properly documenting all those pieces you mentioned, it goes a long way. You’d be amazed.

If it involves Nextjs then we aren’t talking about the same category of software. Yes it can make a website pretty darn well. Can it debug and fix excessive database connection creation in a way that won’t make things worse? Maybe, but more often not and that’s why we are engineers and not craftsmen.

That example is from a recent bug I fixed without Cursor being able to help. It wanted to create a wrapper around the pool class that would have blocked all threads until a connection was free. Bug fixed! App broken!

Re: Claude Code's new hidden feature: Swarms

#162

Post by Kerrick »

7777777phil wrote: post #97
birken wrote: post #75

I'd really like to see a regular poll on HN that keeps track of which AI coding agents are the most popular among this community, like the TIOBE Index for programming languages. Hard to keep up with all the changes and it would be nice to see a high level view of what people are using and how that might be shifting over time.

I just started something like that, haven’t shared it widely yet, but here we go - happy if you participate: https://agentic-coding-survey.pages.dev/

Any chance you'll add Antigravity and Jetbrains Junie? I've been using almost nothing but those for the last month. Antigravity at home, Junie at work.

Re: Claude Code's new hidden feature: Swarms

#163

Post by simultsop »

mafriese wrote: post #157
ggoo wrote: post #145

Earlier quoted context omitted.

Is this satire?

Nope it isn’t. I did it as a joke initially (I also had a version where every 2 stories there was a meeting and if a someone underperformed it would get fired). I think there are multiple reasons why it actually works so well: - I built a system where context (+ the current state + goal) is properly structured and coding agents only get the information they actually need and nothing more. You wouldn’t let your produc…

quite a storyteller

Re: Claude Code's new hidden feature: Swarms

#164

Post by simultsop »

wild_pointer wrote: post #6

Listen team lead and the whole team, make this button red.

We have to reject claude can do it simply by a prompt, then everyone can do it. As SWE's we are not going to pragmatically accept we are done. https://www.youtube.com/watch?v=g_Bvo0tsD9s

Re: Claude Code's new hidden feature: Swarms

#165

Post by stavros »

mafriese wrote: post #157
ggoo wrote: post #145

Earlier quoted context omitted.

Is this satire?

Nope it isn’t. I did it as a joke initially (I also had a version where every 2 stories there was a meeting and if a someone underperformed it would get fired). I think there are multiple reasons why it actually works so well: - I built a system where context (+ the current state + goal) is properly structured and coding agents only get the information they actually need and nothing more. You wouldn’t let your produc…

What OpenCode primitive did you use to implement this? I'd quite like a "senior" Opus agent that lays out a plan, a "junior" Sonnet that does the work, and a senior Opus reviewer to check that it agrees with the plan.

Re: Claude Code's new hidden feature: Swarms

#166

Post by 7777777phil »

Kerrick wrote: post #162
7777777phil wrote: post #97

Earlier quoted context omitted.

I just started something like that, haven’t shared it widely yet, but here we go - happy if you participate: https://agentic-coding-survey.pages.dev/

Any chance you'll add Antigravity and Jetbrains Junie? I've been using almost nothing but those for the last month. Antigravity at home, Junie at work.

Done, upon popular demand I added Antigravity, Codex CLI, and Junie

Re: Claude Code's new hidden feature: Swarms

#167

Post by raffraffraff »

mafriese wrote: post #138

Ok it might sound crazy but I actually got the best quality of code (completely ignoring that the cost is likely 10x more) by having a full “project team” using opencode with multiple sub agents which are all managed by a single Opus instance. I gave them the task to port a legacy Java server to C# .NET 10. 9 agents, 7-stage Kanban with isolated Git Worktrees. Manager (Claude Opus 4.5): Global event loop that wakes u…

The next stage in all of this shit is to turn what you have into a service. What's the phrase? I don't want to talk to the monkey, I want to talk to the organ grinder. So when you kick things off it should be a tough interview with the manager and program manager. Once they're on board and know what you want, they start cracking. Then they just call you in to give demos and updates. Lol

Re: Claude Code's new hidden feature: Swarms

#168

Post by abhinavg »

apsurd wrote: post #82
joshribakoff wrote: post #42

This is just sub agents, built into Claude. You don’t need 300,000 line tmux abstractions written in go. You just tell Claude to do work in parallel with background sub agents. It helps to have a file for handing off the prompt, tracking progress, and reporting back. I also recommend constraining agents to their own worktrees. I am writing down the pattern here https://workforest.space while nearly everyone is buildi…

OT: Your visual on "stacked PRs" instantly made me understand what a stacked PR is. Thank you! I had read about them before but for whatever reason it never clicked. Turns out I already work like this, but I use commits as "PRs in the stack" and I constantly try to keep them up to date and ordered by rebasing, which is a pain. Given my new insight with the way you displayed it, I had a chat with chatGPT and feel good…

If you’re interested in exploring tooling around stacked PRs, I wrote git-spice (https://abhinav.github.io/git-spice/) a while ago. It’s free and open-source, no strings attached.

Re: Claude Code's new hidden feature: Swarms

#169

Post by mafriese »

stavros wrote: post #165
mafriese wrote: post #157

Earlier quoted context omitted.

Nope it isn’t. I did it as a joke initially (I also had a version where every 2 stories there was a meeting and if a someone underperformed it would get fired). I think there are multiple reasons why it actually works so well: - I built a system where context (+ the current state + goal) is properly structured and coding agents only get the information they actually need and nothing more. You wouldn’t let your produc…

What OpenCode primitive did you use to implement this? I'd quite like a "senior" Opus agent that lays out a plan, a "junior" Sonnet that does the work, and a senior Opus reviewer to check that it agrees with the plan.

You can define the tools that agents are allowed to use in the opencode.json (also works for MCP tools I think). Here’s my config: https://pastebin.com/PkaYAfsn

The models can call each other if you reference them using @username.

This is the .md file for the manager : https://pastebin.com/vcf5sVfz

I hope that helped!

Post reply on HN