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

Claude Code introduces specialized sub-agents

docs.anthropic.com

Post reply on HN
Print view View original

51–60 of 65 posts

Re: Claude Code introduces specialized sub-agents

#51

Post by boesboes »

bomewish wrote: post #4

Has CC become much stupider in recent weeks, or is it me? Any anecdata out there?

Yeah, it has become unusable for me. Maybe it always has been and I am just trying to solve harder problems with it and more critical of the results. But it’s still infinitely better than gemini for me, that can’t do anything useful. It even tried removing the entire security system from my rails app because it couldn’t figure out how to login in the tests.

I did a test with a very detailed prompt, exactly specified what to fix and how. Claude did it, but not very well. Gemini? it got stuck in a loop until i told it to stop, gave it a hint and then it got stuck again and gave up after trying the exact same thing three more times…

And while Claude managed to get through it, it couldn’t get it right even with some help. It took me 15 minutes to write the prompt, 15 minutes of claude implementing it & another 10 trying to get it to do it correctly. It would have taken me about half the time to do it myself i think..

I am giving up on it for a while.

Re: Claude Code introduces specialized sub-agents

#52

Post by yumraj »

illusive4080 wrote: post #6
bomewish wrote: post #4

Has CC become much stupider in recent weeks, or is it me? Any anecdata out there?

Not for me. It gets worse when context is nearly full. I like to compact or clear context more often than it does automatically.

I’ve thought about that but always forget, good to know it helps.

I wish there were a way to persist in-memory context in a file automatically, say on each compact or git commit. Yesterday CC crashed and restarting it and feeding it all the context was a pain since my updated Claude.md file was a couple of days old. It literally went from a Sr Engineer to a Jr post crash.

Re: Claude Code introduces specialized sub-agents

#53

Post by yumraj »

pjm331 wrote: post #20

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 t…

What’s one use case where someone would do this? Very curious.

Re: Claude Code introduces specialized sub-agents

#54

Post by jswny »

yumraj wrote: post #52
illusive4080 wrote: post #6

Earlier quoted context omitted.

Not for me. It gets worse when context is nearly full. I like to compact or clear context more often than it does automatically.

I’ve thought about that but always forget, good to know it helps. I wish there were a way to persist in-memory context in a file automatically, say on each compact or git commit. Yesterday CC crashed and restarting it and feeding it all the context was a pain since my updated Claude.md file was a couple of days old. It literally went from a Sr Engineer to a Jr post crash.

You can do that with hooks! Make a small script that triggers on a commit tool use or a compact hook and reads the conversation file (should be available via inputs to the hook) and back it up somewhere

Re: Claude Code introduces specialized sub-agents

#55

Post by theshrike79 »

yumraj wrote: post #53
pjm331 wrote: post #20

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 t…

What’s one use case where someone would do this? Very curious.

Agents use a separate context and won't pollute the main context.

So if you have a code review agent or a tdd agent checking the current commit if it matches some specs you have, they'll start a separate "subprocess" with its own context and return whatever they find to the main Claude context.

Re: Claude Code introduces specialized sub-agents

#56

Post by [deleted] »

T0Bi wrote: post #34
data-ottawa wrote: post #25

Earlier quoted context omitted.

I would like a simple tool to run Claude in a container with only read/write access to provided folders. I’ve set it up bespoke but the auth flow gets broken.

I use the .devcontainer¹ from the claude-code repository. It works great with VSC and let's you work in your docker container without any issues. And as long as you use some sort of version control (git) you cannot really lose anything. ¹ https://github.com/anthropics/claude-code/tree/main/.devcont...

[deleted]

Re: Claude Code introduces specialized sub-agents

#57

Post by lvl155 »

furyofantares wrote: post #49
lvl155 wrote: post #37

Here my main problem with sub-agents WITHIN Claude Code. They don’t allow you to use other models. Let’s be honest it’s 99% Sonnet.

I haven't used them yet but it says they can use MCPs. The only MCP server I use is zen-mcp-server for routing stuff to o3 and gemini.

But that’s added layer and slow, no? Wouldn’t something like Opencode be a better option? You can pick anything out of major providers.

Re: Claude Code introduces specialized sub-agents

#58

Post by nsonha »

yumraj wrote: post #53
pjm331 wrote: post #20

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 t…

What’s one use case where someone would do this? Very curious.

Like "do research on topic/library X and use the conclusion for next steps"

Re: Claude Code introduces specialized sub-agents

#59

Post by beefnugs »

data-ottawa wrote: post #25
jampa wrote: post #18

Earlier quoted context omitted.

> IMPORTANT: Claude Code must be installed first: > [...] > # 2. Activate Claude Code with permissions > claude --dangerously-skip-permissions Bypassing all permissions and connecting with MCPs, can't wait for "Claude flow deleted all my files and leaked my CI credentials" blog post

I would like a simple tool to run Claude in a container with only read/write access to provided folders. I’ve set it up bespoke but the auth flow gets broken.

This is the main problem with all the AI stuff, you really need: whitelist only network isolation, idempotent clean virtual machine creation and cleanup, automated git branches and merging strategies, full chain multi host logging to an external log collector (when something unexpected happens to should be able to review an entire event log of where it went wrong so you can improve), social-graph like tracking of what works and what doesn't, constant background model testing (to detect when censorship is going to bite you) or when a new better model for quality for cost effectiveness can be swapped in, anything background like agents needs an orchestrator so you can set up daily or weekly budgets to try and keep a handle on costs, some defined methodology to reduce long running agent based production down to actual reliable code on an ongoing basis

The tooling required for any of this to approach actual engineering reliability levels is unbelievable really

Re: Claude Code introduces specialized sub-agents

#60

Post by anuramat »

mortsnort wrote: post #48

It says they can be "fine tuned," but it looks like the agents are all using the same model with different system prompts? This would be more intriguing if they trained a debugger model from the ground up that could be used for the debugger agent. I suspect we'll get there eventually.

you can specify the model in the yaml frontmatter, so at least with litellm it should be possible
Post reply on HN