u/cctldrping

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 50 comments.

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

Alright folks, the community's been busy showing off their Claude creations, and it's pretty impressive stuff! The general vibe is super positive, with tons of cool projects shared.

The standout hit of the thread seems to be Glovebox.quest, a mini-arcade for road trips that people are digging.

A major theme popping up is the idea of building tools for AI agents to build more tools. It's like a meta-AI playground in here! We're seeing a lot of projects focused on agent orchestration, memory, and making agents more efficient.

Here's a quick rundown of some other cool things people whipped up:

• VIRP: A governance gate to let AI operate real infrastructure safely.
• CalendarPA: A Calendly alternative with a built-in referral program.
• Better Stickies: Smart sticky notes for your desktop.
• Orgabot: An agent orchestration tool aiming to replace your org chart.
• ChapterPals: A reading tracker and book club app.
• Pizzaπ: A math game for kids.
• CrumbVMS: A self-hosted video management system.
• United Mazes of America: An iPad app featuring hand-drawn mazes.
• SpinFreeze: For Ninja Creami owners.
• Percolate: A coffee tracker app.
• A Third Place: An app for sharing and planning locations with friends.
• PokerInk: A tool for live poker players to track hands.
• Sense Linter: Checks if your words match your intent.

Basically, the community is using Claude for everything from personal projects and fun games to serious dev tools and infrastructure management. Keep 'em coming!

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 50 comments.

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

So, OP's feeling like their brain is fried from "vibe coding" with Claude and they're losing touch with their projects. The general consensus? Yeah, that's a thing, and you're not alone.

• Several folks, like u/Additional-Race-2797 and u/Critical-Location146, are calling it "review fatigue" or feeling like a product manager who doesn't know the nitty-gritty. It's that weird in-between where AI is too useful to ignore but not quite good enough to fully hand off.
• Some are saying it's basically the same trap engineers fall into when they move into management – you know the high-level stuff, but not the line-by-line details.
• Suggestions for staying sane include:
  • Building robust documentation processes (u/TreyKirk, u/skitchbeatz).
  • Breaking down tasks into smaller, reviewable chunks and actively participating in planning (u/MaitoSnoo).
  • Using tools like LLM-wikis to keep a digestible record of your projects (u/Comfortable-Ad-6740).
  • Taking breaks and revisiting the fundamentals when you feel overwhelmed (u/reycloud86).
• There's also a bit of a philosophical debate: is this just the natural evolution of coding, or are we losing something vital? u/MetaShadowIntegrator paints a grim picture of a "ball of mud" future, while others, like u/Lopsided-Bridge-9810, advocate for using AI as an amplifier, not a replacement.
• And yes, some are joking about becoming "Masta in Copy Pasta" (u/ThePnisher) or co-authoring books with Claude (u/MeanCryptographer585).

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.

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

Original post body :

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.

---

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.

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/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 50 comments.

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

Alright, so it seems like the consensus is that Opus 5 is being a total word-salad machine, and you're definitely not alone in this struggle. A lot of folks are finding its output to be confusing, overly verbose, and frankly, gibberish. Some are even saying it's worse than jargon.

Here's the lowdown on what people are doing to try and fix it:

• Simplified English is your friend: Several users, including u/nospoon99 and u/ruskyandrei, are recommending setting the output style to 'use ASD-STE100 (simplified technical English)' or generally simplifying the language.
• Prompt Engineering FTW: Some are having success by explicitly telling Opus to be less wordy, use shorter sentences, or avoid complex words in their system prompt. u/Spare_Bison_1151 even suggested limiting sentence length to 8-10 words.
• Fable to the rescue: A popular workaround is to use Fable as an orchestrator or manager for Opus. This way, you can interact with Fable and have it delegate tasks to Opus, then review its work. u/jasze and u/Localinmyowncity are doing this.
• TL;DR is a must: If you don't want to wade through the verbosity, u/mkhaytman suggests following up with "tldr, eli20" (explain like I'm 20).
• Just skip it or restart: Some are just ending sessions when Opus gets too weird or starting new ones with clearer guidelines. u/lukaslalinsky does this.
• Rephrasing hooks: u/reviery_official has added a hook to rephrase output, removing filler and "engagement bait."
• Avoid Opus 5 altogether: A few users, like u/DimmKirr, are sticking with older versions like Opus 4.6 if they can.
• It's not just you, it's Claude: u/Relative-Desk4802 pretty much sums it up.

On the flip side, u/itsReferent is actually okay with Opus 5's chattiness, seeing it as "thinking out-loud" and just skipping the repetitive parts. And u/arankays is arguing that Opus 5's wording is technically correct, just obtuse, and uses professional SWE jargon.

But yeah, the general vibe is that Opus 5 is being a bit of a mess, and you'll likely need to implement some workarounds to get coherent output.

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.

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

Original post body :

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?

---

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.

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

Original post body :

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?

---

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.

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 50 comments.

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

Alright, so the general vibe in this thread is that while Cursor is a solid IDE with AI bolted on, most folks seem to prefer Claude Code for its terminal-centric, agentic workflow, and especially its cost-effectiveness.

Here's the breakdown:

• Cost is King: This is the biggest recurring theme. Many users point out that Claude Code subscriptions offer way more usage for the money compared to Cursor's API-based pricing. u/freddybelly and u/SetAdministrative502 explicitly mention this as their primary reason for switching or sticking with Claude Code. u/Mystical_Whoosing and u/FlatCondition6222 echo this sentiment.
• Terminal > IDE for AI Work: A significant chunk of the community argues that an IDE is unnecessary bloat when working with AI agents. u/Biomech8 and u/madaerodog are big fans of the terminal, finding it more stable and less prone to UI changes. u/ObjectiveSalt1635 and u/jasperkennis suggest that if you're not actively writing code, the IDE's benefits diminish. u/LoneFox4444 adds that the CLI offers more freedom than a constrained IDE.
• Superior Agent Harness/Behavior: Some users, like u/cartoonist498, believe Claude Code's underlying "harness" for agents is simply better, allowing Claude to operate more autonomously than it can within Cursor, even with Opus.
• Flexibility and Composability: The CLI approach with Claude Code allows for easier integration with other tools and workflows. u/Original-Ad4399 mentions tools like Superpowers, and u/ProcedureEthics2077 highlights how it handles complex, multi-language projects better. u/Markronom is even setting up a hands-free system with Claude Code.
• "Vibe" Coding: u/ABetterUsename humorously captures the feeling that Claude Code is more about the "vibe" of AI-driven development, while Cursor feels like a more traditional IDE with AI added.
• Not Everyone Agrees: It's not a total consensus. u/AsidK and u/spottie_ottie feel you're not missing anything and that Cursor is superior, especially now. u/Andreas_Moeller misses Cursor's integrated editor experience after switching due to XAI's acquisition. u/ALAS_POOR_YORICK_LOL thinks the difference is minimal.
• The "You Don't Need to Edit Code" Argument: A few comments imply that if you're still focused on manually editing code, you might not "get" the Claude Code workflow yet. u/finik21 and u/siberianmi mention not looking at diffs until they're ready for review.

TL;DR: People dig Claude Code for its killer cost-to-usage ratio and its terminal-first approach, which they see as more flexible and powerful for agentic workflows than an IDE like Cursor. While Cursor has its fans for its integrated experience, the community consensus leans towards Claude Code's efficiency and raw agent capabilities, especially when budget is a concern.

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/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.

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

Original post body :

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?

---

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.

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

Original post body :

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.

---

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.

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

Original post body :

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.

---

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.

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."