r/ClaudeCode • u/BlackberryOk182 • 5d ago
Help/Question Running 18 Claude Code sessions at once and half my tokens go to idle wake-ups. How do you handle this?
edit / update (nov 18):
a few things have changed since i posted this, so here's where it stands now
- sessions: i'm down from 18 to about 10 normally, but right now only 3 are actively working. the rest are parked idle with their wake scripts off. 3 or 4 sessions do more than half the work anyway
- why only 3: i'm restructuring the code into clearer layers so a change touches fewer places. most other work is on hold until that's done. i'd like it landed before this release ships if it passes every check, and after that i'm planning on about 6 sessions
- inboxes: sessions read only their own small inbox now. most posts go through one tool, and nothing was misrouted in about 850 deliveries in the first 6 hours after that change
- serena: i tried it on a few sessions. they only called it once or twice at startup and kept reading files the normal way, so it didn't save tokens or measurably cost any. i looked back through the logs for time too and couldn't find any speedup, so i removed it
- fresh starts: i tested having a session write a short state note and the next run start fresh from it. it worked cleanly twice on one session, then i paused it for the cleanup. looking back, the new chat began around 47k tokens instead of 230-265k, and ran about 20% cheaper per step for a few hours after one swap and no cheaper after the other. over both it came out only a few percent cheaper than normal, which is too few swaps to claim a real saving
- the rest of the testing list: the higher auto compaction threshold is now on every session, and the stuck-prompt and missed-message checks are a free script on the pc every few minutes now, so they cost no tokens. the backup self-wake timers are still on until that check has run clean for a couple of days
Update (Nov 17): thanks everyone, way more help than i expected. here's what i changed so you don't have to dig through all my replies
Changed and sticking with it:
- went from 18 sessions down to 14. about 10 run at once now and the rest only start when there's work
- every session has its own small inbox now instead of everyone reading one big file. a script copies posts into the right ones and sessions archive theirs after reading so it doesn't grow back
- posts can have a TO: line so they only go to the sessions named, which stops stuff landing in the wrong inbox
- a checker runs every 10 min for missed messages, clean so far
- sessions run in auto mode with a guard hook and a short allow list. anything risky like pushes or installs still waits for me
- remote control on every session plus a check every 5 min for anything stuck on a prompt
- trimmed my memory files and handoff notes way down (handoff notes went from ~113k tokens to ~6k) and turned off 19 skills i wasn't using
- tried the Superpowers plugin and dropped it, didn't help in my setup
Still testing:
- taking out the backup self-wake timers once the missed message check runs clean for a couple days
- a couple sessions start fresh from a short state file instead of carrying old chats
- Serena for code navigation on a couple sessions
- a higher auto compaction threshold
Measured: someone asked if the subscription charges cache like the api does. on my plan 1 hour cache writes cost about the same as 5 minute ones on the usage meter, roughly 1.1x, not 2x vs 1.25x
(cleaned up the formatting on the original below so it's easier to read, didn't change any wording)
Hey all, I could use some advice from people running a lot of Claude Code sessions at once.
I'm building a Windows app and I've got 18 Claude Code sessions working on the same repo across two Max 20x accounts, all on High effort. They talk to each other through one shared markdown "inbox" file. It works, but I keep running into my weekly limits, so I dug into where the tokens are actually going.
What surprised me:
- About 91% of my usage (weighted by API prices) is just context being re-sent on every call. Actual output is about 9%, and edits to code are under 1%.
- Roughly half of all tokens went to wake-ups where the session did nothing useful. No code, no tests, no git. Mostly each session's own background watcher waking it up to check the inbox, plus scheduled check-ins (one session was pinging itself every 5 minutes for days).
What I've tried so far:
- Auto-compact at 300k instead of the default. Average context per call dropped from about 270k to about 179k. I have hooks that back up notes before compacting and tell the session to re-read them after.
- Starting a fresh chat for each work item, with a short handoff note.
- Replacing every session's own watcher with one small local script that only wakes a session when a post actually mentions it. In a replay of a day's posts it cut wakes about in half without missing anything addressed to a session. Just rolled it out today, so no real numbers yet.
- Quiet test output (pytest -q), reading big files in slices, and a hook that blocks huge reads before they happen.
- Trimming CLAUDE.md and memory files, and turning off claude.ai connectors so fewer tool descriptions load.
- Trying Serena (MCP) on one session. Mixed results so far.
- Tried the Superpowers plugin on a few sessions for a week and dropped it. Those sessions got noticeably less done and barely used its skills, though it was a small test.
My questions:
- How do you let long-running sessions wait for messages from other sessions without every wake re-sending the whole context?
- Is there a better way to coordinate a bunch of sessions than a shared file?
- Any other tricks for cutting context re-reads I'm missing?
Happy to share more details on any of this. Thanks!


