Real world Example
For anyone out there who isn't using AI for tasks such as coding support and might be a bit baffled by some of our complaints, I thought a real-world example [as best as I can manage] might help give an insight as to the obscurity and inexplicable "costs" when running sessions with a model.
What you see below is an exchange at the end of an 90-minute session with Claude Opus, Anthropic's most powerful [and thus most token-expensive model].
We've just spent > 80 minutes chasing a couple of defects to ground. One was in a multi-form, "Create New Record" type setup, written in a single re-entrant PHP script. The other was to diagnose a fault in a complex, context-sensitive and authorisation-driven menu framework (which I wrote and Claude broke). It was a very productive session and as you can see, all that problem diagnosis - and then a counted 7 cycles of me doing unit testing, failure-capture testing and regression testing on the "create" code, with Claude diagnosing reported oddities by scraping log files in real time.
That was 74% of a session's token allowance.
Then, as the log below shows, Claude:-
1. Ran 7 commands [that's me giving Claude access to my BASH script library to reduce cost of doing stuff]
2. Performed 3 git commits - that's literally entering 3 statements on my behalf and letting git do the heavy lifting...
3. Documenting where we had reached and next steps by editing 4 files:-
3.1. A summary of what we did this session
3.2. Updates to our snagging list
3.3. Updates to "CLAUDE.md", which is basically our "Big Rules for this Project", which I required Claude to read at every session start
3.4. Putting down a skeleton of our "Next session brief" for me to edit/refine off-line.
You're going to have to take my word for it that the above is trivial when compared with the 50+ minutes of deep triage and unit testing we just did.
The entirety of what follows took maybe 2 minutes to complete.
But... before I closed down the session, I went and checked my token usage - and I was apparently and miraculously at 100% - not a percent under, nor over. [You get an amber pop-up warning window when you actually hit 100%]. So that's 26% of a session's token allowance to create scratch notes of what we did and what comes next - basically a dump of what it's holding in session storage.
I don't know for sure - I'm not sure how I could test this in real time - but it looks to me that the moment we hit my objectives for that session and the documentation was complete, token usage miraculously jumped to *exactly* 100%. Not 99%. Not 101%. *Exactly* 100%. What are the odds of that, eh? Twice now, in a week as a paying Claude user.
I shall be checking every session from now on.
Don't get me wrong, the Anthropic models are stunningly effective. But there are some deeply fishy behaviours when it comes to token consumption. Top tip for anyone starting out using Claude for this sort of thing: Take the time to read up on how to get the best out of your Model-of-Choice. Look for articles like this:-
https://faizkhan3597.medium.com/98-of-your-claude-tokens-are-already-wasted-heres-how-to-take-them-back-6a758565d28c
with plenty of concrete proposals, then experiment with them. There are quite a few YT videos out there with similar content. If you're paying for access, it's in your best interest to be aware of how to get the best of of the resource.
Me: Re-test complete. urDefault is good; urCreatorRef is good.
Me: Session Usage at 74%
Claude: FP6 is signed off. Marking #9 and proceeding straight to the commit per the three-commit recommendation from the previous session's brief. Will go quickly to leave room for the end-of-session brief.
Claude: Ran 6 commands, used 2 tools
Claude: Ran 6 commands, used 2 tools
Claude: Commit 1 — 25-May unblockers:
Claude: Ran a command
Claude: Ran a command
Claude: Commit 2 — FP6 deliverable:
Claude: Ran a command
Claude: Ran a command
Claude: Task list is in good shape. Continuing with commit 3 of 3.
Claude: Ran 2 commands
Claude: Ran 2 commands
Claude: Three commits landed cleanly. Two backup files left untracked (your offline backups — safe to ignore or move to Archive).
Claude: Used a tool
Claude: Used a tool
Claude: Now updating CLAUDE.md §4 with FP6 ✅ and new commit hashes, then writing the end-of-session brief.
Claude: Edited 3 files
Claude: Edited 3 files
Claude: Now writing the end-of-session brief while we still have budget.
Claude: Used 2 tools, created a file
Claude: Used 2 tools, created a file
Claude: All seven tasks complete. Session summary:
Claude: FP6 ✅ closed and committed. Three commits:
59f1f7d — 25-May menu/auth/dispatcher unblockers
8224e59 — FP6 Add User multi-step form (with B3/B4/B5 fixes and the urDefault fix)
d002816 — Migration 019
Claude: Menu regression diagnosed (read-only, per your brief): both regressions have high-confidence root causes and small fix sketches in Daily Brief/2026-05-26 - Menu Regression Investigation.md. tracked as B-003 and B-004 in CLAUDE-snagging.md.
Claude: Snagging framework created: CLAUDE-snagging.md with seven open defects (B-001…B-007) and one closed (B-000). Housekeeping cleaned up; CLAUDE.md companion list updated.
Claude: Recommendation for next session: B-003 + B-004 fix as a quick standalone pair (one line + a six-line block removal). It removes the visual broken-window, restores the menu chain, and lets us test future modules via the navigation path rather than direct URLs — which would also reduce the practical impact of B-006 while FP7 dispatcher auth is being planned.
Claude: End-of-session brief at Daily Brief/2026-05-26 - Session 1 - FP6 Close-out + Snagging Framework.md. CLAUDE.md §4 updated with the new commit hashes and FP6 ✅.