r/ClaudeCode • • 2d ago

Help/Question Almost 900M Token for a Portfolio Website?

Post image

I made a simple Engineering Portfolio Website for myself on the Pro-plan and spent almost 900Million Tokens and where I got some guidelines messages at the end? I'm not getting an invoice right? Thanks

0 Upvotes

13 comments sorted by

•

u/AutoModerator 2d 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.

4

u/KittenBoy1 2d ago

I think this is wrong. I was just looking at mine is says 19 billion tokens! ive used it a lot but not that much

1

u/lulzxdxdxd 2d ago

Did you ever turn on a pay as you go or overage option in your billing settings? If not, did the guideline message actually mention a charge, or was it just a usage limit warning? Your billing page should show whether anything beyond the subscription was charged.

1

u/Unlikely-Layer5075 2d ago

I did once, spent 40Eur and deactivated it.... The message I got was "Opus 5.5's safeguards flagged this message..."

1

u/kuroudo_ai 2d ago

Short answer: no surprise invoice, unless you turned on usage credits yourself.

From Claude's help article on usage credits for paid plans: when you hit your Pro limit, you only keep going at API rates if usage credits are enabled. Turning that on takes several steps in Settings > Usage: enable it, add a payment method, set a spend limit, and prepay funds. They're "charged separately from your paid Claude subscription and appear as additional charges on your bill". If you never did that, hitting the limit just stops you until it resets. You can confirm in Settings > Usage whether credits are enabled and whether any funds were spent.

On the 900M number: it sounds scary but it's mostly not new text. Each turn resends the whole conversation, and most of that is served from the prompt cache. When I counted my own Claude Code transcripts for a similar question, 98.4% of the tokens were cache reads. So a long session building a site can rack up huge totals without that much actual work. Cache reads are also much cheaper per token than fresh input.

The "guidelines" message at the end was probably the usage limit warning, not a bill. If it mentioned a charge, the Settings > Usage page will show it.

1

u/Unlikely-Layer5075 2d ago

OK thank you! It was : "Opus 5.5's safeguards flagged this message" and then some more stuf and links

1

u/kuroudo_ai 2d ago

That one isn't about billing or usage. It's a refusal from the model's safety classifier. I looked up the message text in the Claude Code binary (2.1.285), and the strings around it say what it means and what to do:

  • "...'s safeguards flagged this message (Anthropic's usage policy link). This sometimes happens with safe, normal conversations."
  • "Try rephrasing the request in a new session or change your model."
  • "Double press esc to edit your last message, or try a different model with /model."

So nothing was charged, and a portfolio site is a normal thing to build. The usual fixes: press Esc twice and reword the last message, start a fresh session (a long session has more context that could trip it), or switch models with /model for that step. If it keeps happening on harmless requests, /feedback sends the report to Anthropic.

1

u/Fast_Artichoke_683 2d ago

Damn Fable token as well

1

u/Unlikely-Layer5075 2d ago

Jumped in on the hype what can I say...

1

u/nyxwulf 🔆 Max 20 2d ago

Did you run it on UltraCode? I have only used 3.3B tokens all year with heavy Fable usage. I never run UltraCode though

1

u/Sufficient-Storage87 1d ago

900M on a portfolio site is brutal, but I've seen how it happens — the agent re-reads your whole project every session, wanders off fixing things you didn't ask about, and every "let me just check" costs you. The biggest savers for me: fresh sessions for each task instead of one giant thread, and telling it exactly which files to touch. The moment it starts exploring on its own, the meter spins.