We call it Shawarma where I come from
Claude Code's new hidden feature: Swarms
111–120 of 351 posts
Re: Claude Code's new hidden feature: Swarms
#112Earlier quoted context omitted.
It’s even less of a feature, Claude Code already has subagents; this new feature just ensures Claude Code actually uses this for implementation. imho the plans of Claude Code are not detailed enough to pull this off; they’re trying to do it to preserve context, but the level of detail in the plans is not nearly enough for it to be reliable.
Interesting about the level of detail. I’ve noticed that myself but I haven’t done much to address it yet. I can imagine some ideas (ask it for more detail, ask it to make a smaller plan and add detail to that) but I’m curious if you have any experience improving those plans.
I have had good success with the plans generated by https://github.com/obra/superpowers I also really like the Socratic method it uses to create the plans.
Re: Claude Code's new hidden feature: Swarms
#113Earlier 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/
You should add OpenAI Codex CLI.
Thanks for the feedback, I'll do that. For now, if you select "other" you get a text field to add any model not listed..
Re: Claude Code's new hidden feature: Swarms
#114Earlier 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/
Add vscode. Add a list of models, since many tools allow you to select which model you use.
Thanks for the feedback. I thought there are just too many models and versions to list them all. For now, if you select "other" you get a text field to add any model not listed, hope this helps.
Re: Claude Code's new hidden feature: Swarms
#115Earlier quoted context omitted.
Please don’t use git-flow. Every time I see it, it looks like an over-engineer’s wet dream.
Can you say more as to why? The concept is not complex and in our situation at least provides a lot of benefits.
Literally the reason’s for git’s existence is to make merging diverging histories less complicated. Adding back the complexity misses the point entirely.
Re: Claude Code's new hidden feature: Swarms
#116Hasn't cursor been doing this with it's Plan mode for a while? Or is this different?
Re: Claude Code's new hidden feature: Swarms
#117I'm not going to try this. Anthropic will probably ban me again.
Re: Claude Code's new hidden feature: Swarms
#118The problem I’ve been having is that when Claude generates copious amounts of code, it makes it way harder to review than small snippets one at a time. Some would argue there’s no point reviewing the code, just test the implementation and if it works, it works. I still am kind of nervous doing this in critical projects. Anyone just YOLO code for projects that’s not meant to be one time, but fully intend to have to be…
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.
Re: Claude Code's new hidden feature: Swarms
#119The problem I’ve been having is that when Claude generates copious amounts of code, it makes it way harder to review than small snippets one at a time. Some would argue there’s no point reviewing the code, just test the implementation and if it works, it works. I still am kind of nervous doing this in critical projects. Anyone just YOLO code for projects that’s not meant to be one time, but fully intend to have to be…
I have Claude Code author changes, and then I use this "codex-review" skill I wrote that does a review of the last commit. You might try asking Codex (or whatever) to review the change to give you some pointers to focus on with your review, and also in your review you can see if Codex was on track or if it missed anything, maybe feed that back into your codex review prompt.
Re: Claude Code's new hidden feature: Swarms
#120Hasn't cursor been doing this with it's Plan mode for a while? Or is this different?
With plan mode, I would hope there's an approval step.
With Swarm mode, it seems there's a new option for an entire team of agents to be working in the wrong direction before they check back in to let you know how many credits they've burned by misinterpreting what you wanted.