I was constantly fighting Claude Code's context limits. So many /clear and /compacts!
So I built a system of subagents. Now my sessions run 10x longer, and the code quality is higher.
Here are 6 battle-tested subagents that transformed my workflow (with working code) π§΅π
@iannuttall For sure. People have built AMAZING products, even solo, without LLMs at all. Or by copy and pasting into ChatGPT 3.5! None of these tools should hold you back if you are dedicated and have a solid idea.
@GosuCoder Automatic memory is a really hard problem to solve. What memories to save? And when to retrieve them that doesnβt confuse the current context?
@eliotpaynter@DannyAziz97 I was looking at doing something like this awhile ago but it seemed like an annoyance that the user has to restart their session. But not taking anything away from this - what you built is very cool!
@steipete@cerebras Yup itβs for sure hard mode in every way! But CC is actually pretty helpful with that figuring out configs and compiling software.
Research preview of Claude Code on Claude[.]ai
- updated layout with the prompt composer and sessions moved to the sidebar
- repository setup requires installing the GitHub Claude app on your repository and committing the "Claude Dispatch" GitHub workflow file
- you can enable email and web notifications for Claude Code updates
@Thomasmarkelly@trq212 For sure you can do it manually. Get Claude to write to https://t.co/0CiXubiaYe. But Claude Code is about best practices and making it easy for everyone to do that. So having an official solution for this would be nice. (could be optional too if you want to roll your own)
A popular NPM package got compromised, attackers updated it to run a post-install script that steals secrets
But the script is a *prompt* run by the user's installation of Claude Code. This avoids it being detected by tools that analyze code for malware
You just got vibepwned