Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Care sharing some of your sub-agent usage? I've always intended to really make use of them, but with skills, I don't know how I'd separate these in many use cases?


I just grabbed a few from here: https://github.com/VoltAgent/awesome-claude-code-subagents

Had to modify them a bit, mostly taking out the parts I didn’t want them doing instead of me. Sometimes they produced good results but mostly I found that they did just as well as the main agent while being way more verbose. A task to do a big hunt or to add a backend and frontend feature using two agents at once could result in 6-8 sizable Markdown documents.

Typically I find that just adding “act as a Senior Python engineer with experience in asyncio” or some such to be nearly as good.


They're useful for context management. I use frequently for research in a codebase, looking for specific behavior, patterns, etc. That type of thing eats a lot of context because a lot of data needs to be ingested and analyzed.

If you delegate that work to a sub-agent, it does all the heavy lifting, then passes the results to the main agent. The sub-agent's context is used for all the work, not the main agent's.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: