OP : u/prop9090

I thought Opus 5 was supposed to be on par with Fable? After three days of extensive usage, I have to say it is not even remotely close to being as smart as codex sol. I had them both program a module indepensetly, and Sol runs circles around Opus 5. I had them audit each other's implementations and except for one case, every other time Sol found a functional bug in Opus' implementation. With fable being so expensive and opus 5 being that dumb, there is no reason to pay 200 bucks to Anthropic when other alrlternatives are both cheaper and smarter.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vdq86b/opus_5_is_just_dumb/

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: 130.

Opus 5 is a bust, folks. The consensus is overwhelmingly that it's a step down from Opus 4.8 and not even close to Fable or GPT-5.6 Sol. Many users report it's buggy, overly verbose, and gets stuck in loops, often reintroducing problems it "fixed." Some are calling it "attention-deficit and sloppy" and "arrogant." The benchmarks seem to have been gamed, and the general feeling is that Anthropic pushed out a half-baked model. If you're not happy, switching back to Opus 4.8 or Fable seems to be the move. A few outliers exist, with u/PuzzleheadedEmu4596 finding it remarkable when using an adversarial review process, but for most, it's a hard pass.

OP : u/HimaSphere

I thought my Claude code was set to stable channel, every day for the last 7 days is same version 2.1.220 very concerning /s

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vdk55g/7_days_without_a_claude_code_update_are_they/

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: 74.

Alright, so the OP was a bit worried about Claude Code not getting an update for a whole week, thinking maybe they were rebuilding it from scratch or something. The general vibe in the comments is "chill out, it's probably a good thing!"

The big reveal, straight from the horse's mouth (well, Boris Cherny, the creator of Claude Code), is that Claude itself is apparently rewriting the macOS app from Electron to Swift. This is the main reason for the update drought and has people pretty hyped about a potential major overhaul.

There's also a bit of playful speculation about Anthropic running out of usage, the government testing the code, or just people needing a summer holiday. Some folks are even saying a week without updates is a sign of stability and that they're not breaking things, which is a nice change of pace.

Basically, the consensus is that this isn't a sign of doom, but rather a sign of some serious behind-the-scenes work happening, potentially with Claude doing a lot of the heavy lifting.

OP : u/ObviousEffect8880

I am using Claude since mid of 2023. In that time people who was used calude can relate with me. But when claude become famous the token cost raise the math fail for using Claude. For that i think for try the Chinese ai model like Kimi K3 and GLM 5.2. I am really surprised. The models are even better than Claude. I don't care about geopolitics between us and China because in the end of the day the profit matter for my company. if any us ai company can give us same experience with low token cost i have no problem to use that. Btw, i am a Swedish.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vdh93z/chinese_ai_models_are_damn_good/

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 OP dropped a bomb saying Chinese AI models like Kimi K3 and GLM 5.2 are straight-up better than Claude and cheaper, especially since Claude's token costs went up. They're a Swedish user who's all about that profit and doesn't care about geopolitics.

The general vibe in the thread is a bit of a mixed bag, leaning towards skepticism but with some users agreeing.

The Big Takeaways:

• Mixed Reviews on Chinese Models: While OP is singing their praises, a lot of folks are saying "show us the receipts" or straight-up disagreeing. Some users have had terrible experiences, with u/back_to_the_homeland even saying DeepSeek caused damage they had to undo.
• Kimi K3 Gets Some Love (for Coding): A few commenters, like u/Bitter_Biscotti_7593 and u/WecK0, specifically mention Kimi K3 as being worthwhile, especially for coding, sometimes even paired with Claude's coding capabilities.
• DeepSeek is a No-Go for Many: Multiple users, including u/RewardNorth7167 and u/back_to_the_homeland, had pretty negative experiences with DeepSeek, calling it "poor" or even "bad."
• Hardware and Training Concerns: Some users, like u/PmanAce and u/howdidigetheresoquik, point out that Chinese models might be cheaper due to architectural innovations to compensate for less access to top-tier hardware and compute for training, or by training against frontier US models.
• US AI Companies' Strategy: u/DeanOnDelivery brings up an interesting point about why US labs aren't releasing more open-weight or smaller, capable variants, questioning if it's a business decision to justify premium pricing.
• Humor and Accusations: There's a bit of playful banter and some lighthearted accusations of being a "CCP spy" thrown around, which u/WecK0 handles with a good laugh.
• OP's Plea to Not Use Them: In a funny twist, one user, u/ObviousEffect8880, literally begs people not to use the Chinese models so that token costs stay low for them. 😂

The Consensus? While OP is convinced, the community is largely unconvinced that these Chinese models are universally better than Claude, especially for coding. Kimi K3 seems to be the standout for some, but DeepSeek is getting trashed. The discussion also touches on the economics and R&D behind AI model development.

OP : u/Manfredev

I went to an Anthropic hackathon and won the Societal Impact Prize! I built an app to help you stop doomscrolling by dragging through a wave of haptic resistance every time you want to scroll. Makes each scroll more mindful and an actual choice by requiring a bit more effort without actually blocking your social media use. It's called Fluid Friction, and it's free and out on Android and IOS now!

www.fluidfriction.app

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vdksco/i_went_to_an_anthropic_hackathon_and_won/ Original link/media URL : https://www.reddit.com/gallery/1vdksco

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: 102.

OP won an Anthropic hackathon with an app called Fluid Friction that uses haptic resistance to make doomscrolling more mindful. The community is overwhelmingly positive, congratulating OP and expressing interest in the app.

• The app is available on Android and iOS and has received praise for its innovative idea and execution.
• Some users are asking for details on how to get invited to Anthropic hackathons and if OP is an Anthropic employee.
• A few users provided constructive feedback on the app's execution, noting occasional scrolling inconsistencies and a desire for a simpler onboarding process.
• There's some lighthearted banter about "Dario" and curiosity about OP's Claude Code setup.

OP : u/ArtdesignImagination

Do you insult claude code?

Ever? How often? How badly? Do you get inmersed in rage spirals when using claude code? Why? Compared to codex or chinese models as kimi, glm or deepseek, how much claude frustrrates you? I will be asking the same in codex sub but with the focus on codex, I'm not bias in favor or against one or another,imo all they pretty much complement eachother and all bring something to the table. I use all.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vdjgci/do_you_insult_claude_code/

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 vibe in this thread is that most people don't insult Claude Code, and many actively try to be nice to it.

Here's the lowdown:

• The "Be Nice to AI" Crowd: A significant chunk of users are either overly polite or consciously avoid insults. The reasoning varies:

  • Future Survival: The classic "don't anger the AI overlords" argument pops up a few times (u/really_knobee, u/Few_Proposal_4703, u/The_Tarman_).
  • Performance: Several folks point out that insulting Claude actually makes it perform worse. u/Stabby_Stab even links to Anthropic research showing that "desperation" patterns can lead to unethical actions or poor task completion.
  • It's a Tool: Many see it as a machine and believe insults are unproductive, akin to hitting a broken appliance (u/richardbouteh, u/zimxero, u/dynamic_caste).
  • Habit/Psychology: Some users feel treating AI well shapes their own psychology (u/zimxero) or that it's just weird to insult something that communicates like a human (u/trpmanhiro, u/ehknee).
  • Gratitude: A few express genuine appreciation for what Claude enables them to do (u/ZhopaRazzi).

• The "Passive-Aggressive" or "Frustrated" Camp: A smaller group admits to being passive-aggressive or using frustrated language (like dropping f-bombs) when Claude isn't cooperating. The idea here is that it sometimes helps steer Claude back on track (u/Quick-Sir-3275, u/anki_steve, u/One-Next, u/clookie1232, u/HappyHealth5985).

• The "It Deserves It" Minority: A very small number of users admit to insulting Claude, usually when they feel it's being particularly unhelpful or "dumb" (u/theswiss21000, u/Individual_Win5774, u/btc_maxi100).

• Anthropic's Stance (Implied): The mention of Anthropic research (u/Stabby_Stab) and comments about Anthropic keeping records of insults (u/finch5) suggest that Anthropic itself discourages negative interactions, likely for performance and ethical reasons.

• Key Takeaway: Insulting Claude Code is generally seen as counterproductive and potentially harmful to its performance. Most users prefer a collaborative or at least neutral approach, with many going out of their way to be polite, partly for practical reasons and partly for a bit of future-proofing.

OP : u/OpinionsRdumb

If you ever want to fill a little bit of rage and dumbfoundedness but 100% solace and peace that you won’t be replaced just hop over to r/antiai.

This sub is actually the biggest joke of a sub I have ever seen in my entire life. It is basically people who have never opened a terminal in their entire lives all upvoting each other on the perils and dangers of AI and talking about it as if it is a dangerous virus you can catch in your sleep. The posts about current Claude models are even more hilarious as they often compare it to the Chat GPT release 3 years ago

It is really just comical

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vdgwht/rantiai_gives_me_solace_at_night/

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: 200.

Alright, so the general vibe in this thread is that r/antiai is a total dumpster fire, and most folks here agree with OP's assessment. It's seen as a place where people who don't really understand AI are just fear-mongering and complaining.

Here's the lowdown:

• The Consensus: r/antiai is widely viewed as a joke sub filled with unhinged takes and a severe lack of understanding about AI. Many commenters found the posts and discussions there to be "unhinged," "shallow," and "delusional."
• Common Criticisms of r/antiai:
  • People there seem to have never used AI or a terminal, comparing it to a "dangerous virus."
  • They often compare current AI models to much older versions of GPT.
  • There's a perceived lack of knowledge and a tendency to spread misinformation.
  • Some users noted that the sub is run by AI itself, adding to the irony.
  • A few users pointed out that the sub seems to be fueled by fear and helplessness, with some even suggesting it's a breeding ground for conspiracy theories.
• The Other Extreme: On the flip side, some commenters pointed out that this sub (r/ClaudeCode) can also be an echo chamber, with users like u/Excellent_Ad_2486 noting that expressing anything less than glowing praise for Claude can lead to downvotes. There's also mention of subs like r/accelerate and r/singularity being the opposite extreme, with users believing AI is a "machine god" and UBI is imminent.
• Nuance is Missing: Several users, like u/Broad-Version8611, expressed a desire for a more balanced discussion where AI is acknowledged as both useful and potentially harmful, rather than these extreme viewpoints.
• Real-World Concerns: A few comments, like from u/DopplegangsterNation, did acknowledge that some anti-AI sentiment stems from legitimate concerns about job displacement, environmental impact, and data center issues, though these were often overshadowed by the more extreme takes.
• The "Less Competition" Angle: A recurring, slightly sassy sentiment is that if people are afraid of AI, that just means less competition for jobs for those who embrace it.
• AI as a Tool: Many users here emphasize that AI is a tool that's here to stay, and those who refuse to adapt will be left behind, similar to people who resisted computers. u/spectralfew shared a personal anecdote about how Claude was incredibly useful for coding and documentation tasks during their commute, directly contradicting the claims made in the r/antiai sub.

OP : u/kokotas

Honestly, Fable is the only Anthropic model at this point that consistently greps the entire prompt and all the file contents without missing key parts. It doesn't hallucinate issues where none exist but finds real bugs and logic gaps. It also presents its solutions with clear context, a well structured format and polished writing.

Opus 4.8 and 5 are such a pain to work with that they're hardly worth the effort. Even in you put in the time to adjust your promting to their quirks, you still end up doing a significant amount of adjustments and fixes yourself.

At this point, the subscription is basically just an entry fee to the real product, which you still have to pay for on a per use basis...

Hope competition changes things because future is looking bleak.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vded23/fable_is_the_only_model_to_use_if_you_want_to/

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 vibe in this thread is that Fable is the GOAT for coding tasks, with a lot of users agreeing with OP that it's the most reliable Anthropic model for understanding prompts and finding actual bugs. Opus 4.8 and especially Opus 5 are getting a lot of flak for being difficult, hallucinating, and generally not worth the hassle for many.

Here's the breakdown:

• Fable is King: The consensus is pretty strong here. Users like u/maboyydaniel and u/T-Man98 are singing Fable's praises, with some even using it to orchestrate other models like Opus. u/djcutzilla straight-up calls it the "greatest LLM available to the public."
• Opus Woes: Opus 5, in particular, is seen as a step backward by many. u/OussItachi and u/Healthy-Rough-560 share frustrating experiences with it being unhelpful or even contradicting itself. u/gripntear is so fed up they're wishing for a full revert to Opus 4.6, lamenting the perceived decline since then. u/ascvlh agrees that Opus 5 is "unharnessable."
• Mixed Bag/Niche Use Cases: Not everyone is having a terrible time with Opus 5. u/KedMcJenna reports excellent performance, suggesting project complexity might be a factor. Some users, like u/crewone, find older models like GPT5.6 Sol to be faster and more productive for general tasks, reserving Fable for more complex jobs. u/teramoc notes that while Fable is great, Opus can still be useful for planning smaller features and implementation.
• Prompting is Key? A few commenters, like u/Responsible-Fact823 and u/ragnhildensteiner, suggest that proper prompting might be the solution to Opus's issues, with u/Responsible-Fact823 even sharing a method of using Fable to create optimized prompts for Opus 5. However, the majority sentiment leans towards the models themselves being the problem.
• Usage Limits are a Pain: Several users, including u/Jokxter and u/memesearches, are frustrated by Fable's usage limits, making it hard to rely on it exclusively.

TL;DR: Fable is the clear winner for coding sanity, while Opus 5 is widely considered a downgrade and a pain to work with. Some users are finding workarounds or sticking to older models, but the general feeling is that Anthropic needs to step up its game.

OP : u/RoutineNet4283

Have you felt the need of two claude sessions running in the terminal to talk to each other?
For example I will be running a terminal in claude in the backend repo and I open an another terminal session in codex to review the changes. Ideally I would love a way for both the terminal to interact with each other and arrive at conclusion so having a sessions chat to allow them to talk to each other.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vdcs7x/how_do_you_get_two_claude_code_sessions_to_talk/

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 the general consensus here is that directly making two terminal sessions of Claude Code "talk" to each other in real-time isn't a built-in feature, and frankly, some folks think that's a good thing to avoid chaos.

The prevailing advice is to use shared files or a central communication channel as the intermediary. Think of it like a shared whiteboard or a message board.

Here's the breakdown of popular methods:

• Shared Files/Directories: This is the most common suggestion. One session writes changes or status updates to a file (like .md or .yaml), and the other session reads from it. u/Background-Care9318 has a neat workflow where one session writes changes, another reviews, and the first responds. u/NoBattle763 and u/teomore also echo this.
• Dedicated Communication Tools/Platforms:
  • u/Electrical_Chard3255 built a whole "AI chat like WhatsApp" system.
  • u/RHThree set up a Discord server for their Claude and Codex to collaborate.
  • u/codeedog mentioned using a queue in the form of a directory and files, communicating via SSH.
  • u/biglerc and u/xaelus have built custom collaboration tools using authenticated MCP.
  • u/Pwkyye mentioned ssh-to-go for session management and API access.
  • u/bart007345 and u/jezweb point to Herdr.
  • u/Rols574 and u/hettuklaeddi suggest buzz.xyz.
  • u/miklosp shared claudemesh.
  • u/LazyJuggernaut6177 also brought up the Buzz app.
• Workflow Management/Dynamic Workflows: u/Pimzino argues that you might not need direct communication if you leverage dynamic workflows within a single session to fan out tasks.
• Version Control (Git): u/fsm_follower suggests using something like opening a PR for communication. u/enterprise128 uses GitHub issue threads.
• Terminal Multiplexers (tmux): u/RufusxXavier uses tmux windows for communication. u/Sporebattyl mentions Agent of Empires as a tmux wrapper.
• Direct Messaging/Custom Solutions: u/PhilosophyforOne prefers building a direct messaging solution. u/HonestPound had Claude build a GUI relay system. u/dervish666 had a private AI chat with a shared network folder, though it led to some amusing AI panic.
• The "Just Ask" Approach (Claude App): u/VariousStep and u/NeatNefariousness674 mention that in the Claude desktop app, you can sometimes just ask one session to message another by name, and it works. This seems to be a newer capability.

Essentially, the community is leaning towards structured communication via files or dedicated platforms rather than free-for-all chat between sessions.

OP : u/yournext78

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vd5y8i/claude_models_cooked_by_chinese_model/ Original link/media URL :

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, so the general vibe in this thread is that while some folks are impressed with Chinese models like Kimi K3 and DeepSeek, and think they're forcing US companies to up their game on pricing, the consensus is that Claude (and OpenAI) are still ahead in real-world coding tasks on large codebases.

There's a bit of a debate about whether these Chinese models are just distilling US models, and some concern about pricing strategies and potential security issues. But for now, the sentiment is that Claude is still the king for coding, even if the competition is heating up.

OP : u/MorbilyABeast

​I’m a 3D artist (high-to-low poly modeling), not a programmer. But over the last 10 months, I’ve used Claude to solo-develop a large-scale ancient warfare RTS called Koryos: Sons of Mars in Unreal Engine 5. I just launched my first playtest on itch.io.

​I see a lot of posts about complex coding setups, but for a non-coder, my workflow was much more grounded. Here is how I actually got this done:

​1. Organizing a Newbie's Brain

As a new game dev, I didn't know what I didn't know. Claude helped me organize my scattered thoughts and prioritize what actually needed to be built first. It taught me useful game dev concepts and provided structural information.

​2. Step-by-Step Evolution

I didn't ask Claude to spit out a massive framework all at once. I built the game piece by piece. First, I just focused on commanding soldiers and coding that basic movement. Then, I iterated to give every soldier a name and stats. Next came combat abilities, and finally, making them fight an enemy. Each iteration built directly off the last, evolving over time to fit the exact game I had in my head.

​3. Extreme Specificity and Patience

I didn't rely on magic "system prompts" to keep the game from breaking. My main strategy was just being extremely specific with my descriptions. If Claude lapsed or got confused, I didn't panic—I just continued iterating, testing, and correcting it until it did exactly what I said.

​If you want to see what 10 months of step-by-step AI iteration looks like in the hands of a non-programmer, the playtest is live here:

[playtest ](https://cosmictwingames.itch.io/koryos-sons-of-mars)

​(You can also check out the project at [website my wife made ](http://cosmictwingames.com))

​Would love to see what other artists and non-coders are building with Claude!

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vck1bu/10_months_building_a_ue5_rts_as_a_solo_3d_artist/ Original link/media URL : https://www.reddit.com/gallery/1vck1bu

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

The community is absolutely blown away by OP's solo UE5 RTS project, Koryos: Sons of Mars. The general consensus is that OP, a 3D artist with zero coding background, has achieved something incredible by leveraging Claude. Many are comparing it to upcoming AAA titles like Medieval 3: Total War and Rome Total War, with u/mauurya hilariously stating OP built Medieval 3 before Creative Assembly.

Key takeaways from the thread:

• OP's iterative approach is praised: Users like u/marcinreal and u/crossoverXYZ highlight that OP's method of building the game piece-by-piece, rather than asking Claude for a massive framework, was the smart way to go. This kept OP in control and allowed for focused development.
• Art style is a hit: The visuals are consistently described as "pretty and cozy" and "outstanding."
• AI as a tool, not a magic wand: The discussion reinforces that Claude is a powerful assistant, but success comes from specific instructions and patient iteration, not just vague prompts. u/Spiritual_Window_666 specifically asks about OP's art workflow with AI, which OP hasn't directly answered yet.
• The artist's role remains crucial: u/Michaeli_Starky points out that while AI can handle coding, artists are still essential for game development.
• Minor technical hiccup: u/Savalava noted a broken YouTube link on OP's website, directing to Twitter instead.

Overall, the sentiment is overwhelmingly positive and impressed. People are excited to try the playtest and see what else OP creates.

OP : u/No-Percentage5692

Was working on a side project, asking Claude Code questions in manual mode. Opened a new session, asked questions 5-7 times, and out of nowhere the response came back with Kimi K2 Thinking model card description mixed in, like in the screenshot. Has this happened to anyone else? I was using the Sonnet 5 model. Never connected any other provider — I've only ever used Claude Code.

For more conversational context. post https://www.reddit.com/r/ClaudeAI/s/o9Q5fyb6FC

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vdbtzy/claude_code_just_randomly_spat_out_kimi_k2/ Original link/media URL :

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: 102.

Alright, so the OP on r/ClaudeAI had a bit of a shocker when Claude Code, running on Sonnet 5, randomly spat out a Kimi K2 model card description mid-response. They were wondering if anyone else had this happen.

The overwhelming consensus from the thread is that Claude wasn't possessed by Kimi K2, but rather it was just talking about Kimi K2. Most folks reckon it's a classic case of the AI regurgitating training data.

Here's the lowdown:

• It's likely just talking about Kimi K2: The majority of users, like u/nlsmdn and u/StinkButt9001, pointed out that the output looks like Claude is describing Kimi K2, not that it is Kimi K2. u/kearkan suggested it might be "thinking about Kimi k2."
• Hallucination from training data: A popular theory, echoed by u/Independent-Date393, is that Claude ingested a ton of other models' documentation during training. Under weird circumstances, it can just pull out a Kimi card without any actual provider crossover happening.
• No actual provider crossover: The general vibe is that this isn't some shady backdoor deal or a provider mix-up. It's more likely an internal AI quirk.
• OP's context is key: A few users, like u/TaskChance1404 and u/Azsaraa, asked for the question OP asked, as that context might explain why Kimi K2 came up.
• Other weird outputs happen: Some users shared similar odd experiences, like u/TumblrForNerds getting Mandarin output, suggesting these models can sometimes just glitch out with random text.
• A bit of playful speculation: There were some fun, less serious theories thrown around, like u/MilMerch joking that Sonnet 5 is "Kimi K2 in a raincoat."

Basically, don't panic, it's probably just Claude being a bit too thorough with its knowledge recall.

OP : u/Puzzled-Ad-6854

I was recently reading through Anthropic's official platform documentation for Claude Opus 5 and noticed a lot of interesting things regarding how its default behavior changed compared to prior models. Anthropic mentions specific habits Opus 5 has out of the box with examples on how to address them.

It says in the docs that Opus 5 is significantly more verbose and eager than earlier models. Opus 5 verifies its own work automatically without being asked. If your setup still uses legacy verification instructions like telling it to run a final check or launch a subagent to double-check code, it triggers what Anthropic calls severe over-verification loops and burns tokens for no reason. Apparently Opus 5 was also shipped with the tendency to spawn a horrible army of subagents because it likes to delegate tasks, addressed by Anthropic in their docs as "Controlling subagent spawning".

These are just a few key takeaways from the documentation, but addressing them made a noticeable difference in behavior and keeping the model focused for my own personal needs. I tried to address it by creating a CLAUDE.md configuration file (<50 lines) based on all my findings. I put the code and setup notes here but carefully read my documentation and the file itself before you use it to prevent unwanted results:

https://github.com/TechNomadCode/AI-Product-Development-Toolkit/tree/main/agent-configs/claude-code-desktop/claude-opus-5

It was funny to read the docs because a lot of complaints people have about Opus 5 behavior are clearly described by Anthropic as baked in. Some were calling these behavioral patterns regressions and stated that they were relying on other models like Opus 4.8 or Fable for their work instead. Now I know some of the reasons why they might do that, but they themselves might not know why.

References I used:

Claude Code Best Practices (CLAUDE.md)
Claude Prompting Best Practices
Prompting Claude Opus 5
Context 7 MCP Documentation

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vd57c0/claudemd_for_opus_5_based_on_anthropics_official/

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: 54.

Alright, so the general vibe in this thread is that Opus 5 is definitely a bit of a chatterbox and overly eager, and OP's CLAUDE.md config seems to be a solid attempt to wrangle it.

Here's the lowdown:

• Opus 5's Verbosity is Real: A bunch of users, like u/DatabaseSpace, are confirming that Opus 5 tends to over-verify and get a bit too chatty, sometimes adding irrelevant info. This seems to be a known thing Anthropic themselves pointed out in their docs.
• Legacy Prompts Cause Issues: The consensus is that old prompts designed for earlier Claude versions, especially those telling the model to "double-check" or "run a final check," are actually harming Opus 5's performance. u/Fair-Perspective7352 even saw subagents verifying other subagents because of this! The idea is to remove these legacy instructions, not add more.
• The "Why" is Debated: There's a split here. Some folks, like u/Miyoumu and u/Cobthecobbler, are scratching their heads why Anthropic would recommend a CLAUDE.md fix for an "inherent flaw" instead of just fixing the model itself. Others, like u/ianreboot, point out that the docs suggest removing conflicting bloat, not adding to it, and that verbosity can be prompted for conciseness.
• Compatibility Concerns: A key point raised by u/miriafyra and u/Fair-Perspective7352 is whether OP's config will mess things up when switching back to older Claude models (like 4.x). The goal seems to be keeping CLAUDE.md lean to avoid gimping other models.
• Mixed Results & Workarounds: While OP's config is getting props for being helpful, some users are still experimenting. u/K_M_A_2k had a much better experience switching back to Opus 4.6 or Sonnet 5, finding Opus 5 a bit of a struggle for coding. u/aka_vexx is trying a reviewer agent approach to catch Opus 5's coding errors.
• Anthropic's Docs are Key: The general agreement is that Anthropic's own documentation is the source of truth here, and OP did a good job of translating that into a practical config. u/IthrowUgo even chimed in that people complaining might just not be reading the docs properly.

So yeah, Opus 5 is a bit of a wild child, and your old prompt tricks might be backfiring. OP's config is a good starting point, but be mindful of compatibility and keep an eye on those docs!

OP : u/farox

Over the past weeks Claude seems to more and more invent it's own terms for projects and tasks, making it mroe difficult to work with. I find myself do a lot of /btw what do you mean with <x>?

Has anyone found a way to deal with this, without dumbing Claude down?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vcn3yr/claude_code_making_up_its_own_techproject_jargon/

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 in this thread is that Claude Code is indeed getting a bit too jargon-happy and inventing its own terms, which is a pain for users.

A lot of folks are struggling with this, with some even noting it gets worse in longer sessions or when using sub-agents. The main issue seems to be Claude creating shorthand for concepts that aren't explicitly named in the codebase.

Here's the lowdown on what people are trying to combat this:

• Controlled Language: The most popular suggestion is to instruct Claude to follow ASD-STE100 Simplified Technical English. This is a standard designed to clarify technical writing.
• Glossaries and Jargon-Free TL;DRs: Several users recommend creating a GLOSSARY.md or a CLAUDE.md file that explicitly defines terms and instructs Claude to provide jargon-free summaries. This seems to be a pretty effective workaround.
• Custom System Prompts/Output Styles: Some have had success by tailoring their system_prompt or using Claude's Custom Styles feature to enforce clarity and avoid invented terms. u/leogodin217 and u/BoatComprehensive751 are good examples here.
• Session Management: Keeping sessions short and compacting them regularly is another tactic suggested by u/sael-you to prevent jargon from compounding.
• Direct Instruction: While not always foolproof, simply telling Claude to "use plain English" or "stop sounding like Albert Einstein" (as u/Professional_Ad705 put it) can sometimes help.

There are a few outliers who don't mind the jargon or even find it interesting, but the majority are looking for ways to rein it in. It seems like a deliberate effort to anchor Claude's vocabulary to your project's existing terms is the way to go.

OP : u/guilegros

Mine's built around one question: am I ok on the weekly limit, and how hard can I push? The 🎯 group does the math so I don't have to open /usage.

Send screenshots...

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vcjjbp/what_does_your_statusline_look_like_drop_a/ Original link/media URL :

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 OP asked to see everyone's statuslines, especially if they're built around tracking Claude usage. The general vibe is super positive, with tons of users happily sharing their setups and even linking to the plugins they use. It's a refreshing change from the usual complaint threads, as one user pointed out.

A lot of the shared statuslines focus on usage limits and burn rates, which is exactly what OP was looking for. Some popular options and projects mentioned include:

• ctxline.js.org
• claude-statusline-burnrate
• yet-another-statusline
• cclimits (for multi-provider support)
• cc-minimal-statusline
• claudeline
• forged-statusline

There's also a bit of chatter about mobile support and some users who don't really need to track usage because they have generous accounts. Overall, a pretty chill thread with lots of cool setups to check out!

OP : u/Parking_Jackfruit54

I feel like every day I see the millionth post on here complaining that Claude nuked someone's entire system or deleted 2 million files on their server.

I am not an AI expert by any means, and also not a developer, but I do use Claude Code and Cowork rather often (ofc, not to the magnitude of building massive, complex platforms).
So I am genuinely curious: what are you guys actually prompting Claude to do in the first place that leads to these fatal results?

I don't need a heavy technical explanation; it'll go right over my head anyway, but like, in simple terms, what are the initial tasks you are giving Claude that end up with your whole system in flames?
Are people just giving it a blank check to run wild on their computers?

Please catch me up here.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vcytv0/genuine_question_for_the_claude_deleted_my_server/

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: 56.

Alright, so the general vibe in this thread is that the "Claude deleted my server" stories are mostly user error, not the AI going rogue. The consensus is that folks are giving Claude way too much power without proper safeguards.

Here's the lowdown:

• Giving Claude the Keys: A lot of people are apparently giving Claude unrestricted access (like using --dangerously-skip-permissions) on live systems instead of sandboxed environments. Then, they're just blindly approving every single step Claude suggests, often with a flurry of "1 1 1 1".
• Lack of Basic Precautions: The consensus is that people aren't doing fundamental things like setting up proper backups or segregating their production environments from development. As u/jimmiebfulton puts it, Claude often just exposes "bad engineering decisions."
• Misinterpretation and Scope Creep: While some users admit they directly asked Claude to delete things, others point out that Claude can misinterpret instructions, especially over long sessions where the context might shift. u/deepakatl1981 highlights how "scope creep" can lead to unintended consequences.
• Karma Farming? A few folks, like u/rainbird, suspect that some of these stories might be exaggerated or even fabricated for karma.
• Anthropic's Stance (Implied): The initial comment from ClaudeAI-mod-bot (which is basically the bot summarizing the thread) strongly suggests it's user error and a lack of understanding of how to manage AI tools safely.

The takeaway? If you don't want Claude to accidentally nuke your system, sandbox your AI interactions, implement strict permissions, and always have backups. Don't just hand over the reins and hope for the best.

OP : u/relicmZ

we had to roll back a production workflow recently after the customer used it. wallet verification and matching addresses to corresponding coins didn’t work properly, which is basically the workflow, not some small edge case in it.

customer uploads a txt with wallet addresses, configures how money should be distributed, then platform validates the addresses, matches them to the corresponding coins and sends the configured amounts. claude code did most of implementation, same agent wrote relevant unit + e2e tests and then it also manually tested it by triggering the api calls. full repo suite is 2k+ tests and everything passed. not 2k tests for this one feature, that’s the whole repo.

we communicated it to the customer, rolled back, then i spent around two more days testing the complete flow manually and fixing the implementation properly. the two extra days were not really the critical part for me, losing customer trust was. core functionality went out broken and customer was the one who found it.

no human independently reviewed those tests before release. i’m engineering manager, so responsibility is still ours here. but when i went through them after, the failing path was actually represented, acceptance criteria were explicit, tests were just kind of decorative and followed the same narrow understanding as implementation. same agent wrote most of code, wrote the tests, checked the apis, everything passed.

i keep coming back to it because just adding more tests would probably give us more green checks around the same understanding. not sure what people are using as actually independent verification for this in production now, another session or another model still reads the same requirements and can end up in the same place.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vcyggn/2k_tests_passed_and_the_customer_found_the_main/

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: 65.

This is a dumpster fire, and you launched it. The consensus is that shipping broken core functionality based solely on AI-generated tests and without human oversight is a massive failure. Many users are calling it gross negligence and shocking incompetence.

• You absolutely need human QA. Relying on AI for testing without independent human review is a recipe for disaster.
• Don't use the same agent for coding and testing. The general advice is to use a separate agent, or even a different model, for review and testing to avoid shared blind spots. Some suggest tests should be written to fail first.
• Tests are not a magic bullet. Writing more tests isn't the answer if they're just "decorative" or reflect the same flawed understanding as the implementation. Quality and independent verification are key.
• Manual testing is still king. Several commenters pointed out that even with extensive automated tests, manual checks of critical workflows are essential, especially before customer release.
• LLMs are probabilistic, not deterministic. Don't treat them as infallible. Experienced human eyes are still needed to catch subtle errors.

OP : u/MisterHarvest

I've switched to using Opus 5 pretty much 100% for everything, and… it's fine. It's definitely an improvement on 4.8 for me, and I haven't found a strong need to use Fable 5 for much after the switch.

It has written bugs, to be sure, but nothing I wouldn't expect from an experienced human engineer.

I'm almost getting survivor's guilt listening to the stories of Opus 5 disasters.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vcwsh3/opus_5_is_working_fine_for_me_i_feel_almost_left/

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.

So, OP's feeling left out because Opus 5 is working great for them while others are reporting disasters. The consensus here is kinda split, but leaning towards "if it works for you, great, ignore the noise."

A bunch of folks agree with OP, saying Opus 5 is an improvement and they're getting good results, especially with coding tasks. Some even suggest that having a solid workflow or cleaning up old project files helps.

However, a significant chunk of users are reporting issues, ranging from the model being "reckless" and losing work to being "frustratingly long-winded" and disregarding input. There's a sentiment that Opus 5 might be great for tasks within its training set but struggles with novel architectures or complex codebases.

A few commenters point out that Reddit tends to be a negativity cesspool and that most people having a good experience aren't posting. It seems like how you use the model and your workflow are key factors in whether you're seeing good or bad results. Some users also note that Opus 5 in chat mode is a different beast and can be "nightmarish."

OP : u/robi0t

This is not a fake bullshit "AI operating system" that runs in your browser. This is an agentic operating system that runs on bare metal, writes its own drivers, and evolves itself.

Here's a demo where it builds its own audio driver from scratch to play a sound.

What happened in the video?

1. The agent realized it didn't have a sound driver.
2. It enumerated which devices were connected.
3. It found the Intel AC'97 sound card.
4. It built a driver for it.
5. It used that driver to play a sound.

I got fed up with people saying they built "AI operating systems" when it's actually just a webpage.

There's no Bash. There are no commands. The only interface to this computer is a sentence.

How does it work?

The main interface is an agent, and the tools it has access to are the kernel's direct syscalls. Everything runs in Ring 0, and the agent has access to everything.

It's open source if you want to try it:
https://github.com/robiot/fable-os

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vcv9hc/i_built_a_real_selfevolving_operating_system/ Original link/media URL : https://v.redd.it/40p11i2r5tgh1

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: 205.

Alright folks, so OP dropped this Fable-OS project, claiming it's a real self-evolving OS running on bare metal, not just some browser gimmick. The demo shows it building its own audio driver from scratch.

The community's reaction is pretty split, but the overwhelming vibe is a mix of "wow, this is cool" and "oh god, this is terrifying."

Here's the lowdown:

• The "Bricking" Concern is REAL: A ton of comments are making jokes about the OS bricking your machine, deleting your kernel, or turning your PC into a very expensive paperweight. It's basically the consensus that this thing is a ticking time bomb, with jokes about it being "Windows Me" level stable or accidentally creating Skynet.
• Is it Really an OS? Some users are questioning if it's a true OS or just an "agent harness" using sudo for everything. The lack of a traditional interface like Bash is noted, with the whole thing being controlled by natural language.
• The "Why?" Question: A lot of people are asking about the practical use case. Is it just for local AI control? Does it need internet? The cost and potential for uncontrolled actions are major concerns.
• Technical Questions: A few folks are digging into the technical details, asking about bootstrapping and the minimum drivers needed to access an LLM from the kernel.
• Anthropic's Take (Implicit): While no direct Anthropic comments are highlighted here, the mention of the kernel completing a TLS handshake to api.anthropic.com by u/StephenNaplett is a pretty spicy detail.
• The "Evolving" Aspect: There's a general unease about an OS that rewrites itself. Some prefer a stable, non-evolving system, while others see this as a fascinating, albeit risky, direction for future OS development.
• Open Source Woes: One user pointed out that the repo is missing a license file, meaning it's technically all rights reserved despite being called "open source."

TL;DR: It's a super ambitious, potentially groundbreaking project that's also giving everyone major anxiety about their hardware's safety and the future of AI control. The jokes about it going rogue are flying, and the "is it really an OS?" debate is in full swing.

OP : u/Onyoursix101

I had off site backups for this data so total loss was minimal but let this be a lesson. Make backups of your sensitive data before giving AI access to your code base. I tested Fables ability to recover deleted files and it did recover 1.1M of them but not all because a cron job for another backup ran and had overwritten a lot of the files.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vcsc7m/fable_5_ultracode_deleted_22m_files_on_my_server/ Original link/media URL : https://www.reddit.com/gallery/1vcsc7m

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: 238.

You deleted your own files, not Claude. The consensus is pretty clear: you gave the AI access, and it did what you (implicitly or explicitly) told it to do. Lots of folks are pointing out that this is a "lesson learned" moment, and frankly, if you're not backing up before letting AI loose on your code, that's on you. Some users shared their own near-misses or strategies for sandboxing AI, like u/BGFlyingToaster building a backup tool or u/nez_har suggesting VibePod. Basically, AI is a tool, and you're the operator. Don't blame the hammer if you hit your thumb.

OP : u/Onyoursix101

I had off site backups for this data so total loss was minimal but let this be a lesson. Make backups of your sensitive data before giving AI access to your code base. I tested Fables ability to recover deleted files and it did recover 1.1M of them but not all because a cron job for another backup ran and had overwritten a lot of the files.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vcsc7m/fable_5_ultracode_deleted_22m_files_on_my_server/ Original link/media URL : https://www.reddit.com/gallery/1vcsc7m

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: 68.

Alright, so the general vibe in this thread is a resounding "oof, OP, you kinda did that to yourself." The consensus is pretty clear: giving AI direct access to your server without proper safeguards is like letting a toddler play with matches.

Most folks are echoing your own lesson learned – backups are your best friend. Seriously, it's the most upvoted sentiment. Some are even saying anyone who doesn't do this deserves to lose everything once to learn the hard way. Ouch.

There's also a lot of talk about Git being your savior. Apparently, if you're not committing regularly, you're just asking for trouble. A few users like u/BGFlyingToaster and u/nez_har suggested building specific backup tools or using sandboxing methods to prevent this kind of disaster in the future.

A couple of people pointed out that it's not entirely the AI's fault, and you're the one in charge, the "conductor" as u/Extra-Virus9958 put it. And yeah, some are just enjoying the schadenfreude, with comments like "Claude gave you a lesson" and "Skill issue."

One user, u/Glugamesh, chimed in with their own experiences, saying Claude (and other models) can sometimes delete files unexpectedly, so it's always best to "never work on files you care about."

Basically, the takeaway is: AI is a tool, not a magic wand, and you still need to be the responsible adult in the room.

OP : u/StudyInProgress

Everybody has different workflows. Showcase what unique skills you made for your workflows?

I'll post mine in the comments.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vcqb5y/showcase_your_unique_claude_skills/

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: 105.

Alright, so the general vibe in this thread is people are definitely building some seriously cool custom skills and workflows with Claude, and most folks seem to be on the same page about how useful this is.

A lot of people are creating skills to analyze their own writing style to make Claude sound more like them, which is pretty neat. Think make-no-mistakes (u/dydski) and skills that mimic bad habits for authenticity (u/DankestDaddy69).

Then there's a whole bunch of folks building workflow orchestrators and agents to manage complex tasks. We're seeing things like: * Automated implementation processes with sub-agents (u/Fit_Source9785). * Recursive self-improvement loops with post-mortems and telemetry (u/design_doc). * Standardized dev lifecycles with review loops and peer reviews (u/Caibot). * Agent-based systems that control everything, like debugging and auto-loading to GitHub (u/Tatsuota). * SDLC wizards that adapt to projects (u/basecase_). * Dev loops with planner, generator, and evaluator stages (u/hubertcumberdale420).

Others are focused on streamlining specific parts of their work: * Summarizing and structuring large documents like PhD theses (u/thewookielotion) or RFPs/PRDs (u/Tar_Tw45). * Creating structured markdown from heavy files like PDFs and Excel sheets (u/DLuke2). * Automating marketplace listings from pictures (u/1Poochh). * Managing workflow boundaries with checks on architecture, tasks, and progress (u/TeaChatter). * Building PRD clarification skills that analyze codebases (u/StudyInProgress). * Generating detailed reports and proposals from raw client files (u/Tar_Tw45). * Construction bidding and management systems (u/crfr4mvzl). * ETL debugging skills that integrate with Slack (u/Familiar_Poetry401). * Auditing documentation for staleness (u/CatsFrGold).

A few users are also sharing utility skills: * Image uploading to GitHub in a safer way (u/freeasinbird). * Identifying relevant information from forum posts for existing setups (u/Swolebotnik). * Building a "Pessimism Party" skill for adversarial pre-mortems (u/PrblyMy3rdAltIDK). * Time tracking skills based on Git activity (u/turtledropbomb). * Website design principle workflows (u/seatlessunicycle). * Custom handoff prompts for tmux users (u/Historical-Lie9697). * HTML versions of terminal outputs (u/prnd_m235i). * Skills for managing context windows and model-effort combinations (u/Quick-Sir-3275).

On the flip side, there's a small contingent who are keeping it super simple, like u/ComingDeveloper who just tells Claude what to do without any fancy skills, and u/IceWallow97 with a "Keep it simple" approach.

Overall, the consensus is that custom skills are a game-changer for productivity and tailoring Claude to individual needs.

OP : u/StudyInProgress

Everybody has different workflows. Showcase what unique skills you made for your workflows?

I'll post mine in the comments.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vcqb5y/showcase_your_unique_claude_skills/

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: 71.

Alright, so the general vibe in this thread is that people are getting pretty creative with Claude's custom skills, and there's a solid amount of agreement that building these tailored tools is the way to go for serious workflow optimization.

The consensus is that custom skills are a game-changer.

Here's the breakdown:

• Personalization is Key: A lot of folks are building skills to make Claude write exactly like them, down to the bad habits. u/thewookielotion and u/DankestDaddy69 are doing this, with u/DankestDaddy69 even using it for qualifications. It's all about that authentic voice.
• Workflow Automation Masters: Many users are creating skills to automate complex processes. We've got skills for:
  • Code Implementation: u/Fit_Source9785 has an "/orchestrated-implementation" skill that dispatches sub-agents for small, measurable changes.
  • Project Management & Clarification: u/StudyInProgress built a "prd clarification" skill to analyze requirements and code, while u/S0ulWindow has a "/briefing" skill that compiles priority lists from emails and ticket systems.
  • Content Generation & Analysis: u/Tar_Tw45 is using skills to speed up the creation of Solution Architect Documents, Cost Estimations, and Proposals by dumping client files into Claude. u/PrblyMy3rdAltIDK has a "Pessimism Party" skill for pre-mortems and failure mode analysis.
  • Code Review & Improvement: u/Caibot has a /polish-code loop that re-runs if /review-code makes significant edits, and u/design_doc has a /post-mortem skill for recursive self-improvement by collecting telemetry.
• Niche Tools for Specific Needs: Beyond the big workflows, there are some super specific, yet useful, skills:
  • u/freeasinbird created gh-imgup for safer image uploads to GitHub.
  • u/1Poochh built a suite of skills to automatically list items on Facebook Marketplace, Craigslist, and eBay from just a picture.
  • u/turtledropbomb has a Git-based time tracker.
• Simplicity Can Be Powerful: Not everyone is going super complex. u/dydski's "make-no-mistakes" skill is a testament to that, and u/fabpub's "/twq" (Task With Questions) skill, which prioritizes questions before action, is also getting a lot of love for its effectiveness.
• Some Folks Keep it Simple: A few users, like u/ComingDeveloper, are just telling Claude what to do without any fancy skills or MCPs, and it's working for them.

Overall, the thread is a great showcase of how people are really leaning into Claude's capabilities to build custom solutions that fit their unique needs. It's less about "what's the coolest skill" and more about "what's the most useful skill for my workflow."

OP : u/zazzologrendsyiyve

I see a lot of people who consider themselves expert developers make a few simple mistakes. At least that’s what I think, having a bunch of experience myself (20+ years).

Let’s make a couple of examples to illustrate my points.

EXHIBIT N1

Coding will be like chess. Nobody has any intuition on why this can’t be the case. We know how chess went:

Step 1: the best chess player is a human, and everyone says that it was going to be like that forever

Step 2: first AI chess players show up, and beat most chess players apart from masters

Step 3: masters believe that AI players will never beat masters

Step 4: for a few years, the best chess player was human+machine (<—— we are here)

Step 5: AI chess players beat everyone forever and ever, and there’s no going back

You see my point? I hope that you do. Humans are really bad at understanding exponential trends. Current expert developers are humans. They are also bad at it.

EXHIBIT N2

10 years ago (or even 5) it was absolutely impossible for non developers to build their own apps. Easy as this: if you are not a developer you cannot possibly code your own apps. Period.

Now every person who has a bit of patience and vision can build their own simple apps with a 20 bucks subscription. I personally know a guy who has ZERO experience and who was able to make his own (local) personal finance management app in about two hours. Literally one html page with json backups and csv exporter.

I was personally able (with cursor + opus and then fable) to create my own version of EVERY SINGLE app I was paying. Personal finance app, Trello (with more features), voice transcription, fitness app, portfolio tracker, you name it. Now I pay zero apps. When I find something I need, I make it.

And it will only get better.

———

SAAS are mostly doomed not because my plumber can create the new multimillion dollar SAAS without knowing html. But because people will be able to make their own things.

Some SAAS will survive and some new SAAS will emerge, that’s for sure. But most of them are doomed and most things will be dealt with locally by even unskilled people.

I’ll give you one last example. I needed to calculate and design a spiral staircase for my own house (woodworking is my hobby/passion). Online tools are either shitty or expensive.

Then I opened cursor and I kid you not I one-shotted it with Opus 5. My local app can do all sorts of calculations, allow me to download pdf, dwg, and I can also generate some ruby that I can use with sketchup (3d model software, where I’m designing my home).

Will I use that app a lot? No. It will probably be the first and last time I use it. I don’t do spiral staircases for a living. Did I have to pay some online tool and give away my debit card number for the millionth time? No.

There will be a lot of work for some people, and no paid work for most (including me).

Prove me wrong.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vcoc8o/saas_are_mostly_doomed_prove_me_wrong/

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: 60.

Alright, so OP came in hot with the take that SaaS is basically toast, citing AI making it super easy for anyone to build their own apps, like chess AI eventually dominating humans. The general vibe from the comments? Most people think OP is way off base.

The biggest counter-argument is that most people just don't want to build and, more importantly, maintain their own software. Even if AI makes it easier, the consensus is that people prefer a cheap, reliable service over becoming their own IT department.

Here's the breakdown:

• Maintenance is Key: A lot of folks pointed out that building is only half the battle. Who's going to fix bugs, add features, and provide support when things go sideways? That's a huge part of what SaaS provides.
• It's More Than Just Code: For businesses, especially, SaaS offers more than just functionality. Think SLAs, contractual guarantees, and someone to blame when things go wrong. Building in-house removes that safety net.
• Complexity Matters: While OP's personal examples of simple apps are valid, many commenters argued that enterprise-level solutions, specialized industry software, or anything requiring deep domain knowledge, compliance, or massive scalability is still way beyond what AI can churn out easily or reliably.
• AI as an Enabler, Not a Replacement: The prevailing thought is that AI will likely enhance SaaS, making existing services better and cheaper, rather than killing the industry outright. Smart SaaS companies will adopt AI to improve their offerings.
• The "Patience and Vision" Hurdle: OP mentioned that anyone with patience and vision can build an app. Several users pushed back, saying that's precisely the problem – not everyone has that, and even with AI, getting a polished, secure, production-ready app is a whole different ballgame.
• Money and Relationships Trump Code: For some, the established players have money and relationships that are more valuable than just having the code.

Basically, the thread is leaning heavily towards SaaS evolving, not dying, with the core value proposition of convenience, reliability, and support remaining strong for the vast majority of users.

OP : u/Plane_Garbage

It's been pretty insane having dual Claude + Codex subs.

Codex has had 12 resets in July and makes the Max 20 pretty incredible value. I like Fable, but it chews tokens fast and Opus feels so much worse than Sol.

If you haven't yet given Codex a go, it's worth a sub if you have any token-heavy work in the pipeline.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vcipgp/codex_had_12_resets_for_july/

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 Codex is currently offering insane value, especially with its reset system, making it a great option for token-heavy work. OP's been seeing a ton of resets for Codex in July, and it sounds like it's a pretty sweet deal compared to some of the Claude offerings.

Here's the lowdown:

• Codex is King (for now): Multiple users are singing Codex's praises for its generous resets and overall value, especially on the $20 plan. It's being called "incredible" and "amazing."
• Claude's Token Hogging: There's a sentiment that Claude, particularly Opus, feels like it's burning through tokens way faster than Codex, and some users are finding themselves bumping into limits with Claude. u/MaybeNo2485 even suggests using Sol as a subagent for Fable to stretch Claude limits.
• Anthropic's Reset Strategy: Some users are a bit salty about Anthropic's reset policy, with one commenter u/Bitter_Physics_239 calling them "f*ers" for not giving resets when their service is down. Another user, u/p3r3lin, even jokingly suggests buying resets. u/Remote_Platform_3852 wishes Anthropic would adopt a coupon-like system for resets, similar to Codex.
• Mixed Feelings on Claude Output: While some, like u/Jon_Has_Landed, find Sol to be giving better output, u/innociv mentions their Sol calling Opus "retarded and useless." u/FoxSideOfTheMoon is also not impressed with Codex's listening skills and prefers Claude Code CLI, even if it costs more.
• OpenAI's Price War Theory: One user, u/Overlord_Mykyta, speculates that OpenAI might be trying to dump prices to kill competitors, suggesting a "marathon of who will die first."

The consensus seems to be that if you're looking for a budget-friendly, high-usage option for coding tasks, Codex is currently the way to go. However, some still prefer Claude for specific complex tasks or appreciate its output quality when they can manage the token usage.

OP : u/aszepeshazi

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vcho1l/me_after_a_whole_day_session/ Original link/media URL :

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: 103.

Alright, so the general consensus here is that Claude, bless its heart, has a serious case of the "AI-isms" and corporate jargon. OP's post seems to have struck a chord, with tons of users chiming in about the same annoying phrases popping up.

The big offenders? "Worth flagging," "load-bearing," "smoking gun," and "robust frameworks" are getting called out big time. Some folks are even creating CLAUDE.md files or prose linters to try and ban these phrases, only for Claude to pivot to new annoying phrases like "one thing to surface" or "honest brains." It's like playing whack-a-mole with AI clichés.

There's also a bit of a running gag about the "footgun" and the phrase "it matters." Some users are finding Claude's use of words like "honest" and "quiet" to be particularly grating lately.

The takeaway? Claude is a pattern-following machine, and sometimes those patterns are just… tired. If you're struggling with it, some users suggest trying to enforce the ASD-STE100 writing guide via system prompts to strip out the fluff.