r/WOZCODE

Been on Max for a while. Kept hitting my limit mid-task and assumed I was just doing too much. Turned out I wasn't doing too much. My tools were just incredibly inefficient under the hood.

Traced a single refactor task. One rename across a few files. Claude Code ran 161 turns to finish it. Every read, every grep, every edit is its own API call. Each one re-ingests everything before it as input tokens. By turn sixty you're paying context cost on the entire session history.

Once I understood that I started looking for ways to batch the calls. Found a Claude Code plugin that collapses search and read into one call and stacks all edits into one roundtrip. Same task finished in 52 turns.

Didn't change my plan. Didn't change my model. Just changed how many roundtrips each task makes.

Been using Claude Code heavily for the past few months. Started noticing sessions on larger codebases felt sluggish in a way I couldn't explain. The model wasn't struggling. It just felt... slow between actions.

So I actually traced what was happening under the hood during a straightforward task renaming a hook across three files.

This is what Claude Code ran:

Glob to find the files. Grep to filter which ones had the hook. Read on file one. Read on file two. Read on file three. Edit on file one. Read on file one again to verify. Edit on file two. Read on file two again to verify. Edit on file three. Read on file three to verify.

That's 11 calls. For one rename.

The part that surprised me most each call re-ingests the output of everything before it as input tokens. So by call 11 you're paying input cost on the entire session history. The slowness wasn't latency. It was context ballooning across a dozen roundtrips.

The fix is simple in theory. Batch the reads into one discovery call. Batch the writes into one edit call. Same outcome, fraction of the roundtrips.

I ended up switching to a Claude Code plugin called WOZCODE that handles exactly this. Cut the same task from 11 calls down to 2. But even without it, just knowing what's happening under the hood changed how I think about structuring tasks.

Curious if anyone else has dug into their call counts or found other ways to reduce roundtrips.

https://reddit.com/link/1tdfqik/video/u27qzhjjz61h1/player

Been using Claude Code pretty heavily for the past few months. Bug fixes, refactors, shipping features the whole thing. At some point I realized I had zero idea what each session was actually costing me. I knew it was adding up but I could not see the breakdown anywhere. Tokens, turns, money per task all just running in the background.

So we built something to fix that. It is called WozCode and it runs as a plugin directly inside Claude Code. No separate tool, no demo repo, no fake workload.

You run /woz-benchmark inside your actual codebase, pick a real task you would normally do, and it shows you exactly what that task cost tokens used, turns taken, total spend. Then it shows you what the same task costs with WozCode optimizing the session.

https://reddit.com/link/1tbdr1i/video/mdcs6n9qnr0h1/player

The numbers were honestly kind of embarrassing when I first saw them. Not in a catastrophic way but in a "I cannot believe I did not know this" way.

If you are on Claude Code and curious what your workflow is actually costing you, just run it in your own repo. Takes 30 seconds to set up and you do not need to create an account to start.

https://reddit.com/link/1taas41/video/6xwo0uskqj0h1/player

Getting started with WOZCODE takes 30 seconds.

If you're already on Claude Code, open your terminal and run:

claude plugin marketplace add WithWoz/wozcode-plugin

claude plugin install woz@wozcode-marketplace

Launch Claude Code, type /woz-login, authenticate in the browser, and you're live.

The only prerequisite is an active Claude subscription. No extra setup. No new workflow to learn. WOZCODE runs directly inside the environment you're already using.

From your very first session, every token used, every dollar spent, and every minute saved gets tracked automatically on your dashboard.

That's it. Two commands and you're in.

wozcode.com

I'm running Wozcode for my coding tasks and it's handling most of what I need pretty well. The one thing I'm stuck on is token usage.

I've noticed some prompts burn through tokens way faster than others, and I'm not sure if that's normal or if I'm doing something wrong in my setup.

Have you built any simple checks or habits around this? I'm trying to keep costs reasonable without obsessing over every single request.