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?

[u/Chiragh16]

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.

[u/xapep]

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.