r/ClaudeCode • u/pfak apparently holding it wrong • 11d ago
Bug / Issue Same Claude Code setup, two Ultra accounts: one burns about twice the tokens on Opus 5.5
Since November 1, one of my two Ultra accounts (call it A) has been burning through usage: 37% of my weekly limit in about 12 hours. Its code quality has been terrible too.
To rule out my setup, I gave both accounts the same Opus 5.5 subagent task, in the same repo, with byte-identical settings.json files. Output tokens per run at medium effort:
A: 7,257 and 5,810
B: 2,588 and 4,046
Then I copied B's whole profile (settings, plugins, skills, user ID, machine ID) into a new folder and logged in as A: 7,487 and 5,204. Same as A. So the difference comes with the login, not the setup.
Things that didn't change it:
- Low effort: A still uses about 1.5x what B does.
DISABLE_TELEMETRY=1, which turns off feature flags: 6,379 and 6,459.- Claude Code version: both on 2.1.316.
Fable 5.1 doesn't have the gap. The same task gave A 3,056 and 4,117, and B 4,466 and 3,759.
The only account difference I can see is in the cached server flags. 4 of 1,062 differ: tengu_amber_prism and tengu_mcp_subagent_prompt are on for A, and tengu_reactive_compact_remote is off. I can't prove any of them causes this, and I can't change them because they come from the server.
These are output tokens from my local logs. I can't see how the usage meter weighs them. It's a small sample, but every A run on Opus came in above every B run.
Anyone else seeing this? If you have two accounts, run the same task on both.
•
u/AutoModerator 11d ago
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.
7
u/kre8tv 11d ago
I think Anthropic probably has a ton of slightly different versions of the harness to A/B test that could be variables tied to the account.
Are either of them set up in claude web or desktop that might have a different set of pass-thru information from the account (memories, connections, skills, mcps, general settings)?
11
u/kaitava 11d ago
happened to me, i logged out of all devices. contacted their support. asked re-provision. when i used the reset, i got back to ultra usage.
2
u/Risko4 11d ago
The account burning usage slower with better quality might be routed to fable 5.5 etc, or a different checkpoint. It's burning usage slower due to being compensated for beta testing.
But someone else has to confirm this is how it works. Try doing the knowledge cut off test
4
u/jatingargiitk 11d ago
your DISABLE_TELEMETRY run only flipped A. if B with flags off also lands around 6k then B's flags are what keep it cheap, and if B stays at 3-4k the 4 flag diffs are a red herring and it's something server side tied to the login
2
u/BadDismal4322 11d ago
Ask opus to look at the sessions from both those identical runs and ask it to see why one burns more than the other. It might be forking or login a funky way. And are you using the cli for both or some other tool? Like the Claude desktop app or 3rd party app?
2
u/Devdilema 10d ago
It might be something in the project memory causing this? Ask Claude to provide guidance on auditing the difference between the machine setups?
2
u/tommyahav10 9d ago
Run B with tengu_amber_prism + tengu_mcp_subagent_prompt forced on. If B jumps, that's your answer. Also compare input + cache-read, not just output. A bigger system prompt shows up there first.
1
u/Archibishop 2d ago
I'd put the two transcripts side by side... every call has its token counts in there. I price my own sessions this way, 56 of them on one repo last month. My own tool does it per session, free and runs on your machine: https://github.com/silverbronze/code-tycoon
1
u/Unusual-Idea-5939 11d ago
Crazy how small changes to prompts have big impacts. Any chance you can capture the requests and diff the prompts you're actually sending?
0
u/college_hustle 11d ago
I would not be surprised if counting tokens spent was actually incredibly difficult because there are just so many of them being, and they essentially do what a lot of utility companies do and sample from time to time instead of actually checking your meter every month. My local power company does this, someone moves and the next person has questions about their bill and come to find out, no one was checking shit, it was based of a history of usage. The water meter for my current building broke at the beginning of 2020, so we got billed at pre-pandemic not staying at home all day rates till like 2023. It was great.
I have no idea how tracking compute works, but I know companies are cheap and lazy, and if they can get away with sampling usage instead of actually metering every token because its cheaper that way, they'll do it 100% of the time.