Twitter/X

Author @hasantoxr reports discovering that Claude Code's…

Brief

Author @hasantoxr reports discovering that Claude Code's architecture—re-ingesting prior context on every tool call and reading each file as a separate round trip—was causing repeated token charges. After a week with WozCode (80% on TerminalBench 2.0) and checking /woz-savings, two commands eliminated the cost gap on last month's bill without changing his workflow.

Source evidence

I didn't know cutting my Claude Code costs could be this simple.

I spent three months assuming the bill was just part of using a good model.

It's not.

Claude Code re-ingests prior context on every tool call.
Every file read is a separate round trip.
You pay for the same tokens repeatedly. Every session. Every day.

I ran WozCode for a week to see if the fix was real.

→ 80% on TerminalBench 2.0
→ /woz-savings showed a gap I couldn't ignore on last month's bill
→ Two commands. Nothing changed in how I work.

The problem was never the model.

It was the structure underneath it.

Two commands fixed what three months of manual optimization couldn't.

Video