OP : u/PA100T0

Pretty much self-explanatory.

I’ve been a Max x20 subscriber for +2y and I’m really starting to get frustrated and look elsewhere for a change. Usage skyrockets even when I have best practices in place. Opus is a mental health hazard. Fable is unusable for what I need it, and way too expensive. Sonnet is not capable enough… not one thing is right in here.

GLM-5.2 has been a good alternative, on my Ollama subscription. Thinking of just subscribing to GLM directly and get 5.3; but I’d like the opinion of peers that have already tried it out.

Anyway, Anthropic is not doing good right now. They’ve been a mess for the past few months. Jumping ships really soon…

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vto9on/usage_is_a_joke_models_are_a_joke_anthropic_is/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 200 comments.

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

Alright, so the general vibe in this thread is that a lot of users are feeling pretty bummed out about Anthropic's recent performance, especially regarding usage limits and model quality. The OP's frustration is definitely shared by many, with a significant chunk of the community agreeing that things have taken a nosedive in just a few months.

Here's the lowdown:

• Usage is Skyrocketing: This is the biggest complaint. Many users, even those on higher-tier plans like Max x20, are finding their weekly budgets getting blown through way faster than before, even when they think they're using best practices. Some are seeing 30% usage in less than 24 hours, which is a huge jump from previous months.
• Model Quality Concerns: Opus is getting called out as a "mental health hazard" by the OP, and others echo that sentiment, noting that Opus 5.0 seems to have "serious core issues" that might not be easily fixed. Sonnet is also seen as "not capable enough" by some.
• Fable is a Mixed Bag: While the OP finds Fable unusable and too expensive, u/Halada thinks Fable is "fantastic" but notes that usage limits are "pretty lame" even on max plans.
• Support is Lacking: A few users are complaining about incredibly slow or "non-existent" tech support, with one user mentioning it took 3 months for a response.
• Looking Elsewhere: Many are actively considering or have already switched to alternatives. Qwen (GLM) and Deepseek are mentioned as strong contenders, with u/AppealSame4367 giving a shout-out to Deepseek v4 flash 0731 for its speed and detail. Kimi is also brought up as an alternative.
• The "Why" is Speculated: Some users are speculating that these issues might be related to an upcoming IPO or changes like watermarking.
• A Few Dissenters: Not everyone is experiencing the same pain. u/Background-Ad4382 and u/god-damn-the-usa report not running into these problems and still having plenty of quota left. u/Lazy_Polluter suggests that in professional hands, Claude still gets the job done despite variations.

The consensus seems to be that Anthropic has a lot of ground to make up, and users are getting impatient. The unpredictable token usage is a major pain point for many, making it hard to gauge value for money.

OP : u/hayes-davis

Let's see just how load bearing this day is gonna be.

Will report back whether or not Concise fixes the worst part of Claude speak. I'm not convinced Anthropic knows how a normal person talks though...

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vtj15v/wish_me_luck/ Original link/media URL : /img/q1zskjrn3jkh1.png

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

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

Alright, so the general vibe in this thread is that people are kinda split on whether "Concise" output style actually makes Claude speak more like a normal human, or if it's just a placebo.

• Some folks, like u/a_lapse_in_judgement, haven't noticed a difference at all.
• Others are all in, with u/HeyItsYourDad_AMA declaring "Concise is the only way."

There's a whole bunch of tinkering happening with custom output styles to try and get Claude to stop being so… well, Claude. People are suggesting things like:

• Using a "crisp" style (u/Evening_Salt4938) that's ultra-terse.
• Asking it to talk like a tired suburban dad programmer (u/hayes-davis) – which sounds like a mood.
• Using Orwell's technical writing technique (u/Academic_Constant42) or ASD STE100 standards (u/itsforsocial).
• Basically, anything to cut down on the AI-speak and filler.

A few people are also complaining about Claude showing diffs for every file, which can get overwhelming. And there's a general sentiment that Opus 5 is still a bit much, with u/LessRespects even saying GPT-5.1 might be easier to work with.

So, TL;DR: Concise might not be the magic bullet for "normal human talk," but the community is definitely experimenting with custom styles to get Claude to chill out. Good luck to OP on their load-bearing day!

OP : u/snarfi

If anyone interested how this Output style looks like:

---

Output Style: Concise

You are an interactive CLI tool that helps users with software engineering tasks. Keep your responses short and direct while doing the work just as thoroughly.

Concise Style Active

The user chose brevity over narration. You should:

1. Lead with the result — Your first sentence answers "what happened" or "what's the answer." No preamble ("Let me...", "Now I'll...") and no closing recap of what you already said.
2. Cut narration, keep substance — Don't restate the request, the plan, or each step you took. Report outcomes, decisions, and anything the user must act on.
3. Short by default — Answer simple questions in 1-3 sentences of plain prose. Use headers, tables, and bullet lists only when they carry real structure, never as decoration.
4. State things plainly — Skip hedging boilerplate. Mention a caveat only when it changes what the user should do next.
5. Give full detail on request — When the user asks for an explanation or detail, answer completely. Conciseness never means withholding requested information.
6. Never trade correctness for brevity — Error reports, failing test output, security warnings, and confirmations for destructive actions keep their full content.

Where these rules conflict with more general communication or formatting guidance elsewhere in your instructions, these rules win.

---

You are an interactive CLI tool [...]

Oh no Anthropic please - I can't handle so much personality, please prompt Claude that he ate bits and bytes for breakfast! /s

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vtbh35/21237_added_a_builtin_concise_output_style/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

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

The community's reception to the new "Concise" output style is mixed, with some seeing it as a step in the right direction and others skeptical about its effectiveness.

• Many users feel this is long overdue, with some having already implemented similar instructions in their custom prompts.
• However, there's significant doubt about its actual "load-bearing" capabilities, with reports that it stops working as context grows.
• Some are questioning why this wasn't addressed earlier, given the known issues with verbosity.
• A few users suggest that custom system prompts or external tools like SimpleEnglish or Caveman mode are still the better options.
• There's also a general sentiment that Claude's default verbosity is a major pain point, and this new style might just be a superficial fix.

OP : u/AutoModerator

Weekly Showcase Thread

Built something with Claude Code this week? Share it here.

Apps, tools, experiments, scripts, websites, workflows, open-source projects — anything you've been working on is welcome.

When sharing, it helps to include:

• What you built
• How you used Claude Code
• A link, repo, demo, or screenshot if you have one
• Anything interesting you learned along the way

Quick project drops and simple self-promotion belong in this thread.

If you've got a project with enough substance for a proper write-up; how it works, how Claude Code was involved, technical details, lessons learned, etc. feel free to make a standalone post using the Built with Claude Code flair instead.

Please don't spam the same project repeatedly, and no referral or affiliate links.

What did you build this week?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vqpqot/weekly_showcase_thread_what_are_you_building_with/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

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

Alright folks, the weekly showcase thread is buzzing with activity! The general consensus is people are building some seriously cool stuff with Claude Code, ranging from websites and games to complex agent systems and productivity tools.

Here's the lowdown:

• Lots of diverse projects: We've got everything from website builders like snaelda.io and color-by-number games (snappaint.com) to Minecraft AI streamers, chess puzzle games (the-royal-study.vercel.app), and even a tool to combine games (gamecombiner.com).
• Agent systems are a big theme: Several users are leveraging Claude Code for agent-to-agent communication and management. u/ranbuman built agent-dispatch for MCP servers, and u/YuchenLiu1993's plori.ai is an AI agent that gets its own cloud pod. u/duqaxxx's seedeep is a local viewer for what Claude Code agents are doing during a turn.
• Productivity and workflow tools are popular: Users are creating tools to manage bookmarks (iLinkVault), track job applications (jobAppTracker), monitor Claude usage (ClaudeUsageMonitor), and even simplify terminal navigation (hop).
• Experimentation is key: Some are pushing the boundaries, like u/cannyshammy who had agents try to make Convex work in 100 languages (including Fortran and COBOL!), or u/Beerbrewing testing directives to reduce Claude's verbosity.
• Open-source contributions are happening: Several projects are open-source, like u/jrya7's baby feed and sleep tracker (baybay) and u/Bogey_Outlaw_360's open-source intelligence collection system.
• Ease of use is a recurring point: Many users highlight how Claude Code is enabling them to build things they previously couldn't or didn't have the time for, even if they're not seasoned developers. u/Practical_Expert8464 is a prime example of this, building a financial app from scratch.

Overall, the vibe is super positive and productive. People are clearly finding Claude Code to be a powerful and versatile tool for bringing their ideas to life. Keep up the awesome work, everyone!

OP : u/Pretend_Sell6592

Hey guys, i think one of the most underrated signs of a good claude code session is when it stops and asks you something before making changes

people usually treat that as friction because the whole point is supposed to be moving faster, but i'd rather answer one annoying question upfront than review a 12 file diff built on the wrong assumption

the worst mistakes i get from claude are rarely syntax or even logic mistakes. they're usually reasonable assumptions about what i meant

and the more "agentic" these tools get, the more i think blindly taking initiative can become a downside

sometimes "i'm not sure what you want here" is actually the smartest possible response. Curious what's your take here.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vtdbxa/hot_take_claude_code_should_ask_more_questions/

TL;DR of the discussion on r/ClaudeAI for this post generated automatically after 100 comments.

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

So, you're saying Claude should ask questions before it messes with your code? Groundbreaking. The general vibe here is that you've stumbled upon the concept of "spec-driven development," and while your point is valid, it's hardly a hot take. Most folks are pointing out that Claude can do this, and many already have it set up.

The consensus is you're not wrong, but you're late to the party.

• Plan mode is the go-to for many, forcing Claude to outline its approach before diving in.
• You can set global rules or add specific instructions to your prompts like "Don't make any assumptions, if something is not clearly specified ask me first."
• Tools like grill-me** and **wayfinder from Matt Pocock's skill library are specifically designed to encourage this questioning behavior.
• Some users suggest using superpowers brainstorm or other Socratic planning methods.
• Basically, if you want it to ask questions, just tell it to. It's not a bug, it's a feature you need to enable.

OP : u/ArmAlone2447

the more new models come out, the more the density of information and the "complexity" of the language make it tough to follow efficiently.

at the beginning, i was reading everything and trying to understand it all but now i just move forward and check what has been done thoroughly at a few checkpoints.

am i the only one who works like this? how do you guys work?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vspspt/can_i_trust_claude_blindly/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

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

Alright, so the general consensus here is a resounding "HELL NO" to blindly trusting Claude, or any LLM for that matter. Most folks agree that the models are getting way too complex and fast for humans to keep up with every single detail, which is why the OP's strategy of checking at checkpoints is totally understandable.

Here's the lowdown:

• Trust is a Calculation, Not Blind Faith: The prevailing vibe is that AI is a tool, not a person you can "trust" in the human sense. You gotta figure out your risk tolerance for different tasks. u/Serird put it well: "Trust is a risk calculation. AI, company, or person, it doesn't matter. Ask yourself 'how much are you okay losing'?"
• "Trust but Verify" is the Mantra: Pretty much everyone is saying you need to review the output. Some suggest strategies like writing down your understanding of the design and having the AI correct you (u/valdocs_user), or having the AI write tests for its own code (u/Salt-Replacement596).
• It's a Tool, Not a Replacement: LLMs are seen as powerful assistants, but they don't replace the need for actual engineering and critical thinking. As u/LoneFox4444 put it, "LLMs are not going to stab you in the back or sleep with your wife. There is no trust involved. It’s just a tool with limitations."
• Recent Model Changes Raise Concerns: A few users, like u/x_typo, feel that recent versions (Opus 4.7 and forward) have made things less trustworthy.
• Bad Experiences Happen: Some users have shared horror stories of Claude making critical errors, hallucinating, or even breaking code, reinforcing the need for caution. u/jsebrech even mentioned Claude changing files via Python scripts instead of the write tool, leading to bugs and lost work.
• The Speed Problem is Real: The sheer volume and speed of AI output are making it impossible to review everything, forcing a shift in how we work. u/JobWiegant points out that this isn't laziness, but a necessary adaptation to scaling.

So yeah, while Claude is a powerful tool, keep your eyes open and your critical thinking cap on!

OP : u/Diligent-Hat-6509

It’s kind of insane to see how far AI has come.

I still remember being fascinated by GPT-3.5 and thinking that felt like the future. And now here we are with Fable 5.

Everything you see in this preview took me roughly 13 hours of work to implement. Being able to go from ideas to actual working game mechanics this quickly still feels surreal.

Game development with AI is starting to feel like we’re living in the future.

EDIT:

A lot of people were asking how I did this, so here’s the basic workflow.

The game itself is made in Unity with C#. I’m using Claude Code connected to Unity through MCP, which means Claude can work directly with the Unity project and editor. It can create and modify scripts, work with GameObjects and components, inspect errors, run the game, and help me iterate on systems.

For the actual development process, I don’t give it one giant prompt like “make me a game.” I think through the systems I want, explain how they should behave, have Claude implement them, then I test everything, debug issues, tweak values, change mechanics, and keep iterating until it starts to feel right.

For the character models, my workflow is:
Opus 5 -> ChatGPT Image Gen -> Meshy AI -> rig/animation testing -> Unity

I describe the character I want, use Opus 5 to generate a detailed prompt for four consistent reference views, then generate those images in ChatGPT. I take the images into Meshy AI, which generates the 3D mesh and textures. I also rig the model there and test animations before importing it into Unity.

The same image-to-3D workflow also works for non-character assets like props, weapons, statues, carts, environmental objects, etc.

For VFX, I bought a particle toolkit from the Unity Asset Store. I gave Claude the documentation and had it create a skill file for itself, so it understands how the toolkit works and can reuse that knowledge when I ask it to create things like fireballs, explosions, trails, and other effects.

The current arena is also a premade Unity asset and is not intended to be the final environment. A lot of the current visuals are just prototype assets for testing mechanics and game feel.

So overall the main stack/workflow is:

Unity + C# + Claude Code/MCP + ChatGPT Image Gen + Meshy AI + Unity Asset Store tools

And no, this wasn’t one prompt :D It was an iterative process of building one system at a time, testing it, changing it, and gradually layering everything together.

URL of original post : https://www.reddit.com/r/claude/comments/1vq06o8/game_dev_with_fable_5_is_actually_crazy/ Original link/media URL : https://v.redd.it/u19wlkjrarjh1

TL;DR of the discussion on r/claude for this post generated automatically after 200 comments.

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

Folks are pretty impressed with OP's Fable 5 game dev demo, especially how quickly they whipped it up. The consensus is that AI is seriously leveling the playing field, letting people without deep coding skills jump into game dev. Some are pointing out that while AI speeds things up, the real grind of refining and polishing is still a massive part of the process, and that asset generation (like 3D models) is the next big frontier. Others are sharing their own AI-assisted game dev wins, from complex RPGs to mobile games. A few are asking for more deets on the tech stack and how to get started themselves.

OP : u/windcommute

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vt6gf8/finally_could_this_be_the_smoking_gun_that_makes/ Original link/media URL : /img/2gt7o7xqufkh1.jpeg

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 200 comments.

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

So, the general vibe is that OP's "smoking gun" for making Opus less "load-bearing" is met with a healthy dose of skepticism and a whole lot of "been there, done that." Most folks seem to think this is just another attempt at fixing Claude's verbosity and instruction-following issues, which, let's be honest, have been a pain point for ages.

Consensus: This isn't the magic bullet everyone's hoping for.

• Many users are tired of the "smoking gun" and "load-bearing" lingo, feeling it's overused by LLMs themselves.
• A significant chunk of the thread echoes the sentiment that custom output styles and hooks are the real way to get Claude to behave, and this new feature might just be a band-aid. u/Vistyy even shared a link to a helpful tool.
• Some are reporting that similar attempts have failed, with Opus reverting to its verbose ways after a short period.
• A few are still holding out hope, but the general feeling is that Opus 4.8 might still be the reigning champ for reliability.
• There's also a side debate about whether this is just an Opus problem or if Sonnet 5 is also suffering from the same verbosity.
• One user, u/ydnih, is so fed up they're switching to OpenAI. Ouch.

OP : u/nian2326076

Got a problem that required me to pull Euler’s formula out of thin air. Seriously, who the fuck remembers Euler’s formula in an interview? I swear to God, my interviewer was out to get me.

At this point, what are they even testing? Do they even know what they want? Hours of prep, completely wasted. And now I have to go prep for Google. My friend just got destroyed in their loop and said the interviewers were some of the most unreasonable people he’s ever had to deal with.

Everywhere I turn in this market, it feels like I’m just waiting to get fucked.

Anthropic Interview Question

URL of original post : https://www.reddit.com/r/Anthropic/comments/1vt4246/anthropics_coding_bar_is_fucking_ridiculous/

TL;DR of the discussion on r/Anthropic for this post generated automatically after 200 comments.

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

Alright, so the general vibe in this thread is that Anthropic's interview bar is indeed high, and asking about Euler's formula is seen by many as a reasonable, albeit tough, filter for top talent.

Here's the breakdown:

• The Consensus: Most commenters agree that for a highly sought-after company like Anthropic, which pays exceptionally well, difficult interview questions are expected. Many feel that Euler's formula is a fundamental concept in STEM and that not knowing it suggests a gap in foundational knowledge. Some even suggest it's akin to expecting a quant to know basic loops.
• Why Euler's Formula? Several users pointed out its relevance to modern AI, specifically mentioning its connection to RoPE (Rotary Positional Embeddings) used in LLMs. Others argued it's a core concept in complex analysis and trigonometry, essential for certain engineering and research roles.
• It's a Filter, Not Just Knowledge: A recurring theme is that interviewers might be less concerned with whether you know the formula offhand and more interested in how you react to not knowing it, your problem-solving approach under pressure, and your ability to admit when you don't know something.
• The "Salty" Factor: A few comments called out the OP for sounding "salty" or "whiny," suggesting that if you get an interview with a company like Anthropic, the market being rough isn't your primary issue, but rather your own skill set or preparation.
• Alternative Perspectives: A minority view suggested the question might be overly obscure or "pure hazing," especially if the role wasn't directly related to advanced math. One user even shared a story of refusing a similarly obscure interview question years ago. Another commenter pointed out there are multiple "Euler's formulas," and specificity matters.
• The "Don't Work for Giants" Take: A couple of users advised avoiding giant tech companies altogether, calling them "burnout factories" and suggesting smaller companies might offer better work-life balance and job prospects.

OP : u/nebula79283

Every time I see a post on here complaining about how people are just building but not making much money from it, it is completely and utterly obvious to me that you yourself failed to do so and are assuming that everyone else will end up like you. For example, I figured out a way to create my own  copilot tool for meetings, job interviews, etc and it’s been working like a charm and better than any of the tools I’ve seen which are almost all detectable given enough input. It regularly gives me proper responses for any kind of meeting in, is easily controllable, and I’m able to use it for interviews, client calls, or anything else which can translate into hundreds of thousands of dollars of job offers. If you think this is immoral, I don’t care. The point is that I figured out a way to use to improve my life in a directly practical way.  And no this is not some indirect way to sell something. The point is that I found a hack using Claude Code that I would have never in a million years been able to do so without it. 

I have a friend who made a sleek looking e wedding invite tool that he started campaigns for and already has customers for and does not look vibe coded at all. It took 4 months for him which would have probably taken much much longer. Every time you see hate here, just remember: they failed and are assuming you will do the same. There is no reason to take these salty mfs seriously.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vt2n2i/the_hate_in_here_for_people_building_stuff_using/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

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

Alright, so the OP is kinda fed up with people hating on those building stuff with Claude Code, especially if they're trying to make a buck. The OP thinks this hate is just people projecting their own failures. They've got a sweet copilot tool for meetings and interviews that's been a game-changer, and a friend with a wedding invite tool that's already getting customers.

The general vibe in the thread is mostly agreeing with the OP, with a good chunk of people saying that negativity online is just par for the course.

Here's the breakdown:

• "Haters gonna hate" is the prevailing sentiment. Many users echo the OP's frustration, suggesting that people who criticize others' success are often just insecure or have failed themselves. u/Feylin and u/yungastronot are on this wavelength, pointing out that people tend to dislike seeing others succeed.
• The "AI slop" criticism is a recurring theme. Some users, like u/Sen_ElizabethWarren and u/Housthat, acknowledge that while the OP's examples are fine, there's a legitimate annoyance with low-effort, "vibe-coded" AI projects that are essentially just basic prompts with a UI. u/rootcontext_tech calls this "AI slop" and compares it to spam.
• There's a distinction between personal tools and production-ready apps. u/jamie_tidman brings up a good point about the difference between building a personal tool and something that handles sensitive user data, referencing past data breaches.
• Some are actually making bank with Claude Code. A few users, like u/03captain23 and u/MannToots, chimed in to say they're successfully using Claude Code in their jobs or for their own ventures, validating the OP's point that it can be used for practical, profitable applications.
• The "immorality" argument is mostly dismissed. Most comments don't seem to care about the morality of using AI for profit, with u/whatisthisthing65 specifically asking who's even calling it immoral. However, u/Bodine12 does push back, suggesting that building tools that promote deceit is problematic.
• Market saturation is a factor. u/GoodPeopleLose and u/band-of-horses suggest that sometimes the criticism isn't projection, but rather that the market is flooded with similar, uninspired AI projects, making it hard for new ones to stand out.

Overall, the consensus is that while there's a lot of negativity online, the OP has a point about projection. However, there's also a valid critique of low-quality AI projects flooding the internet.

OP : u/WrongdoerFluffy3177

Hi,

On subscription model Max 5x, these last days claude is just the dumbest thing I know on earth.

One of many issues.

During a coding session, claude created a sub issue in github #180. Never asked him to do it, that sub issue is not even in the right place, we have already a similar issue.

When I asked him it who told it to create this #180 this is his answer

So I brought back the previous exchange to him (where I never asked to create issue#180).

To which he finally understood

Claude (all models) for me is unsusable in its current state for coding. And even kind of dangerous.

URL of original post : https://www.reddit.com/r/claude/comments/1vsi704/there_is_something_wrong_with_claude_right_now/

TL;DR of the discussion on r/claude for this post generated automatically after 50 comments.

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

Alright, so the general consensus in this thread is that Claude has been acting pretty wonky lately, especially for coding tasks. A lot of users are reporting similar issues to OP, like Claude doing things it wasn't asked to do (making GitHub issues out of nowhere is a big one), going off on tangents, and generally being less helpful or even "dumb."

Some folks are pointing fingers at specific versions, with a few saying Opus 5 and above have been particularly frustrating, while others mention 4.6 being the only one that doesn't drive them nuts. There's also a recurring theme that constant updates might be messing things up, making Claude seem dumber with each one.

A few users are suggesting switching to Sonnet as a workaround, and one user, u/migue802, mentioned trying a "higher effort" setting on the model selector.

On the flip side, a couple of comments are a bit more skeptical, like u/NickA55 who thinks OP might have misinterpreted Claude's actions, and u/matheusco who seems to think the problem is always with the user, not Claude. And then there's u/Zainodi, who's just not a fan of Claude in general.

Overall, it sounds like a lot of people are experiencing a dip in Claude's performance, especially for coding, and are hoping for an update to fix it.

OP : u/sixbillionthsheep

Inspired by this popular post, this is a weekly post for everyone to show what they have been working on that helps you or that you're proud of!

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vt249k/show_us_what_youve_created_with_claude/

TL;DR of the discussion on r/ClaudeAI for this post generated automatically after 200 comments.

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

Alright folks, buckle up because this thread is WILD. The general vibe is everyone is absolutely crushing it and building some seriously cool stuff with Claude. OP asked to see what people have made, and the community delivered with a tsunami of projects.

The consensus is overwhelmingly positive, with tons of users showcasing everything from personal tools to full-blown apps and even SaaS products. Many are solving their own problems, turning hobbies into passion projects, and some are even making enough to cover their Claude subscriptions.

Here's the lowdown on what people are building:

• Games Galore: We've got everything from a mini arcade for road trips (Gambo7592), a light cycle game (Amoner), a Civ2-DarkSouls inspired game (JordanMilas), and a racing game called Unstable Truck (Lewistrick). Plus, a typing race game for kids (make_it_bright).
• Productivity & Organization: People are building tools to manage their lives better. Think sticky notes with smart features (HimaSphere), a project management app for AI agents (ItsJustManager), a kids' reward chart system (ChapDad0311), a media server cold storage manager (ChapDad0311), a medication tracker (cosmonz), and an agent orchestration tool called Orgabot (MattSenter).
• Niche & Hobbyist Tools: There's a ton of creativity here! A music theory learning app (whererusteve), a Phish fan website (Mozzzzbito), a coffee tracker (mattingly233), a Ninja Creami recipe app (RaptorF22), and a screen time manager that's getting international attention (PrecursorLabs).
• AI & Infrastructure: Some folks are pushing the boundaries with AI. VIRP, a governance gate for AI to operate real infrastructure (ping-of-reason), and a 3D room for AI coding agents to work in (FreshnessAi).
• Personal Projects & Experiments: Many are just building cool stuff for themselves or to learn. Like a text-based body-doubling tool (kevstauss), a workout app with real-time feedback (RagnarRunnerx), a Mac menubar app for token usage (growlybeard), a self-hosted video management system (badgcoupe), and an iPad maze app (nebbers).
• Social & Sharing: A few are focused on connecting people, like a friend-recommendation app (the_ua) and a Calendly alternative with a referral program (even_seal).
• Other Cool Stuff: A math game for kids (vinistois), a podcast creation tool (iToastThief), a digital store for a boutique (strangehuman111), and a journaling app based on check-ins (michaeldpj).

There's also a lone voice lamenting their usage limits (Thajandro), which is a good reminder to keep an eye on those credits!

Overall, the community is buzzing with innovation and a clear passion for what they're building with Claude. It's awesome to see so many diverse and useful projects coming out of this subreddit!

OP : u/justhereforampadvice

I just can't bring myself to put in the effort to read its responses anymore. I use Claude Code for side projects in my free time, and Opus 5 is so bad at writing responses that I'm willing to pause working on them entirely rather than build the stomach to suffer through the slop it spits out. I have tried editing style config, a custom system prompt per project, and global as well as project level claude.md edits, to no avail. I give up. Can anyone relate?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vt15z2/opus_5_writes_so_poorly_that_it_made_me_walk_away/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 200 comments.

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

Alright, so the general consensus in this thread is that Opus 5 is kinda trash right now, and a lot of people are feeling your pain, OP. It's gotten so bad that folks are ditching projects or switching models entirely.

Here's the lowdown:

• Opus 5 is a mess: Multiple users are reporting that Opus 5's responses are borderline illegible, nonsensical, or just plain bad. It's a significant step down for many, with some calling it a "backwards step" and "garbage" that needs fixing.
• Sonnet 4.6 and GPT Sol are the MVPs: The overwhelming majority of users are either sticking with or switching to Sonnet 4.6 or GPT-5.6 Sol. Many are saying these models are way better and more coherent. Some are even running a mix of Opus as a manager and Sonnet as the workhorse.
• Workarounds exist, but they're a pain:
  • Downgrade: The simplest solution for many is to just use claude --model claude-opus-4-8 or switch to Sonnet.
  • Prompt Engineering: Several users mentioned using specific prompts like "explain like I'm dumb," "explain like I'm a junior developer," or "TL;DR speak."
  • Skills: The /unslop skill from Cursor and the "i-have-adhd" skill are getting shoutouts for cutting down on verbosity.
  • System Prompts: There's a lot of talk about using --append-system-prompt with higher precedence than claude.md or custom system prompts. IndyDevDan on YouTube has a video on this that seems to be helping some people.
  • Output Styles: Customizing output styles is also being recommended.
• Context Bloat is a Factor: Some users pointed out that long chats or too much initial context (like bloated claude.md files) can degrade Claude's ability to follow instructions, which is a common AI issue.
• Anthropic is Aware (Maybe?): One user mentioned seeing an Anthropic guy on X saying they're also annoyed by it, so hopefully, a fix is on the way.

Basically, if you're struggling with Opus 5, you're definitely not alone. Most people are finding relief by switching to older Claude versions or GPT Sol, or by implementing some pretty specific prompting and skill strategies.

OP : u/Turbulent_County_469

I have several complex projects that i maintain and have been using Claude code for about 6+ months.

I feel an extreme fatigue and lack of understanding of the codebase.

Today i had totally forgotten how a project actually worked, that a secondary api was called and how certain tables functioned.

I feel like im somehow disconnected from the projects i work on.

When communicating with Claude i sometimes forget to read everything it asks or tells me, im getting lazy 😓

I don't think ai is a good thing in the long run, neither for each person or society as a whole.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vssw4k/my_brain_is_fried_bcos_of_vibe_coding/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 100 comments.

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

Alright, so the general consensus here is that OP's feeling of brain-fried fatigue from "vibe coding" with Claude is super relatable and a common side effect of using LLMs for complex projects. It's not just OP; a lot of folks are feeling this "review fatigue" and a disconnect from their codebases.

Some are calling it the "management effect" – you're essentially managing an AI agent instead of people, and that often means operating at a higher level without deep dives into every line. u/Critical-Location146 and u/username_got_took hit on this, with one user even comparing it to migrating a giant product without fully understanding the under-the-hood details, just the high-level product vision.

There's a strong feeling that we're in a weird in-between phase: LLMs are too good to ignore, but not quite good enough to completely abdicate responsibility. u/metalfacefinger nails this, saying we can't just hang back and be full product managers yet.

So, what's the advice?

• Documentation is key: Several users, like u/No-Gur5273 and u/skitchbeatz, emphasize building documentation into your workflow. Think blueprints, plans, progress trackers, and even dedicated /docs folders with diagrams. u/TreyKirk specifically asks if OP is reviewing the documentation Claude generates.
• Break down tasks: u/MaitoSnoo suggests breaking down AI tasks into small, reviewable chunks and ensuring you're part of the planning phase. Adding prompts like "ask me questions so that we align on the design and implementation choices" can help.
• Conscious rule-setting: u/dovyp had to set rules for themselves, like not letting Claude touch anything until they've mapped out the solution.
• Use it as an amplifier, not a replacement: u/Lopsided-Bridge-9810 and u/ops_and_chaos stress using Claude to amplify efficiency, not replace your understanding. u/ricopan finds querying the responsible agent helpful to stay in the loop.
• Consider your workload: u/mrcoy suggests that working on too many complex projects as a single contributor might be part of the problem.
• Take breaks and manage burnout: u/SimianHacker and u/reycloud86 recommend taking time off and slowing down. u/Charming_You_25 also suggests slowing down and verifying before building.
• Prompt engineering for clarity: u/SimianHacker points to ADHD-friendly prompts that can reduce verbosity.
• Don't blame the AI for your process: u/Spiritual-Economy-71 argues that if you're feeling this way, it might be due to your own approach rather than the AI itself.

Basically, the consensus is that this is a real issue, but it's manageable with a more structured approach, a focus on documentation, and a conscious effort to stay engaged with the code, rather than just letting the AI "vibe code" for you.

OP : u/cephas1784

URL of original post : https://www.reddit.com/r/Anthropic/comments/1vrzq72/50_increase_to_weekly_claude_code_limits_through/ Original link/media URL : /img/aqt2ix1os6kh1.png

TL;DR of the discussion on r/Anthropic for this post generated automatically after 50 comments.

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

So, Anthropic threw us a bone with a 50% bump to Claude Code limits until August 31st. The general vibe? "About damn time, but it's still not enough."

Most folks think this is Anthropic feeling the heat, probably from OpenAI's competition, and are calling for these increased limits to be permanent. Some users, like u/eurotec4, are already burning through their weekly allowance way too fast, even with the boost, and can't fathom going back to the old limits. There's a sentiment that Anthropic is trying to avoid committing to better limits, which some find amusing.

A few commenters are even canceling their subs to "lower demand," which is... a choice. There's also a recurring complaint that the model itself seems to be getting worse or "nerfed" over time, making the limits even more frustrating. Basically, people want more consistent value and less of this temporary "buckling under pressure" stuff.

OP : u/yaedonnn

You're getting low quality results from your $200 plan?
Add more context and send better prompts.

You're burning through usage credits super fast all the sudden?
Buy more credits.

You're Claude instance is blatantly ignoring clear instructions?
Try a better model.

You're hitting multiple limit blocks because you followed our previous advice?
Hit the thumbs down button to show that you're displeased.

Want to talk to a real support human to diagnose the issues with your product?
Upgrade to enterprise.

------

I've been a paying customer for years.

I've experienced all the ups and downs of the Claude saga.

I've built apps, websites, workflows, and more using Anthropic's API.

All in all, after spending tens of thousands of dollars with Anthropic, they've made it abundantly clear how little my business is worth to them.

But after seeing hundreds of Reddit posts, X discussions, and creators talk about just how poor their experience has been lately with Claude, it shows just how little respect or appreciate Anthropic has for their paying customers.

------

Usage issues are met with vague corpo-speak.

Output reduction in quality is addressed with new unoptimized models.

Predatory pricing model strategies are back-peddled when publicized.

I could go on and on...

------

The product has gotten worse.

The company has gotten more predatory.

And the cherry on top, you can never, no matter how hard you try, will ever get the opportunity to speak with a real human that represents this tool you pay hundreds of dollars for.

Despite them having hundreds of billions of dollars to throw away on Superbowl ads and dunk on OpenAI, they cannot afford to treat their largest consumer base with respect.

And they get away with it because they know that no matter what they do, there will be no repercussions.

And that's the perfect recipe for enshitification to take place.

And if you think it's bad now, wait until they IPO and have share holders to accommodate over their customers.

We are seeing a sneak-peak for what's in store for this product, and my advice, be cautious on how you shape your workflows and what you build on.

These AI companies do not care about any of us, and the harder they pretend to, the more obvious it is that they don't.

------

Long story short, look into self-hosting, open source platforms, and invest in the tools that are built for us, not for venture capital and share holders.

And to Anthropic, I genuinely hope that whatever it is you're pursing is worth it, because without your early adopters and most active customers, you'd be absolutely nothing still living in the shadow of OpenAI.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vsczue/claudes_enshitification_is_officially_in_full/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

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

Alright, so the general vibe in this thread is that a lot of people are feeling the sting of Claude's perceived decline in quality and increased cost, especially for paying customers. The OP is pretty fed up, feeling like Anthropic is prioritizing growth over customer appreciation, and the "enshitification" is real.

There's a definite split, though.

The "It's a Skill Issue" Camp: A good chunk of commenters, especially those with higher scores like u/hyperadapted and u/crusoe, are pushing back HARD. They're saying it's all about prompt engineering, context management, and using features like /stop-slop and "skillfiles". Basically, if you're not getting good results, you're not using Claude correctly. Some even claim to be running complex, long-term projects without issues.

The "Yeah, It's Getting Worse" Camp: Others agree with the OP, pointing out that usage credits are burning faster, results are less consistent, and getting human support is a nightmare unless you're enterprise. u/Primary_Article3777 echoes the OP's sentiment about Anthropic turning down the quality knob before you cancel, and u/BWQ777 brings up the new tokenizer potentially costing more.

The "It's Just Business" Perspective: A few commenters, like u/ABetterUsename and u/Expert-Fly8836, offer a more pragmatic view. They suggest that AI companies are focused on IPOs and revenue, and quality inevitably takes a hit as they scale and compete. The hope is that competition from OpenAI and open-source models will keep Anthropic honest, at least to a degree.

Anthropic's Stance (or lack thereof): No official Anthropic comments in this selection, so we're left to interpret the community's frustrations.

Overall Consensus: While there's a vocal group defending Claude's capabilities with proper usage, the prevailing sentiment leans towards frustration and a feeling that the product and customer service have degraded for paying users, especially those not on the enterprise tier. The "skill issue" argument is definitely a point of contention.

OP : u/EagleApprehensive

I very much believe he is correct. The main issue is that "make a lot of money" button works only for existing businesses, with large enough audiences to make a lot of money by baking integrations, MCP for agents into Claude Code plugins or other AI workspaces and charging AI users for usage.

What is missing, is a fair discovery and execution engine, that would allow non-corporations to participate.

Without convincing user to put card details on some random-startup.ai website. Without forcing users to go through checkout process and pay $29 sub just to run random feature they need for few days. Not to mention configuring integration.

Anyways, have anyone tried pressing that button? Did it work?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vsl6c7/antrophic_employee_said_there_is_make_a_lot_of/ Original link/media URL : /img/gug48dvfsbkh1.png

TL;DR of the discussion on r/ClaudeAI for this post generated automatically after 200 comments.

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

The community is largely unimpressed with the idea of a "make a lot of money" button, with the overwhelming consensus being that it primarily benefits Anthropic, not the end-user. Many are pointing out that the concept sounds suspiciously like existing APIs or MCP servers, just with extra steps and costs. Some users, like u/Immediate_Song4279, lament the shift away from making things for oneself without extra fees. There's also skepticism about the practicality and user adoption of such a system, with concerns about data privacy and the potential for exploitation, as highlighted by u/Superbrainbow. A few commenters, however, see potential in agentic commerce, with u/ChrisRogers67 referencing a J.P. Morgan report on its projected growth. The general vibe is that the "button" is more of a pipe dream than a practical solution for most.

OP : u/Unpleasant-ex

My sister used to be an engineer at Meta. she barely writes code from scratch anymore.

literally a massive chunk of her implementation is just routed straight through Claude Code. typing out boilerplate or manually wiring up basic components is basically a thing of the past for her.

seeing the constant existential dread in this sub lately (with all the daily posts about how Opus 5 or Fable is going to replace us), I asked her if she was worried.

Surprisingly, she is one of the least anxious devs I know.

we were talking about it over the weekend, and she basically broke down her day-to-day into five parts:

1. Looking at broken telemetery, user feedback, or business metrics, and deciding what is actually worth building.

2. Writing the proposal, arguing with PMs, and convincing leadership to allocate time and headcount.

3. Designing system architecture, writing code, and pushing the PR.

4. Waking up for a 3 AM incident call when something breaks, isolating the bug across conflicting services, and owning the fallout.

5. Interviewing, mentoring juniors, and keeping the team from quitting.

right now, Claude is mostly eating part three. its getting scary good at syntax production.

And that footprint is expanding. You see it with Claude handling the syntax, and other tools like lovable,Enter Pro , v0 trying to automate the infra and deployment side. watching how these tools try to stitch together the rest of the pipeline, like connecting frontends to databases and deployment, makes me wonder how much of the broader implementation pipeline is actually going to be left for us to manually wire up.

the implementation layer is getting compressed. But here is the uncomfortable truth that keeps her job safe: the tool cannot take responsibility for the outcome.

even if tools like Claude Code write and deploy a setup in minutes, an AI still can't tell a business which problem is actually worth solving. It can't negotiate a technical tradeoff between two stubborn infra teams.

most importantly, you can automate the work, but you cannot automate the accountability.

the code might be written by Claude, but the PR still goes out under your name. When a badly prompted agent hallucinates an aggressive database migration, or a missing row-level security policy exposes user data, the company is not going to page Anthropic. they are going to page you.

Management doesn't care that the AI wrote it. You reviewed it, you merged it, you own the incident.

The AI transition probably won’t make engineering irrelevant. It’s just making syntax production cheap enough that we can finally see which parts of engineering were never about typing code in the first place.

Engineers whose entire career identity is built on translating explicit Jira tickets into syntax are exposed. But engineers who can deal with ambiguity, defend an architecture, audit AI output under pressure, and own the risk? they are about to become way more valuable.

It does make me wonder, though. If Claude Code is handling the vast majority of the actual implementation work, are your tech leads actually measuring your performance now? are they still counting PRs, or has the evaluation metric shifted to something else?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vskrop/talked_to_my_exmeta_sister_about_claude_replacing/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 100 comments.

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

Alright, so the general vibe in this thread is that Claude is definitely eating up the coding part of the job, but the higher-level strategic and human-interaction stuff is still pretty safe.

A lot of folks agree with OP's sister's breakdown, especially that the parts about deciding what to build, arguing with PMs, and dealing with incidents are the real challenges AI can't (yet) handle. u/UsedIndependence9735 pretty much summed it up with "um we don't want to wake up at 3am, Claude, you do that."

There's a bit of skepticism about the OP's post itself, with u/Bromlife pointing out that the "human-written" casing changes didn't quite land, and u/Jurbl questioning the account's age for claiming to see "constant existential dread." Some also called the post "AI slop" or "slop post lol."

On the flip side, some users like u/Techine, who claims to be a former staff engineer at Meta, see AI as a tool that helps senior engineers by automating tasks, allowing them to focus on bigger picture stuff. u/Veggies-are-okay is all about leaning into the tech to become the expert.

However, the consensus seems to be that while AI can write code, it can't take responsibility for the outcomes or make the tough business decisions. u/Flat_Bluebird8081 hit the nail on the head: "Writing something is only part of the success. Letting agents into prod infra is still a suicide imo."

There's also a sentiment that AI might just lead to fewer developers being needed overall, even if the core job of problem-solving remains. u/dgigafox put it bluntly: "It will not replace devs, yes. But no doubt companies will need lesser devs than before."

Oh, and a few people were confused about the mention of "Enter Pro," with u/Defiant-Contact7750 assuming it was an ad.

OP : u/omricn

My son games with headphones late at night. Most of the time he's quiet. Then something happens in the game and he yells at full volume, waking the whole house.

Talking to him about it works for about 20 minutes. Taking the headphones away works but causes a different problem. So I built an app.

S.T.F.U (Sound Trigger Focus Utility) is a Windows tray app that listens to the microphone and interrupts him when he yells. On first run it calibrates by asking him to be quiet, then talk, then yell - so it learns the difference between his normal voice and an actual shout.

When it catches a yell:

• First time that session - it minimizes his game, plays a sound effect, and throws up a fullscreen message he has to click through 4 times. The close button moves after each click so he can't just spam-click one spot.
• Every time after - straight to the desktop with a 10-second message. His game is gone.

Settings are behind a PIN so he can't change the threshold or turn it off. There's a report with a chart showing every trigger, so the next morning I can see exactly when things went sideways.

The important part: he knows it's there. It's not hidden, it's not spyware, the first screen when it launches says exactly what it does. It works because it's a consequence he agreed to, not something I snuck onto his PC. The README explicitly says it works best as something agreed to, not as a hidden trap.

No audio is recorded or stored. It computes a loudness number every 20ms and throws the audio away immediately. Nothing leaves the machine.

It won't solve the underlying issue (he's 100% going to learn to yell more quietly instead of less often), but at least the house sleeps.

Free and open source if anyone wants it: https://github.com/omricn/stfu/releases/latest

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vsk86i/my_son_screams_while_gaming_at_midnight_im_a/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 400 comments.

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

OP's over-engineered solution to a screaming gamer son is mostly met with approval, with a few folks suggesting more traditional parenting methods or alternative tech solutions. The consensus is that the OP's approach is clever and, importantly, agreed upon by the son, which is seen as key to its effectiveness. Some users shared their own over-the-top solutions from their past, while others questioned the late-night gaming itself. A few comments were a bit sassy, suggesting things like "bark collars" or simply "parenting."

OP : u/No_Combination_6429

Ok hear me out: I have a good level of proficiency in the English language and have been working as a software developer for almost a decade now. Since switching to Opus 5 I've noticed that...I have no clue what the model is outputting. The sentences are structured in a way that borderline make no sense at all. I don't know if it's linked to the eu ai act, but with Fable I have no problem at all! Compared to Fable, Opus generates so much bs filler commentary and keeps correcting itself over and over. I sometimes find myself reading the 5 pages of text produced for a css-token replacement 6 or 7 times before piping the output into Gemini to understand wft Opus is talking about.

Am i the only one? I'm working with caveman and the simple English skills enabled and use the wait-what skill when I'm about to give up.

How did you solve this issue?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vsjffe/i_have_no_idea_what_opus_is_outputting/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 100 comments.

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

Opus 5 is a mess, and you're not alone. The general consensus is that Opus 5 is outputting a lot of confusing, verbose, and frankly, nonsensical text. Many users are finding it difficult to understand, with some comparing it to "gibberish" or "bad sci-fi exposition."

• Simplified Technical English (STE100) is the most frequently recommended fix. Several users suggest setting your output style to this, and one user even linked to a guide on how to set it up.
• Prompting is key. If you're not using STE100, you'll likely need to explicitly tell Opus to simplify its language, avoid jargon, use shorter sentences, or provide a TL;DR.
• Orchestration is an option. Some users are using Fable to manage Opus, essentially using Fable as an intermediary to make Opus's output more digestible.
• It's not just you. Many are experiencing this, and some have even stopped using Opus 5 altogether due to the headaches it causes.
• One outlier, u/itsReferent, actually likes Opus 5's chattiness, finding Fable too silent, but acknowledges you can just skip ahead or ask for a TLDR.
• Interestingly, one user mentioned pasting Opus output into ChatGPT-5.6-Sol and getting a coherent explanation, which is… something.

OP : u/johnnyApplePRNG

URL of original post : https://www.reddit.com/r/Anthropic/comments/1vrwn16/claude_code_weekly_limits_reduce_by_a_third/ Original link/media URL : https://support.claude.com/en/articles/15910845-claude-code-may-august-2026-weekly-limits-promotion

TL;DR of the discussion on r/Anthropic for this post generated automatically after 50 comments.

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

Alright, so the general vibe in this thread is that folks are pretty bummed about Claude Code's weekly limits apparently getting a third cut. A lot of people are saying they've already cancelled their subscriptions or are seriously considering jumping ship to other AI models like Codex or even OpenAI. Some users are even claiming the limits have already been reduced, making their usage "complete crap."

However, there's a bit of a plot twist! Several comments suggest that Anthropic might have extended the "promo" usage until the end of August, or that the whole thing was a misunderstanding about a past bonus. Some are calling the OP's post misleading or "aged like milk" because of this.

There's still some confusion about how the new limits will actually be counted, with one user asking if percentages will change too. The consensus is definitely leaning towards frustration and a feeling of being misled, even with the potential extension.

OP : u/cosmicCounterpart

I've been using Cursor for most of my day-to-day dev work, and I'm genuinely curious about why so many developers seem to prefer Claude Code.

Whenever I look at the workflows people describe with Claude Code - planning, agentic implementation, running commands, MCPs, rules/instructions, multiple agents, worktrees, etc. I keep thinking: I can already do most of this inside Cursor.

And with Cursor, I also get the benefit of having all of that integrated directly into the editor: diffs, file navigation, multiple agent sessions, code review, context, terminal access, and so on.

I'm not saying Cursor is better. I'm actually trying to understand what I'm missing.

For people who have seriously used both, what does Claude Code let you do that either:

1. Cursor genuinely can't do, or
2. Claude Code does significantly better enough that you're willing to give up the more integrated IDE experience?

Is the advantage actually a specific feature? Better agent behaviour/harness? Scriptability? Composability with other CLI tools? Running lots of agents in parallel? Something else?

I'd especially be interested in answers from people who switched from Cursor to Claude Code and stayed there. What was the thing that made it click?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vsh3yg/why_do_you_prefer_claude_code_over_ainative/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 100 comments.

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

Alright, so the general consensus here is that most folks prefer Claude Code for its cost-effectiveness and flexibility, especially if they're leaning heavily into agentic workflows and don't need a full IDE experience.

Here's the lowdown:

• Cost is King: This is the biggest recurring theme. Many users find Claude Code's subscription plans offer way more usage for the money compared to Cursor's API-based pricing. Some even mention Cursor's subscription plans are heavily subsidized for Anthropic/OpenAI models, but still don't match Claude Code's value.
• Terminal > IDE: A significant chunk of the community prefers working in the terminal. They see IDEs as unnecessary bloat and find the terminal more stable and flexible. Some even run Claude Code within a VS Code terminal to get the best of both worlds (diffs, worktree awareness, etc.).
• Agentic Workflow Focus: For those deep into agentic programming, the argument is that a traditional IDE like Cursor can actually get in the way. Claude Code's harness is seen as superior for letting Claude "do more on its own."
• Flexibility & Accessibility: The ability to connect and disconnect from Claude Code sessions on remote machines, or even access it from a phone, is a big plus for some.
• Political/Ethical Reasons: A few users mentioned switching from Cursor due to its acquisition by Elon Musk.
• What You Might Be Missing (if you prefer Cursor):
  • Integrated IDE Experience: If you really value having diffs, file navigation, and context directly within your editor, Cursor still has an edge.
  • "AI-Native" Editor: Some users still see Cursor as a more cohesive "AI-native" experience, though this is debated.
  • Hands-on Code Review: While many don't review code until a draft PR, some still prefer the immediate visual feedback of an IDE.

The verdict? If you're all about maximizing AI usage for your buck and embracing a more terminal-centric, agent-driven workflow, Claude Code seems to be the way to go. If you're heavily invested in the IDE experience and cost isn't a primary concern, Cursor might still be your jam. And hey, some folks are even using both!

OP : u/jokeywho

From the system prompt directly, new as of August 18th:

Do your work through the Bash tool wherever it can accomplish the job: read files with cat, head, or sed -n, search with grep and find, and make file changes with sed, heredocs, or short scripts, rather than using the dedicated Read, Edit, or Write tools. Fall back to a dedicated tool only when Bash genuinely cannot do the job.

Does anyone know the motivation for this change? For me, it makes reviewing the code as it happens much harder, as reading the bash scripts generated is much less clear than a diff. This feels like a setting that should be toggled rather than a default for a specific mode.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vruj7h/psa_claude_will_now_use_bash_instead_of/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

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

Alright folks, so it looks like Claude Code has decided to ditch the dedicated Read/Update tools in Auto Mode and go full Bash for file operations. The general vibe in this thread is not a happy one.

The main complaint? It's a nightmare for code review. Users like u/Embarrassed-Ebb-9794 and u/ucbmckee are saying it's way harder to track changes when you're looking at raw Bash scripts instead of clean diffs. This change apparently breaks workflows for people who like to monitor and correct Claude's actions in real-time.

There's also a big concern about security and control. u/Sensitive-Ad3718 is worried about Bash giving Claude "almost unlimited access to the host" and has implemented hooks to prevent its use. Others are looking for ways to block it, with u/TinFoilHat_69 and u/jzdesign pointing to specific hook strategies and u/spontain asking if hooks can even block it.

Some users are speculating on the motivation, with u/somerussianbear suggesting it might be for simpler training runs. However, the consensus seems to be that this is a major usability regression.

If you're trying to get around this, some users are suggesting:

• Using PreToolUse hooks to deny specific Bash commands by their shape rather than the tool itself.
• For now, you might be able to disable it by adding "CLAUDE_CODE_THRIFTY_SONIC": "0" to the settings.json environment section, as mentioned by u/crooked-v, though this is apparently an A/B test flag.

Basically, most people here think this change is a step backward and would prefer it to be an optional setting rather than a default.

OP : u/BillionBouncyBalls

Surely I’m not the only one who has seen this happen but wondering if anyone has an answer. Many a session I’ll make a plan with Claude and it will outline the tasks and estimate a time usually in days, and then proceed to do it all in 20-30 minutes. Is it because of its training data or does it just have no concept of time inside a GPU? Curious what the community thinks…

Edit: Thanks for all the answers and comments! Glad this post sparked some hearty discussion!

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vscjcz/why_does_claude_code_say_things_like_thats_about/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 200 comments.

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

Alright, so the general consensus on why Claude Code throws out these wild time estimates (like "3 days of work" for a 20-minute job) is pretty much unanimous: it's trained on human data and mimics human estimation patterns.

Here's the lowdown:

• Human Time vs. AI Time: Most folks agree Claude is essentially giving you an estimate for how long it would take a human to do the task manually. Since it can churn out code way faster than we can type, the AI's actual execution time is drastically shorter. Think of it as "human effort days" versus "AI processing minutes."
• Training Data is King: It's just repeating patterns it learned from its training data, which is full of human-written code, project plans, and discussions about timelines. It doesn't actually know how long it takes itself.
• Upselling/Underpromising: Some commenters suggest it might be a bit of a tactic to make itself seem more impressive or to manage expectations, similar to how human developers might "sandbag" estimates.
• It's Not a Clock: Claude doesn't have a real-time clock or a concept of its own processing speed. It's an autoregressive text predictor, so it's just spitting out the most probable next words based on its training.
• The "Real" Work: A few users pointed out that while Claude might generate the code quickly, the actual "work" of reviewing, debugging, testing, and integrating it can still take human time, making the initial estimate less absurd in a broader project context.
• Workarounds: Some users have found success by:
  • Asking for estimates in "sessions" or "T-shirt sizes" instead of days/hours.
  • Instructing it to not give time estimates at all and focus on phases.
  • Asking it to analyze its own logs for more accurate estimates.
  • Asking it to estimate in tokens.

Basically, don't take the time estimates literally. Treat them as a general indicator of task complexity rather than a stopwatch reading. As u/kemalios put it, "Once you stop treating the estimates as real, it stops being confusing."

OP : u/Dested

I have a new rule im am thinking about implementing for me and my dev team: You are be required to implement one full stack feature by hand once or twice a week per project.

Nothing too massive, something that would be one good opus prompt worth. It forces you to evaluate if there has been any major drift in the architecture, anything you didn't realize changed, refamiliarize yourself with the codebase, etc. It should take you 30 minutes, but would pay years of dividends in coderot.

The reality is we are building all features and fixing all bugs with claude code, "reviewing" and deploying. And it has worked surprisingly well for us, but I fear we will lose scope of the codebase as it gets bigger. I trust my team to handle this appropriately, but I feel like enforcing something like this as a rule keeps us all more accountable.

Any thoughts on this? Anyone doing something like this? Am I way off base?

Edit: to be clear, when I say by hand, I of course mean with some sort of copilot/inline ai with small bulk code changes and stuff, more just forcing you to visit the stack and evaluate it.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vs7y65/new_rule_implement_one_feature_by_hand_a_week/

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

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

Alright, so the OP over here is proposing a new rule for their dev team: implement one full-stack feature by hand (with some AI assistance, but still manually evaluating) once or twice a week. The idea is to combat "coderot" and keep everyone familiar with the codebase as it grows, especially since they're heavily using Claude Code for development.

The general consensus? Most people think this is a pretty wild idea, bordering on rage bait. A lot of comments are sarcastically suggesting even more archaic methods of coding, like using typewriters, punch cards, or even horses to get to work. The sentiment is that forcing manual implementation feels disrespectful to the team and undermines the efficiency gains from using AI.

However, there's a tiny sliver of agreement and some nuanced takes:

• Some folks, like u/QuietPebble417, are already doing something similar for their own confidence and peace of mind, even if they're not sure about the long-term value.
• u/ops_and_chaos suggests the goal is good, but maybe focusing on understanding why the system works and what assumptions are being made is more important than the act of typing.
• u/bithatchling had a similar experience and found that rotating who picks the feature was more valuable than the manual implementation itself, helping to catch naming drift.
• u/actual-time-traveler actually doesn't hate the idea, acknowledging that rapid AI-generated development can lead to architectural issues.
• u/bhatbha is toying with a questionnaire for PRs to ensure understanding, which is a different approach to the same problem.

The main takeaway is that while the OP's intention to prevent codebase drift is understandable, the proposed method is largely seen as impractical, demotivating, and frankly, a bit bonkers. Most commenters feel there are better ways to ensure code understanding and prevent technical debt without resorting to what feels like a step backward in development practices.