Twitter/X

aditya (@adxtyahq) reports on 2026-05-09 that switching to WozCode fixed his…

Brief

aditya (@adxtyahq) reports on 2026-05-09 that switching to WozCode fixed his Claude Code token-limit problem: sessions that previously died in ~30–40 minutes and sometimes consumed ~8% of a $200 Anthropic plan now hold up. He claims Claude Code made separate tool calls and reprocessed prior context repeatedly, while WozCode batches calls to prevent context buildup and sustain sessions as part of his workflow.

Source evidence

finally not burning through Claude Code limits in like 30-40 mins anymore

been using WozCode for a week now and this is the first time Claude Code is actually sticking as part of my workflow

before this it was always:
too many tool calls → context buildup → limits hit fast → workflow falls apart.

with WozCode installed from the start, sessions just hold up way better

if Claude Code limits frustrated you before, this is probably for you.

aditya (@adxtyahq)

found a way to stop Claude Code from burning tokens

been seeing prompts eat ~8% of a $200 anthropic plan and it made zero sense

tried Claude Code twice in the last 2 months. both times I got excited, hit limits way faster than felt reasonable and gave up

turns out it’s not even the work. Claude Code just isn’t optimized for how sessions scale

it makes separate tool calls and re-processes prior context every time
so mid-session you’re paying for the same tokens again and again

that’s why costs spike out of nowhere

found WozCode and tried it this week
it batches those calls so context doesn’t blow up

sessions that used to die early now actually run properly

— https://nitter.net/adxtyahq/status/2051568016329187678#m