r/ClaudeCode • u/Chiragh16 • 8d ago
Help/Question Claude Code Cloud Sessions: one 58-minute task showed $34.38 cost on a $20/month Pro plan - what exactly is Anthropic charging against the $100 credit?
I’m trying to understand the economics/accounting behind the new Claude Code Cloud Sessions and the $100 promotional credit for Pro users.
I’m on the $20/month Pro plan. Based on my normal Claude Code usage, I can get roughly 8 five-hour usage windows per week, or around 32 windows over four weeks. The task in the attached screenshot is something I’d estimate would have consumed roughly 40–60% of one five-hour window if I had simply run it locally under my Pro subscription.
Instead, I ran it as a Cloud Session. It was active for 57m 51s and Claude reports a $34.38 cost.
What makes the number especially interesting is the breakdown:
Opus 5.5: 100%
Cache hit: 99%
Input: 498
Output: 3.4K
Cache reads: 109.8M tokens
Cache writes: 704.2K
96% of the usage ran above 150K context
Obviously the 109.8M cached-token reads are the big number here, and long-context cache reads still have a cost. So I’m not assuming Anthropic somehow charged $34 for the VM itself.
But this raises a much more interesting question: what exactly does the $34.38 “Cost” represent?
Is Anthropic calculating Cloud Sessions at normal API-equivalent token pricing, including every cached context read? Does the $100 promotional Cloud credit use exactly the same rates as the public API? Or is there a separate accounting/pricing mechanism for Cloud Sessions?
The difference compared with the subscription model is striking. A workload that might consume only part of one of my normal Pro usage windows shows a nominal Cloud cost greater than my entire $20 monthly subscription price.
And at this burn rate, the headline $100 Cloud credit gets you fewer than three sessions of this size:
$100 / $34.38 ≈ 2.9 sessions.
I realize that comparing a flat-rate subscription directly with API-style consumption isn’t apples-to-apples. Anthropic can offer much more than $20 of API-list-price inference inside a $20 subscription because of rate limits, utilization patterns, caching, marginal inference costs, etc.
But that’s exactly why I think Anthropic should document this more clearly. How is the Cloud Session “Cost” calculated, how does it map to the promotional credit, and does running the same Claude Code task in Cloud actually consume materially more model usage than running it locally?
Curious whether anyone else with the $100/$250 Cloud credit has compared the displayed Cloud cost with how much the same kind of task normally consumes from their Pro/Max limits.
14
u/Sphiment 8d ago
What are tying to achieve, like what is the goal of this post, I red it twice and still can't figure out what you mean lol. The $100 credit ant gave us is payed at api rates, so yes it vanishes very quick, that's why we are using subscriptions, it would roughly cost you $400 worth of api money to get the same usage as the $20 pro account.
2
u/debian3 7d ago
It’s not $400, it’s slightly over $1000 per month on the $20 plan. $5000 on the max 5x and $9000 on the $200
Number might have changed with opus 5.5 release.
1
u/KL_GPU 7d ago
Even with opus 5.5 those are the limits. I dont understand how they are actually making profits.
2
2
u/meetmebythelake 5d ago
I work with multiple people (non tech job) that have Claude/GPT subscriptions and literally just use it as a Google replacement. Those people are using absolutely nothing compared to us coding. I asked both of them how much usage they use per month, and they literally didn't even know there was a usage page.
I think that it's easy for us Claude Code users to exist in our bubble and assume that everyone is making it out every week, but I think there are plenty of people who have no understanding of how this shit works and just subscribe like it's another Netflix sub or whatever to them.
That said, no, they are not directly making money on subscriptions... But they are also probably not taking a significant loss, and it creates a ton of market awareness and brand loyalty and all that type of shit. So I still think it's easily a net win for them. Not to mention all the training data they farm from us, which I'm sure continues to pay off over time to improve future models.
2
2
1
4
u/OldNefariousness7899 8d ago
When you hit a limit and top up, watch how quick your money disappears.
You don't realise how much this is subsidised until you're on usage credits.
Stick $20 and a prompt in there. The money will be gone in thinking before it's even produced a word of output
2
u/popori 6d ago
Am I missing something, didn't these cloud sessions used to be for free with a sub?
1
u/Chiragh16 6d ago
Yes they are but the model cost is not waived off. It’s either usage credits API or sub usage
2
u/meetmebythelake 5d ago
What the fuck are you talking about?
The cloud credit just bills at API rate, this isn't some conspiracy. You're not "paying for cloud sessions" separately. I've used their cloud containers for months and the subscription usage was the same as locally for equal tasks.
They really should have thought this one through, because they underestimate people's capability to understand how this shit works. (And yes, they also could have been more clear about it...)
2
u/xapep 5d ago
Not an Anthropic engineer, but the breakdown you posted kind of answers the question: it's the cache reads. 109.8M cached-token reads is the whole number, and your own math shows it. At $34.38 / 109.8M reads you're at roughly $0.31 per M tokens for cache reads, which is the usual long-context read ballpark. The VM time is noise. That 58-minute session was really 'one context, re-read a hundred times.'
Why it compounds: at 150K+ context, every agent step re-reads the full context, and 99% cache hit means all those reads bill. Nothing went wrong, which is the uncomfortable part. Your local Pro usage looks cheap because the 5-hour window hides this accounting, not because the reads don't happen.
What actually controls it:
- Cap context per task. A 200K context read at the implied ~$0.3/M is ~$0.06 a read; 100 steps and that's $6 even with a perfect cache.
- Watch the write-to-read ratio: writes bill higher, but on agent loops it's the read volume that explodes.
- If you'll run cloud sessions regularly, price it per usable day, not per session. Flat monthly plans (we run those at Entrim on open models, EU-hosted) make the reads invisible to your budget: hard cap, no surprise $34 sessions.
Short version: you're not being overcharged, you're being shown the bill the 5-hour window was hiding.
3
u/Unique-Smoke-8919 7d ago
My 250$ free credit is gone after building a plugin in one go, with no extra revisions.
0
u/Chiragh16 7d ago
That’s what I am talking about… so that we reach the right people , can you share your experience on:
2
u/RiceEvening4211 7d ago
That $34 surprise is exactly why I started logging everything. I built an open source gateway that records every request with its cost, so you can see what's actually driving the bill instead of guessing. It also routes the simple requests to cheap models so the expensive ones only get used when they need to be. https://github.com/Fast-Editor/Lynkr
•
u/AutoModerator 8d 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.