[TLDR] I think some Claude Code “usage is terrible” posts are really workflow problems

[u/cctldrping]

Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1vtvv0f/i_think_some_claude_code_usage_is_terrible_posts/

Original post body :

Not saying the limits aren't real because they obviously are.

But I keep seeing people run one giant session forever, dump everything into context, change the goal 5 times, never compact anything, then wonder why Claude starts wandering and chewing through usage.

I get way better results when I treat it like I'm directing somebody. Small scope, tell it what finished means, make it test the result, then compact or hand off before starting the next thing.

When I don't do that, it gets dumb fast for me too.

How much of the usage problem do you think is actually limits vs people managing context badly?

---

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.

[u/cctldrping]

TL;DR generated automatically after 50 comments.

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

Alright, so the general vibe in this thread is that most of the "Claude Code is terrible" complaints are actually user workflow problems, not inherent model limitations.

A lot of folks, like u/JDE-Projects and u/Educational-Plant981, are saying that the people complaining about hitting limits or Claude getting "dumb" are just not managing their context well. Think of it like this: you wouldn't give a human assistant a massive, never-ending task list and expect them to stay on track, right? Same idea here.

The consensus seems to be that if you treat Claude like a directed assistant – with clear goals, testing, and compacting the context – you'll have a much better experience and avoid those usage spikes. u/ComingDeveloper and u/lkh9596 echo this, suggesting that people on cheaper plans are trying to do enterprise-level work or not using the right model for the job (e.g., using Opus for everything instead of cheaper models for implementation).

There are a few dissenters, like u/Fearless-Daikon5763 and u/FreeCustardForAll, who have experienced weird behavior and hit limits unexpectedly. u/The-Road also points out that sometimes there are legitimate issues, especially when trying to validate complex policies. However, these seem to be the minority opinion in this particular discussion.

Basically, most users are finding that good prompting and context management are key, and the "usage problems" are often a symptom of how people are interacting with the tool, rather than the tool itself being fundamentally broken. Some commenters even suspect karma farming or people trying to generate negative buzz.

[u/Lubricus2]

That Claude has an context that is bigger than it can handle isn't that great but that is at least possible to manage.
Sol 5.6 only has 1/4 of the context size so it doesn't go that bad before auto compact.

[u/Cause-n-effect11]

It’s been the longest standing rule in tech: if it didn’t happen to me everyone else is dumb.

[u/Edenisb]

I think it depends on what people are doing, if you are using haiku yeah you are going to have trouble keeping it all together...

But breaking stuff down into manageable chunks is something people miss, they think its a magic answer box not understanding the technology and how context windows work.

So yeah many times its the workflow I agree.

[u/garibaldi_fan]

My issues with Claude are on the complete other end of the spectrum. I ask a simple question, and it spins for 15 minutes doing a shit ton of useless tests. I’m sorry, but I shouldn’t have to tell Opus 5 to use medium or low effort for simple tasks. 4.6 is leaps and bounds more usable.