For the last four months I’ve pushed almost everything through agents: sessions, subagents and workflows across a pile of side projects, mostly Claude Code. Some days that meant 50+ active threads at once. The output side was great. I got further on volume than I ever have. What I didn’t expect was how the end of each week felt. Not physically tired, more like I’d been in meetings all week. Every thread comes back sooner or later: test this, approve that, correct this one, send that one somewhere else. Each one is a context switch. A single check costs nothing. Fifty a day add up to something I could feel by Friday. My setup puts me mostly at the end of the loop. Agents pull context from what I’m already doing, they handle the middle, and I test, approve and check quality. I don’t want to hand that last check over, because it’s where I make sure the thing is what I had in mind. It’s also exactly where the switching cost lands. I have ADHD, so fifty threads felt like a buffet for a while. Then it was way too much. Turns out there’s a name for it. BCG surveyed 1,488 US workers in March and called it “AI brain fry”: 14% of AI users said they’d experienced it, and people doing heavy oversight of AI reported 12% more mental fatigue and were 19% more likely to report information overload. Self-reported, one survey, so I hold it loosely, but it matched my weeks. What I’m changing: I stopped treating thread count as the goal, and I’m building a small UI that shows how many decisions are waiting on me and which direction each project is heading, so the queue is in one place instead of scattered across chats. Too early to say if it helps. For people here running lots of sessions in parallel: where do you sit in the loop, and what did you do about the review end? Batch approvals, cap the number of sessions, have a second agent review before it reaches you? submitted by /u/Joozio
Originally posted by u/Joozio on r/ClaudeCode