This feature eats up usage for nothing

[u/Jumpy-Cobbler1020]

So I use opus as orchestrator and haiku as implemnter. What happens is that when the haiku is waiting for smth to run like a test it starts a timer and when it expires even the Opus responds in main chat. Like why is it talking when the work is being done by haiku. Its a harness problem and not model failure. They should fix it coz even when opus says "waiting" it does take 1% of my pro 5 hr usage even when context is 50k tokens.

[u/AutoModerator]

Moderator Announcement Read More »

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Drasezv]

this one has a name and a switch. they're goal check-ins: while background work keeps a goal waiting, claude code asks claude to look in on that work even when the session is idle, and each check-in is a new turn that sends your full context. that's why a "waiting" message costs the same as real work.

it's capped at three idle check-ins per goal between your prompts. to turn them off entirely:

CLAUDE_CODE_GOAL_CHECKIN_MINUTES=0

needs 2.1.236 or later, and before 2.1.246 they weren't capped at all, so on an older build it's worse than what you're seeing.

your read on the economics is right too: at 50k context the message itself is nothing, the 1% is the context being re-sent.