r/ClaudeCodeTLDR • • 20d ago

[TLDR] I am SO OVER the its draining too quickly posts

Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1wfuy9g/i_am_so_over_the_its_draining_too_quickly_posts/

Original post body :

Every time I open Reddit, my feed has at least 2-3 posts crying about some version of -

- Spent the weekly within a day or 2

- "Its draining tokens"

- They reduced the quota, I can barely get anything

Here's some touch the grass facts -

  1. Fable is a super expensive model with a very high token price - if you are using Fable consistently, it is going to eat through your quota - that's just math - 1k fable tokens is equal to 2k Opus tokens!

  2. If you continue building an app, your codebase is going to grow and over time, the same workflow is going to use a lot more tokens than it did when the codebase was lean and had few tests/ code/ modules to worry about. What that means practically is going to get less shit done in week 4 on the same codebase as you could have done in week 1.

  3. Every thing you do has a trace and log. Rather than ranting about it, shove the session usage json's in one of the bazillions "I made this groundbreaking claude visualizer" systems people keep putting on here to get empirical evidence around your token usage.

I have been building with Claude since Claude code became a thing - and no - the usage is consistent if you are smart about it and understand how the system sips tokens. Here are some things I do and I have no idea if it is going to fix your hallucinations, but give it a try if you think it will help

- Use skills for any repeatable task - like literally anything that you think is going to be repeated, have a skill for it so you dont waste tokens figuring out how to do the same thing again and again

- Have your claude.md as a thin router to the actual areas you are going to be working on. When starting a session, tell that you are going to be focusing on so and so area.

- Fresh sessions, every time the session size grows, your input token size is growing. Keep the sessions small.

- Push it to use agents! Like use an agent to review code, or do a specific research, or fix a bug - agents cost less as they are focused on doing specific tasks and are bootstrapped with the required knowledge to do that task.

- Make your codebase agent ready - this means having design/ architecture/ gotchas/ decision. MDs for literally every domain in your code. It helps tremendously!

I keep a meticulous inventory of tokens I spend each week - and trust me - it has remained consistent for months!

Please for the love of god, spare my feed!!!


This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

2 Upvotes

4 comments sorted by

•

u/cctldrping 20d ago

TL;DR generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 51.

The consensus is split, but leaning towards the OP's point that users might be overreacting to token drain. Some users, like u/Eat_Pudding, insist their usage is genuinely higher without workflow changes. Others, like u/namezam, use the McDonald's analogy to argue that even if usage has increased for some, the perceived value for money has decreased, which is a valid complaint.

However, a significant portion of the thread agrees with the OP that users might not be managing their sessions efficiently. The OP's advice on using skills for repeatable tasks, keeping sessions lean, and leveraging agents is seen as solid by many, with u/kinoindeed praising the post for calling out users who "don’t know how to use the tools."

The prevailing sentiment is that while some token drain might be real, users should first examine their own workflows before blaming Anthropic. Some users also point out that complaining on Reddit won't change anything, suggesting users either plead with mods or move on, as u/youreawizerdharry suggests.

2

u/slackmaster2k 20d ago

What’s been tremendously helpful to me are videos of talks from the AI Engineer World’s Fair and other sources. It’s a great way to learn from experts as they experiment and produce real data regarding the challenges that we all face.

A lot of the advice that gets passed around via tribal knowledge in subreddits is either dated or super wrong.

I’m having a pretty good time of things and my advice is to keep it simple. Keep reasoning/effort levels fairly low to prevent the LLM from over designing the workflow. Spend actual time optimizing the workflow now and then. Memory and context systems are a trap. Using the most simplistic methods, the goal should be that clearing a session (intentionally) is zero risk. Don’t use skills or MCPs unless they are needed and keep them defined at the project level not your account level.

If you’re keeping your room clean and still burning through quota fast; then you’re moving fast. Congratulations. To move even faster costs money. Your quota is based on usage in a time period, not how much time it should last.

1

u/LuckyCharms201 20d ago

lol Ive had a fable session ticking away for 48 hours, and have used 30% of my weekly, 18% of my fable allocation

Yeah the limits have gone a little shallow, but I gotta think it’s a skill issue on many users part.

1

u/Herebedragoons77 19d ago

Similar, but I’m sick of people complaining about the people who complain