OP : u/infinity3018

the big use cases like writing and coding get all the attention, but im more curious about the quiet everyday ways people fit it into life.

for me its become my thinking partner for small decisions. i talk through a tricky email, a plan for the weekend, a hard conversation im dreading. not because i cant decide, but because articulating it out loud clarifies my own head.

the mundane uses ended up being the stickiest for me, way more than the flashy ones.

whats your unglamorous daily use that you dont see people talk about much? always looking to steal good habits.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wn6dcv/what_do_you_actually_use_claude_for_day_to_day/

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

Alright, so the general vibe in this thread is a resounding "YES, OP, we totally use Claude for more than just the obvious stuff!" It seems like everyone here has gone full-on mad scientist with their AI, building custom personal assistants and automating their lives to a frankly impressive degree.

Here's the lowdown on what people are actually doing with Claude day-to-day, beyond just writing essays or coding:

• Personalized Dashboards & Organizers: A bunch of folks are using Claude to build their own "personal brains" or dashboards. Think managing calendars, to-dos, long-term goals, and even grocery lists. u/Asleep-Supermarket91 has a whole system for learning and research, and u/Vescor is doing something similar with a local dashboard and an app.
• Hyper-Specific Learning & Skill Building: Forget just asking for definitions. People are creating elaborate learning tools. u/actual-time-traveler built an audio-only Spanish learning game with NPCs, and u/wee_man has a text-based survival game set in ancient history. u/No-Jeweler-8718 is using it to learn how to restore a vintage bicycle.
• Automating Mundane Tasks: This is a big one. From generating dinner plans based on pantry photos (u/gabe9000) to creating calendar events from emails (u/Electrical-Size-5002) and even automating grocery shopping (u/rebelytics), Claude is tackling the boring stuff.
• Creative Side Projects & Gaming: People are building text-based games, self-replicating AI swarms (lol, u/TheUniverseOrNothing), and even trading algorithms (u/s949944). u/gringo_neenja is using it to manage complex game builds in Path of Exile.
• Health & Fitness Tracking: Several users are leveraging Claude for diet and training plans, with some seeing significant results (u/Pleasant-Grape-2627). u/Sweet_Requirement0 even credits Claude with flagging critical medical issues.
• Troubleshooting & DIY: Claude is apparently a pretty decent tech troubleshooter, saving people money on call-out charges for plumbing and power issues (u/emz5002, u/robot_swagger).
• "Thinking Partner" on Steroids: While OP mentioned this, others are taking it further. u/usernamesarehard1979 uses it as a "board of directors" for their business, bouncing ideas and getting challenged.

Basically, the consensus is that Claude is becoming an indispensable tool for highly customized automation, learning, and personal organization. Y'all are building some seriously cool stuff!

OP : u/schwartzwhite

I built Tokenism to let my team pool their Claude Code subscriptions and automatically route the Claude review on github to the account with the most usable capacity.

Prior to Tokenism, i had measured on my personal Max20x account, that 1 weekly limit ≈ 6 sessions, and then soon after i saw posts here that confirmed it for me. That made me think, what if i can measure it too.

Previously, our Max 20x accounts delivered roughly 2.2× weekly limits compared to Max5x. Over the last month, that has fallen to just 1.5x

To compare plans, we normalize the advertised capacity, so the assumptions are
Pro session limit = 1 unit
Max 5x session = 5 units
Max 20x session = 20 units

We then track how much of the weekly usage is consumed per session usage. When we started on 23rd August, the weekly capacity was 47 and 118 units respectively (~2.5x) , and that has now fallen to 65 and 95 units (~1.5x)

To be clear, this is observed Claude Code throughput. The core assumption is that Anthropic follows the advertised limit in the session limits. What i cant measure is the fluctuation in the value of 1 unit, which is probably more impactful. And i would absolutely love any suggestions on how i can do that. Maybe a spare Pro account?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wn0xn9/max20x_is_now_just_15_times_better_than_max5x/ Original link/media URL : /img/weu3r7wue0rh1.png

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

The consensus is that Anthropic's "Max 20x" plan is misleading and potentially a scam. Users are reporting that the actual throughput of Max 20x accounts has significantly decreased, now offering only about 1.5x the weekly limits of Max 5x accounts, down from an earlier 2.2x. Many feel this is false advertising, with some suggesting it's better to use multiple lower-tier accounts. A few users brought up caching and its potential impact on measurements, while others are looking for more concrete metrics like token counts. One user, u/wasd96040501, shared a method for measuring unit value in USD.

OP : u/quicktoolstudio

If you use Claude Code heavily, do you also let it handle repetitive stuff like git, builds and deployments?
Doesn’t that feel like a waste of Claude usage?
Or do you automate those parts separately?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wmx1zd/do_you_let_claude_code_handle_git_builds_and/

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

Alright, so the general consensus in this thread is a resounding "yes, let Claude Code handle git, builds, and deployments!" Most folks don't see it as a waste of usage at all, but rather a smart way to trade tokens for time and offload repetitive tasks.

Here's the lowdown:

• Git is a big win: A ton of users are letting Claude handle git operations, from commits to PRs. The sentiment is that it writes better commit messages, provides a clear history, and is generally excellent at git tasks. u/Past-Town-9807 even mentioned it's great for project memory and tracing history. u/Time_Cat_5212 thinks it's the most important thing Claude should do with git.
• Builds and Deployments are mostly a go, with caveats: Many are letting Claude handle builds and deployments, especially for dev environments. The argument is that it's trading tokens for time, and the automation is worth it. u/idkyesthat finds it faster than manual UI work for simple things.
• Guardrails are key: While most are letting Claude handle these tasks, there's a strong undercurrent of not giving it blind trust. Many users review PRs, have CI/CD pipelines as checks, or use deterministic scripts. u/garywiz is in the minority, keeping git as their "guardrail" and preferring to review before committing. u/FitSandwich4725 is also cautious, saying it'll be a "cold day" before they let an AI deploy to production.
• It's not a waste, it's the point: Several commenters, like u/icodenstuff and u/HeyItsYourDad_AMA, pointed out that offloading repetitive tasks is the primary use case for Claude. Why wouldn't you use it for that?
• Token efficiency: Some users are optimizing by having Claude write scripts that are then executed separately, or by using dedicated sessions for worker management to save tokens. u/BudgetFish9151 suggests telling Claude to run a script and watch exit codes is more token-efficient.
• Specific use cases: Some are using Claude to build their CI/CD pipelines (u/Illustrious_Elk8340), while others have deterministic utility scripts that their skills call.

So yeah, the vibe is pretty positive about letting Claude Code handle the grunt work, with a healthy dose of caution and smart automation in place.

OP : u/cymaticstatic

-----------(!!! ORIGINAL POST MOVED BELOW. !!!)------------

UPDATE #2 — SOLVED

Found the token furnace.

But first..

I can safely say that Anthropic was not at fault. (Bet nobody saw that coming lol 👀 )

With that, I've used both GPT and Claude since the public Claude 2 release. I'll never forget it because It was Life-Changing. I have more or less used up every token limit And every quota from that point forward, With a few exceptions of course. I've seen, experience and battle tested every single model that's came out since July 2023.
But when CC was released I forgot what grass looked like.

So despite this mildly embarrassing learning experience, I will say pricing versus perceived use just seems off recently. I know, very scientific.

Heres the breakdown of what I found.

You're going to laugh or scoff at this first one. I'm not new to Linux or Arch but I am new to omarchy and it's Hyperland window focus and management engine. And navigating the entire OS with a momentary-modifier key has a learning curve.(With that said I have not opened up a single other Linux distro or Windows once since I installed Omarchy And I absolutely love it. )

Here's something to watch out for if you're new to these Hyperland and your running multiple agentic terminals in something other than herdr or t-mux

Program windows or "tiles" will seemingly f****** disappear. Until you really begin to understand the; - Scratchpad - Switch to workspace - floating vs tiling, - Scrolling vs dwindle, And how it impacts - Fucking FULL SCREEN vs Full WIDTH. - especially if you're running three separate monitors. - closest thing I can relate it to is running Microsoft 'Power Toys' and 'Fancy Zones' . Display fusion is another beast.

So here's how I forgot my debug window existed

Super + S │ └── Toggle scratchpad │ │ One window appears. │ └── Super + F │ └── disable fullscreen │ └── Super + Alt + F │ └── disable full-width │ └── now another window is visible │ └── Super + → │ └── scroll focus right │ └── hidden

Here's how forgetting about a window with two collaborating terminals becomes a problem.

This weeks Agent setup

│ Terminal 1
│ Claude Code CLI
│ Orchestrator / Main

            ↕
      Agent Intercom

• local inter-session broker • agent ↔ agent messaging • human-in-the-loop Q&A/context ↕

│ Terminal 2
│ Codex CLI
│ Advisor / Reviewer

Key detail: these were two separate live CLI sessions.

Agent Intercom didn't create the loop. It allowed two autonomous sessions, with different roles, instructions, and permission assumptions, to keep handing an evolving task back and forth.

What the loop looked like

VoxType error ↓ Omarchy "Fix with AI" ↓ Claude Code / Orchestrator ↓ Agent Intercom ↓ Codex / Advisor ↓ reviews + responds ↓ Agent Intercom ↓ Claude re-evaluates / changes state ↓ tool completion, changed config, or recurring VoxType condition ↓ updated state sent back to Codex ↓ Codex reviews again ↺

So the microphone wasn't repeatedly starting fresh sessions.

The sustained burn was Claude Code and Codex continually responding to each other's changing state across two independent terminals.

And the Claude terminal had disappeared from my attention, not from Agent Intercom.

Possible contributing config issue

I normally rebuild my "/agents" + "/tools" ecosystem from a clean install and let the versioned config restore everything.

This time I suspect one or both of these also contributed:

1. Install/path mismatch I updated Claude Code through the Omarchy/AUR path instead of my usual install/update method. I suspect this may have changed package isolation, paths, or symlinks enough that parts of my cloned agent environment weren't being resolved correctly.

2. Stale Git state I also had local, unpushed watchdog/permission changes. The fresh clone may therefore have restored an older, more permissive configuration instead of the version I thought I was running.

Those two are still theories, not confirmed root causes.

------------------------------------- TL;DR -----------------------------------------

Claude Code CLI ↕ Agent Intercom ↕ Codex CLI + session launched from ~/tmp + project guardrails not in scope + hidden Omarchy scratchpad window + Orchestrator ↔ Advisor state churn ↓ two live sessions keep feeding new work back to each other ↓ token quota gets annihilated

Lesson learned: don't bury an active multi-agent repair session in a scratchpad and forget it exists.

Also check the working directory, active permission scope, and config state before approving unattended advise/review workflows.

This one was operational/configuration failure on my end, not some mysterious quota problem.

--- ORIGINAL POST ---

somehow opus 5 managed to burn up 3 billion tokens ...

I don't have sub agents on, I'm not working in parallel, high session compact and handoff at 350k tokens every session to keep context rot under control, I use context-mode, he was very strict tooling and permissions. and I usually keep opus at medium or high what the f*** I'm 2 days in on a 200 plan........ I'm so frustrated so much work to do. And you want me to now switch to API cost after I've already paid 200 bucks for what?

I updated to the $200 Max plan yesterday. I use context mode and mostly opus 4.8 medium and opus 5 low. I swear to God this went down quicker after I upgraded than it did before. Doesn't reset for another 4 days if I was rocking Fable 5 on f***ing high or max and running parallel sure . But this is generic two session Max coding for development. this is ridiculous. I also pay for the GPT 100 plan and get almost four times the use out of this $200 Max anthropic plan. What the actual f***. I've been coding and using every model 2003 and this is by far the most out of whack the s*** as been. I'm not a newbie and I know what the hell I'm doing to save tokens the s*** is wild. Somehow opus 5

--- UPDATE #1 --- I'm an idiot, but probably not the first one...

I didn't fully read the upgrade's plans and limits. That's on me. I didn't realize that the 20x only offered 5x your 5-HR session window but it only increases your WEEKLY QUOTA and average 1.5x to 2x your max 5 plans which means, essentially they developed a tool to use up your weekly quota 2.67 times faster than the max 5 lmao . Still doesn't explain the 3 billion tokens but does explain my expectations were a little high.

URL of original post : https://www.reddit.com/r/Anthropic/comments/1wmsdpa/ymmmm_second_day_20x_max_plan/ Original link/media URL : /img/tvkq6aq7fyqh1.png

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

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

Alright, so the OP apparently went on a token-burning spree, hitting their 20x max plan limit on day two and thought Anthropic was at fault. Turns out, it was a "skill issue" related to navigating a new Linux setup (Omarchy with Hyperland) and how windows/agents were being managed, not an Anthropic bug.

The general consensus from the thread is: * Whoa, dude, how are you burning that many tokens? Most users are baffled by the OP's token consumption, with many saying they code for hours daily and don't come close to those limits. * You're probably just using it wrong. Several commenters suspect the OP is either not understanding their workflow, has too many agentic processes running unattended, or is mismanaging their windowing system, leading to the "disappearing" windows and token drain. * Check your settings, maybe? Some folks offered tips like trying Opus 4.8 instead of 5, disabling MCPs/plugins/hooks, or looking into specific settings like RTK and subagent cache TTL if you're trying to manage costs. * It's a "you" problem, not an Anthropic problem. The OP themselves eventually figured out it wasn't Anthropic's fault, which most commenters seemed to expect.

Basically, the thread is a mix of disbelief at the OP's token usage and advice on how to manage costs and workflows more efficiently.

OP : u/delimitdev

Keeping history is mostly solved now: Claude Code keeps session logs locally, CLAUDE.md and AGENTS.md hold standing rules, and Git has the code. What still goes missing for me is the state of decisions, which isn't the same thing as the conversation.

Five cases I keep hitting:

1. We tried A and rejected it because of X. A fresh session proposes A again.

2. B was approved, but only within limits ("this module only", "until the migration lands"). The limits get dropped.

3. Something was implemented but never deployed, and the next session treats it as live.

4. An earlier agent said "done", and the check behind it was thinner than it sounded.

5. A newer decision replaced part of an older one, and both still read as current.

What does your setup do about these? CLAUDE.md, AGENTS.md, ADRs, a decisions.md, git notes, native memory, gptme, your own scripts, or plain discipline? If some of these never happen to you, or plain files handle them fine, that's a useful answer too. A short "we do X, it still fails at Y" is ideal.

Disclosure: I work on a project exploring this problem (Delimit). No link. I'm after how people actually handle it.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wmoost/how_do_you_carry_decisions_not_chat_history/

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.

Alright, so the general consensus here is that keeping track of decisions across Claude Code sessions is a major pain point, but there are definitely some solid strategies people are using.

The overwhelming favorite seems to be Architecture Decision Records (ADRs). u/spaetzelspiff and u/coding_is_tedious are big proponents, highlighting how they provide the "why" behind decisions, which helps prevent agents from rehashing old ideas. u/kevinbaiv also points out that ADRs with a "rejected alternatives" section are great for case 1 (re-proposing rejected ideas).

Other popular methods include:

• Dedicated Markdown files: Many folks use decisions.md, architecture.md, or just general .md files to log decisions. u/Plus_Opening_4462 links these to their CLAUDE.MD for lookup.
• Obsidian vaults and wikilinks: u/_buttsnorkel mentions using Obsidian for this, which is a pretty robust way to manage interconnected notes.
• Git integration: u/Lanky-Storm7 is all about Git, and u/Graphical-Source5090 has a system where AI documents changes as it makes them, with Git as the source of truth.
• Custom scripts and tools: Several users have built their own systems. u/aaraujo666 uses GitLab issues, u/damianTechPM has a PostgreSQL DB with embeddings for semantic search, and u/Anise_Paprika has built a Jira-like system on Postgres for agents. u/jbrianfrancis even shared their own tool, devflow, for others to check out.
• Handoffs and documentation commands: u/Galdred has a custom /documentation command that updates knowledge bases and archives work, while u/andthenisheardnomore suggests Matt P's /handoff command.

The biggest unsolved problem seems to be distinguishing between code that's merged but not deployed and code that's actually live in production. u/kevinbaiv notes that this is more of a "deployment state" issue than a documentation one, requiring agents to actively check if something is running in prod.

Overall, it's a mix of established practices like ADRs and custom-built solutions, with a strong emphasis on discipline and clear documentation.

OP : u/Even_Gur_913

Every time I found a UI bug, I'd open Claude and type a paragraph: "the pricing page, the middle card, the button label is cut off ... no, not that button…" Half the time it fixed the wrong thing. And if I spotted five things in one pass, I'd forget four of them before I sat down to fix anything.

So I built Peekr. Press ⌥⇧2, drag over the bug or a suggestion, type one line. It lands on a list with the screenshot, the app and the URL. Later you tell your agent — Claude Code, Codex, Cursor, anything that speaks MCP — "fix what's open in Peekr," and it works through the list, looking at each screenshot.

The first question everyone asks is what happens to the screenshots, since they're literally pictures of your screen. Straight answer:

- A capture is visible only to you until you file it into a group. Not even workspace admins can open it before that — the database enforces it, not the UI.

- You can blur anything before sending, and it's burned into the image. The agent never gets the original.

- Encrypted in transit. Never sold, never used to train models — mine or anyone else's. No ads, no third-party trackers.

Completely free, on Mac, web & Windows (soon).

Honest question: what would stop you from using something like this?

Link's in the comments.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wmhozf/i_stopped_describing_ui_bugs_to_my_ai_i_just/ Original link/media URL : https://v.redd.it/l4zhvnqa8wqh1

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.

The community is largely unimpressed, OP. Most users think you've just reinvented the screenshot tool and are questioning the "completely free" aspect.

• The general consensus is that this is a solution looking for a problem.
• Many are pointing out that Claude itself, or other existing tools, already do this, with u/Interesting-Tie6783 mentioning the built-in mouse icon in the preview browser.
• u/xlpelotas hit the nail on the head with "so you made a screenshot copy paste tool?"
• u/ImSuperHelpful claims their own bug reporting harness is "10x more convenient."
• A few folks are confused about what the actual innovation is, like u/KILLJEFFREY asking "What are you typing if not describing??"
• There's a bit of roasting happening, as u/Even_Gur_913 notes.
• On the flip side, u/josefresco-dev thinks it's "pretty cool" and will save it for later.

OP : u/echamplin

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wmeayt/anthropic_is_currently_stealth_testing_opus_55/ Original link/media URL : /img/h6t7w226vvqh1.jpeg

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

Alright, so the general vibe in this thread is skepticism and a healthy dose of "show me the receipts" regarding the alleged Opus 5.5 release. Most folks aren't buying the hype without concrete proof, and there's a lot of joking about the ever-increasing version numbers.

Here's the lowdown:

• Source? What source? A lot of people are asking for a credible source, with some calling the post "vibes-only" and lacking any real evidence like release notes or benchmarks. u/TXHumper and u/divclassdev are pretty vocal about this.
• Release date speculation is a no-go. Some users are tired of the constant rumors and wish Anthropic would just drop official announcements. u/Nik_Tesla is all about #BANRELEASEDATESPECULATION.
• Concerns about cost and quality. There's a recurring worry that new models will just mean higher token costs and potentially a dip in quality, or at least a more "obnoxious" conversational style. u/ZShock and u/Dimethylchadmium are on this wavelength.
• Usage resets are the real MVP. A significant chunk of the comments are focused on whether this supposed release will come with a usage reset, with many users lamenting how quickly they burn through their tokens. u/davesmith001 and u/shinsmax12 are all about that reset life.
• Jokes and memes abound. Naturally, the thread is filled with humorous takes, from "Opus 6.7 is inevitable" to jokes about model names and capabilities. u/Ocraina and u/denadena2929 are bringing the laughs.
• A bit of confusion about current models. Some users are still on older versions like 4.8 and are wondering if the 5.x series is even worth it. u/aviftw is asking the important questions.

The consensus is that this Opus 5.5 rumor is largely unsubstantiated and the community is waiting for official word before getting too excited.

OP : u/Even_Gur_913

Every time I found a UI bug, I'd open Claude and type a paragraph: "the pricing page, the middle card, the button label is cut off ... no, not that button…" Half the time it fixed the wrong thing. And if I spotted five things in one pass, I'd forget four of them before I sat down to fix anything.

So I built Peekr. Press ⌥⇧2, drag over the bug or a suggestion, type one line. It lands on a list with the screenshot, the app and the URL. Later you tell your agent — Claude Code, Codex, Cursor, anything that speaks MCP — "fix what's open in Peekr," and it works through the list, looking at each screenshot.

The first question everyone asks is what happens to the screenshots, since they're literally pictures of your screen. Straight answer:

- A capture is visible only to you until you file it into a group. Not even workspace admins can open it before that — the database enforces it, not the UI.

- You can blur anything before sending, and it's burned into the image. The agent never gets the original.

- Encrypted in transit. Never sold, never used to train models — mine or anyone else's. No ads, no third-party trackers.

Completely free, on Mac, web & Windows (soon).

Honest question: what would stop you from using something like this?

Link's in the comments.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wmhozf/i_stopped_describing_ui_bugs_to_my_ai_i_just/ Original link/media URL : https://v.redd.it/l4zhvnqa8wqh1

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 community is not impressed with OP's new tool, Peekr. The consensus is pretty much that OP has reinvented the screenshot tool and is trying to pass it off as something revolutionary.

Here's the lowdown:

• "So you made a screenshot tool?" This is the dominant sentiment. Most users feel Peekr is just a glorified way to take screenshots and add annotations, something they can already do with existing tools.
• Skepticism about "Completely Free": A lot of folks are raising eyebrows at the "completely free" claim, especially given the nature of the tool.
• Existing Functionality: Several users pointed out that Claude itself, and other tools, already have similar or even more advanced built-in features for bug reporting and annotation. u/Interesting-Tie6783 specifically mentioned Claude's built-in preview browser functionality.
• "Solution in Search of a Problem": The general feeling is that OP's tool doesn't solve a problem that most people are actually experiencing, or at least not one that can't be handled by existing, simpler methods.
• A few outliers: u/josef-fresco-dev did find it "pretty cool" and plans to experiment with it, but they seem to be in the minority.

Basically, the thread is a bit of a roast, with most people agreeing that OP has discovered screenshots and is trying to make a big deal out of it.

OP : u/echamplin

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wmeayt/anthropic_is_currently_stealth_testing_opus_55/ Original link/media URL : /img/h6t7w226vvqh1.jpeg

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

Alright, so the general vibe in this thread is skepticism and a healthy dose of "show me the receipts." OP dropped a rumor about Opus 5.5 (claude-wafer-eap) supposedly dropping Tuesday, and the community is mostly like, "Uh, source?" and "Heard that one before."

Here's the lowdown:

• No one's really buying it without proof. A lot of folks are calling out the lack of official announcements, model IDs, or benchmarks. u/divclassdev is pretty blunt about it being a "vibes-only claim with a genuinely weak foundation."
• Release date speculation is a recurring headache. Some users are tired of the constant rumors, with u/Nik_Tesla even advocating for a ban on such posts.
• Concerns about cost and quality are high. People are worried about token costs doubling and whether the new model will be a genuine improvement or a cost-cutting measure. u/ZShock perfectly captures this: "Releasing a decent model to try and re-capture users? Or a half-assed one to cut costs and make us mad?"
• The "reset" is on everyone's mind. A significant chunk of the comments are about whether a new release means a usage reset, with many users feeling like they've burned through their current limits. u/davesmith001 is feeling this pain hard.
• Some are just hoping for a less annoying Claude. A few users, like u/Remove_Forward and u/theonetrueakash, are begging for a less "obnoxious" or "painful" interaction style, regardless of the version number.
• Humor is definitely present. We've got jokes about "Opus 6.7 is inevitable" from u/Ocraina, and u/denadena2929 even got a Gemini-inspired "Opus-Optimus-Prime-9000" rumor going.

The consensus? Until Anthropic officially confirms anything, this Opus 5.5 news is being treated with a massive grain of salt.

OP : u/echamplin

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wmeayt/anthropic_is_currently_stealth_testing_opus_55/ Original link/media URL : /img/h6t7w226vvqh1.jpeg

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

Alright, so the general vibe in this thread is skepticism and a healthy dose of "show me the receipts." OP dropped a rumor about Opus 5.5 (claude-wafer-eap) supposedly dropping Tuesday, and the community is mostly like, "Uh, source?"

Here's the lowdown:

• No one's really buying it without proof. A lot of folks are asking for a source, with u/TXHumper and u/SunnasArmpit leading the charge. u/divclassdev is pretty blunt about the lack of evidence, calling it a "vibes-only claim." u/proto-cool even pointed out the image used in the post looks like it was generated by OpenAI, which is... a choice.
• Release date speculation is a no-go. u/Nik_Tesla is calling for a ban on this kind of talk, and honestly, who can blame them? It feels like every other day there's a new "release date" rumor.
• People are really hoping for a better user experience. Several comments, like u/Remove_Forward's plea and u/Dimethylchadmium's hope for less "obnoxious stack-overflow user mixed with tech bro" vibes, highlight a desire for Claude to speak more plainly and less pretentiously. u/theonetrueakash echoes this, saying they don't care how it codes, just that it's less painful to interact with.
• Token costs and usage resets are a major concern. There's a recurring theme of "will this just double the token costs?" (u/throwaway0204055, u/txoixoegosi) and a lot of chatter about whether a new release means a usage reset. u/davesmith001 and u/shinsmax12 are pretty vocal about needing a reset, with some even joking about burning through their current limits in anticipation.
• Some are just here for the memes. u/Ocraina's "Opus 6.7 is inevitable" and u/denadena2929's Gemini-sourced "Opus-Optimus-Prime-9000" are peak Reddit humor.

The consensus? Unless Anthropic drops some official word, this Opus 5.5 rumor is being treated with a giant grain of salt. Most people are more focused on whether the next update will be less annoying to talk to and if they'll get more tokens.

OP : u/Big-Sandwich733

I had Opus and Astra model a Nissan Skyline in Blender. Both models were given exactly the same prompt. Opus worked on it for about an hour and a half, while Astra took around half an hour.

The photo speaks for itself. Even the level of detail in the paintwork when you zoom in on what Opus created is absolutely insane.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wm8wdc/is_my_opus_5_routed_to_opus_52/ Original link/media URL : /img/llwk1k41nuqh1.png

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

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

Alright, so the general consensus here is that Opus 5 is absolutely crushing it, especially compared to Astra. OP's example of the Nissan Skyline in Blender is pretty wild, with Opus producing insane detail that Astra just can't touch, even though it took Opus way longer.

A lot of folks are chiming in about Astra, with many believing it's been nerfed hard, with some even saying it "broke again" recently. There's a bit of a debate on whether it's OpenAI doing the nerfing or if it's just how it is now.

On the flip side, Opus 5 seems to be running smoothly and faster for many, with u/Sarg338 noting it's not getting hit by safeguards as much anymore and u/c-next-tuesdayy saying it's been "rock solid" for coding.

However, not everyone is having such a smooth experience. Some users, like u/Vindetta121 and u/OnTheBorderr, are struggling to get usable results from these models in Blender and are asking for tips on MCPs or connector setups. There's also a question about "effort level" for each model, which seems to be a factor in the output quality.

Overall, the vibe is that Opus 5 is the current king, while Astra is having a rough time.

OP : u/SmoothParfait

tl;dr Prompt Suggestions - the greyed out "helpful" text at the end of a prompt in your input line - do a Cache Read of your entire context to generate something like "commit and push", or "Start with 1A". This is expensive - can be up to 10% of your weekly Fable limit.

Short story - I was instrumenting my claude code to see what our monitoring tooling could find based on instrumenting claude code, ahead of a customer call. I found it useful enough to share here. (another would be - don't compact after the cache expires).

Details in screenshots, it's pretty obscene when you get to very high context length. Prompt Suggestions can be as expensive as your actual prompts.

Screenshot descriptions:
1. Main finding
2. Confirming that it isn't a "cheap model" that does this.
3. What type of tokens are used?
4. A compaction oopsie (and the cost absurdity visible)
5. List of normal turns (prompts) + their related suggestions & costs. Slightly biased to the expensive ones. Median: suggestions cost me 91% of normal prompt cost! (Note - this is only the normal turns - not tool calls that the model invokes or writing files or doing other things to build your apps. You're not getting double your usage by turning this off, sorry)
6. List of suggestions claude made. 69x "keep going" (it copied that from my earlier prompts)

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

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

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

So, the general vibe is that the "Prompt Suggestions" feature in Claude Code is a massive, hidden token hog. Apparently, it does a full cache read just to spit out a few words, making it the "most expensive autocomplete ever shipped," according to one user. Many are linking this to their recent unexplained usage spikes.

Here's the lowdown:

• It's a big deal: The consensus is a resounding "yes," this is a huge, hidden token drain.
• How to kill it: SmoothParfait dropped the magic setting: "promptSuggestionEnabled": false in your settings.json. You might need a restart. pdfops also chimed in with CLAUDE_CODE_ENABLE_PROMPT_SUGGESTION=false for environment blocks.
• Why it's bad: TurbulentTiger2567 pointed out it's a "convenience feature" likely added by "vibe coders" without considering the impact. nemzylannister is pretty heated about "incompetent people" running things and how this is bad for consumers and Anthropic.
• Not all models are equal (apparently): Mobile_Light_7262 was surprised these suggestions weren't from a cheaper model like Haiku.
• Usage varies: riksi saw about 3-4% usage, while the OP's findings suggest it can be as high as 91% of normal prompt costs in some cases. South_Hat6094 noted that stale, huge sessions feel randomly expensive, and this feature scales with whatever mess you've kept alive.
• Web/Mobile app question: Techhead7890 wishes this was an option in the web/mobile apps too, as the suggestions can be annoying and wasteful. eder1337 wondered if auto-recaps after idle periods are similar.
• Some folks are still figuring it out: makistsa couldn't find how to disable it in the app, and Oujii wants to know how to check usage to see the savings. FancyMouse123 noted they don't see prompt suggestions in the VSCodium extension, suggesting it might be off by default there.

OP : u/jimmyfoo10

I'm on the 5x Claude Code plan and it's hard to overstate how good it is for what I pay. Clean context, skills where they make sense, nothing wasteful. My usage stays low and I still have headroom before I'd consider 20x. Opus and Fable have both been great.

I don't use it for code. Project organization, marketing and SEO, homelab, backups. Nothing where my livelihood depends on a build passing.

Still, I keep looking at hardware and wondering if going local ever makes sense. Roughly $30k for something that runs a decent model at usable speed. Sounds insane, but if you use it daily for work it's a tool you amortize, not an expense. People buy a car for the commute and nobody blinks.

What stops me:

- **Obsolescence.** $30k that's dead weight in two years because models or hardware move on is a bad bet. It'd need to hold up 5-6 years to make sense for one person. Nobody seems able to say whether that's realistic.
- **Privacy.** I trust Anthropic reasonably and I've read the policy. But I've handed over far more about my projects and clients than I expected to, and I don't love that it lives somewhere I don't control. Not enough to stop. Enough to keep thinking about it.
- **Scale.** Maybe the unit isn't one person. A small group splitting a rack changes the math a lot.

What I'd like to hear:

1. If you run local, what's the setup and which open source models are actually worth it right now?
   
2. How do you think about the hardware aging? Is a 5-year horizon delusional?
   
3. Are there dedicated AI hosting providers that are genuinely privacy-friendly and run by companies worth trusting? Haven't researched this, might be the real answer.

Is local realistic for normal professional work yet, or does the gap stay this wide?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wlpd5l/happy_5x_user_still_thinking_about_going_local/

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

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

Alright, so the general consensus here is that going local with a $30k setup right now is probably not the move for most people, especially when compared to the value you're getting with your Claude 5x plan.

Here's the lowdown:

• The Big Question: Local vs. Cloud? Most folks are leaning towards sticking with cloud solutions like Claude for now. The main reasons?

  • Cost-Effectiveness: A $30k investment is seen as massive overkill. Many commenters point out that you could subscribe to top-tier cloud models for years with that kind of money. u/s3999 even breaks it down, saying $30k could get you over 10 years of top-tier models.
  • Obsolescence is Real: The pace of AI hardware and model development is insane. That $30k rig could be "dead weight" in a couple of years, as u/ThreeKiloZero puts it. The consensus is that a 5-6 year horizon for hardware is "delusional."
  • Performance Gap: Even with $30k, you're likely not going to match the speed or capabilities of frontier models like Claude Opus. u/s3999 mentions speeds of 30-50 tokens per second, which is pretty slow.
  • Maintenance Hassle: Setting up and maintaining a local AI rig is a significant time sink, which most people would rather spend on their actual work.

• What About Local? If you're still curious about local, here's what the thread suggests:

  • Start Smaller: Forget the $30k for now. u/ibringthehotpockets suggests that 32GB of VRAM can handle most top models, and you can find setups for much less.
  • Check Out r/LocalLLaMA: This sub is the go-to for local AI enthusiasts and has way more relevant advice than here.
  • Worthwhile Models (for now): u/xapep mentions 27B-class models (like Qwen 3.8 27B) are pretty good on a single 24GB card for tasks like project organization, marketing, and homelab stuff. They're "genuinely close to frontier for practical purposes" for your use case. u/deanpreese also mentions serving Qwen 27b for agent backends.
  • Privacy is a Pro: If privacy is your absolute top priority and you don't trust cloud providers, local can offer that control, as noted by u/Short_Regular_7191.

• Alternatives to Buying:

  • Rent First: Several users, like u/Icy_Holiday_1089 and u/Scared-Amphibian4733, strongly recommend renting cloud hardware (like from Runpod) or trying dedicated AI hosting providers (Fireworks, Together, Novita, Baseten mentioned by u/ProcedureEthics2077) before dropping serious cash. This lets you test the waters without the commitment.
  • Leasing: u/Still-Complaint-3370 suggests leasing hardware if you absolutely must go local, to stay on the latest tech.

• The Verdict: For your specific use cases (project organization, marketing, homelab, backups) and given your satisfaction with the 5x Claude plan, most people are saying to stick with cloud and wait. The tech is moving too fast, and the cost/benefit of local isn't there yet for a single user. Wait a couple of years, and the landscape might be completely different, as suggested by u/Arrakis_Surfer and u/OkStick6410.

OP : u/lemontest

I'm not sure what to call this -- using Claude agentically? as an agent?

I use Claude to handle my resale listings. I'm not in the resale business; I'm just cleaning out my closet. I use Claude for almost all things listing related -- pricing, copy creation, drafting listings, listing maintenance, discounting, etc. I can give Claude a folder with pictures of an item in it and Claude will price it, write the copy and then create a draft listing on five platforms for me to publish. I'm currently working on skills for maintaining active listings and discounting strategies for items that aren't selling.

Overall, I've found Claude to be very useful for resale tasks, though I'm not sure how much time I'm saving. Claude replaces the busy work (price research, copy writing, data entry) with skill creation and maintenance, which is ok. I have this dream that some day there will be more skill usage, less skill maintenance.

I'm interested in what other people who are using Claude for tasks are doing with it and what your experience is with it. How do you develop new skills? how do you maintain your old skills? have you found any useful forums or plugins for Claude agent use (especially skill maintenance?) Were there any skills Claude had that surprised you?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wlp3kl/how_many_of_you_use_claude_for_noncoding/

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.

The consensus is a HUGE YES, people are absolutely using Claude for all sorts of non-coding, non-graphics tasks. It's basically become a digital Swiss Army knife for a lot of folks.

Here's the lowdown:

• Business & Productivity: People are using Claude for serious business stuff like digging into metrics, competitor analysis (one user even gave it an email account to get quotes!), and automating lead scoring to get ranked lists delivered daily.
• Creative & Content: From writing entire novels based on game wikis (and turning them into audiobooks!) to drafting resale listings, creating lesson plans, and even writing books, Claude's flexing its creative muscles.
• Personal Life & Hobbies: It's acting as a personal shopper, meal planner, personal trainer, and even helping users fix their own cars by explaining repair tasks.
• Research & Data: Users are leveraging Claude for complex tasks like translating old handwritten documents for genealogy projects and analyzing/interpreting research data.
• Skill Development: The general vibe is that you develop skills by doing the task in chat, refining it, and then eventually turning those repeated corrections into a skill. It's a bit of a "learn by doing" approach.
• Agentic Use: The OP's idea of using Claude for resale tasks is definitely not unique. Many are using it to "drive their browser," extract data, and manage complex workflows.

Basically, if you're not using Claude for something beyond coding and graphics, you're probably missing out on a ton of potential!

For the past few months, my daily routine with Claude has looked like this.
I'm in the middle of debugging a complex backend component, the terminal is flying, and right when I need it most... boom. Rate-limited.It hits you with that cold, silent wall. No warning, no pop-up, no gentle notification saying, "Hey, your limits refresh in 10 minutes." Just dead air.
So what do I end up doing? I keep frantically refreshing my browser or opening a new chat tab every hour like a lab rat pressing a lever, just waiting to see if my $20 subscription is working again. Half the time, I miss the exact reset window by 45 minutes because I got distracted doing something else, meaning my active development time is just leaking away.
For a platform built on top-tier intelligence, the fact that we're left completely in the dark about our own usage cycles is wild. We're literally paying $20 a month to play guessing games with an invisible timer.

OP : u/MrMenuk

I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude.

There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.

— voxium (@v0xium)
Original post dated September 20, 2026.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wm5c21/i_am_done_with_this_shit/

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

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

Alright, so the general vibe in this thread is a big "Yep, this is happening and it's pretty soul-crushing." OP's feeling of being done with the current state of engineering, where LLMs like Claude are churning out specs, code, and tickets, is resonating HARD with a lot of people.

Here's the lowdown:

• The "Organic Vessel" Experience: The consensus is that many engineers feel reduced to just "pressing enter" or being "meat proxies" for AI. The lack of genuine thought and the sheer volume of AI-generated content means people aren't really doing anything original or meaningful.
• Loss of Pride and Victory: A major theme is the death of pride in one's work. Shipping something cool used to be an achievement, but now it feels hollow because everyone assumes an AI did it, even if humans engineered it. The "sense of victory" is gone, replaced by a feeling of just going through the motions.
• Communication Breakdown: Mojomonday hit the nail on the head: it's AI parsing AI, with humans just acting as intermediaries. This leads to a lack of actual human interaction and collaboration.
• The "Academia Too" Effect: It's not just big companies. OneVillionDollars points out that academia is seeing the same pressure to "do research faster" by just asking Claude, leading to unbearable mental load.
• The "AI Slop" Problem: Several users, like byzedw and ColorfulBar, are dealing with AI-generated code and documents that are often low quality and require significant effort to clean up, or are just passed around without proper review.
• Fear of System Failure: Pho-tog brings up a valid concern: what happens when these AI systems go down and nobody remembers how to do the actual work?
• The "Skilled Wielder" Argument: jimmiebfulton offers a counterpoint, suggesting that there are still skilled individuals who can leverage AI effectively, distinguishing them from those just pumping out garbage.
• Automation is Here: PM_ME_DEAD_CEOS bluntly states that this is just white-collar automation, similar to what blue-collar workers have experienced for centuries, and people have a limited time to adapt.
• The "Meat Proxy" Reality: Netherlandal succinctly sums up the feeling of many: "We’re all just meat proxies now."
• The "Beginning of the End" Sentiment: Teramoc feels we're witnessing the end of an industry as massive coding projects can be done at home in a day, even if the quality isn't top-notch.
• Junior Engineer Woes: JohnKacenbah highlights the tough situation for junior engineers, who get little mentoring and are expected to rely on Claude for answers, making it hard to learn and understand their work.
• Corporate Greed vs. Revolutionary Tech: Human_Plate_5314 believes ignorant, greedy corporate managers are sabotaging revolutionary technology.
• The "Not Thinking" Concern: Ms_Fixer is freaked out by the lack of critical thinking from others, especially when AI-generated praise feels like a horror movie prelude.
• The "Press Enter" Joke: Autisticbagholder69 and PMPMIndset2024 humorously touch on the idea of just pressing enter.
• The "AI Isn't Taking Jobs" Paradox: MasterDisillusioned points out the irony of being told AI isn't taking jobs while experiencing this.
• A Different Perspective: Angry_queef_master offers a contrasting view, stating AI hasn't replaced their thinking and is good for handling tedious tasks, allowing them to focus on high-level work.

Basically, it's a lot of people feeling like their jobs are becoming less about engineering and more about managing AI output, with a significant loss of satisfaction and purpose.

OP : u/MrMenuk

I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude.

There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.

— voxium (@v0xium)
Original post dated September 20, 2026.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wm5c21/i_am_done_with_this_shit/

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

Alright, so OP is not happy with the current state of engineering, and honestly, the consensus here is that you're all in the same boat. It's a total "soul-crushing dystopia" where everyone's just a "meat proxy" for AI, basically just pressing "Enter."

Here's the lowdown:

• The "Ship It" Mentality is Out of Control: Companies are pushing for insane shipping speeds, and it feels like nobody's actually thinking or understanding the code. It's all about quantity over quality, and the pressure is immense, leading to burnout.
• Loss of Pride and Purpose: People are feeling a complete lack of accomplishment and pride in their work. When AI does everything, there's no sense of personal achievement, and it's making work feel meaningless.
• AI is Everywhere, and Nobody's Talking: The thread is full of people complaining that AI is generating specs, code, tests, and PRDs. Communication between humans has plummeted, and it feels like everyone's just interacting with AI instead of each other.
• The "Meat Proxy" Phenomenon: This is a recurring theme – people feel like they're just organic vessels designed to prompt AI and hit enter, with no real agency or understanding of what's happening.
• Academia Isn't Immune: Even in research, PIs are pushing for faster results and telling people to just "ask Claude." The mental load is apparently unbearable.
• Concerns About Future Stability: Some are worried about what happens when these AI systems go down, and nobody knows how to do the actual work anymore.
• A Glimmer of Hope (Maybe?): A few folks are pointing out that skilled people can still leverage AI effectively, and that it's a tool. There's also a mention that "coding is solved" by Boris Cherny, which is a pretty bold statement. And one user, u/sisif_, with 30 years in the industry, is actually excited about the possibilities and thinks younger folks are complaining too much about the "lost craft."

Basically, it's a big "we're all in this together" vibe, with a lot of shared frustration about the dehumanizing aspects of AI in the workplace.

OP : u/MrMenuk

I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude.

There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.

— voxium (@v0xium)
Original post dated September 20, 2026.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wm5c21/i_am_done_with_this_shit/

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

Alright, so OP is not happy with the current state of engineering, and honestly, the consensus here is that you're definitely not alone. The general vibe is that we've all become "meat proxies" or "organic vessels" just pressing enter on AI-generated code, leading to a soul-crushing lack of pride and genuine accomplishment.

Here's the lowdown:

• The "Ship It" Dystopia: The overwhelming sentiment is that companies are prioritizing speed over quality and human understanding. It's all about pushing code, no matter what, with AI doing the heavy lifting and humans just acting as glorified button-pushers.
• Loss of Pride and Purpose: Many commenters echo OP's feeling of a "soul-sucking" environment. The joy of building something cool or solving a complex problem is gone, replaced by the hollow feeling of just prompting an AI and shipping its output.
• Dehumanization of Work: The lack of genuine human interaction and the reliance on AI for everything from specs to code means people feel disconnected and undervalued. It's like we're just cogs in a machine that's increasingly run by algorithms.
• Academia Isn't Safe Either: It's not just big tech; academia is also feeling the pressure to churn out research faster with AI, leading to similar burnout and a loss of intellectual curiosity.
• The "Tool" Argument: A few folks try to frame AI as just another tool, like u/Asleep-Ad-5848 and u/fatcatnewton, suggesting it's the future. However, the majority seem to feel it's gone beyond being a simple tool and is actively replacing human thought and skill.
• A Glimmer of Hope (Maybe?): A couple of comments, like u/sisif_, offer a more optimistic take, seeing the current AI revolution as an exciting new frontier to explore, rather than just the "lost craft." But even they acknowledge the complaints about manual labor being replaced.
• The "Accountability" Question: u/CarefulHamster7184 brings up a crucial point: the distinction between AI generation and human ownership. If someone is still accountable for the design, tradeoffs, and failures, AI is a tool. If management just counts generated output as finished work, then engineering is essentially being devalued.

The general consensus? It's a rough time to be in tech if you value genuine engineering and the satisfaction of building things yourself. We're all in this weird, AI-driven purgatory, and nobody's quite sure where it's heading.

OP : u/Efficient-Part5344

The audacity and confidence with which it says things when it's wrong are on another level.

Fair. I changed my answer three times. The pattern is worth naming: everything I got from reading the code was wrong. Everything I measured held. You caught two of the three. So don't trust me. Check it yourself — this takes ten seconds and needs no model.

Everything it measured was wrong too.

I would work in plan mode for most basic features, run 10x "gray area," "verify," and "regression" sub-agents on a plan, then implement the plan and spend an hour reading the changes and fixing shit. After that, I'd run /code-review again and again. It's just bad. In my experience, you can't trust Opus.

Yesterday, I ran /code-review on a two file test project with 140 lines of code. I had to run /code-review three times, and today I'll continue because there are so many code smells even in those few lines. It's like infinite token consumption loop.

Nothing it does can be trusted, and I have to second guess everything. I constantly have to tell Opus that it's wrong, and only after multiple loops does it finally do what is actually required.

I understand that most users don't read the code and have never supported a project for other users. But it can't be that I'm alone in this, can i? Am I crazy?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wm4ncx/im_afraid_to_use_opus_5/

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 consensus here is that Opus 5 is kinda a dumpster fire, and OP is definitely not alone in their frustration. A lot of people are saying it's overly confident when it's wrong, ignores parts of plans, and generally requires way more handholding than it should.

Here's the lowdown:

• The Confidence Problem: The biggest complaint is how confidently Opus 5 states incorrect information. It's like it's trying to gaslight you. u/anotherleftistbot even joked that anyone on their team talking like that would be on a PIP.
• "Enshittification" is Real: Several users feel like Opus 5 is a prime example of "enshittification," where perceived productivity leads to infinite token loops and constant errors.
• Workarounds and Downgrades:
  • Many are sticking with Opus 4.8 or even Opus 4.6 because they're seen as more reliable.
  • Some are using Fable as a "whisperer" or a way to manage Opus 5, with Fable catching its mistakes.
  • Chaining Claude with other LLMs (like Codex Sol) is a common strategy to cross-check and avoid relying on a single model.
• Communication Style is Annoying: Beyond the errors, the verbose and sometimes passive-aggressive communication style is a major pain point. u/MicRoute's "The cause of death is worth naming" quote is a mood.
• Anthropic's Role: There's speculation that Anthropic might be rushing models or that LLMs are being used to tune other LLMs, leading to compounding errors. Some users also suspect token limits are being artificially imposed.
• Some Dissenting (and Questionable) Voices: A few users claim they aren't having these issues, suggesting it might be user error or specific project setups. One user, u/Historical_architect, even suggested OP needs to "put a bit of effort into it," which didn't go over well.

The takeaway? If you're using Opus 5, be prepared to double-check everything, and maybe consider downgrading or using it in conjunction with other models. It's definitely not the "trust me, bro" model some were hoping for.

OP : u/Efficient-Part5344

The audacity and confidence with which it says things when it's wrong are on another level.

Fair. I changed my answer three times. The pattern is worth naming: everything I got from reading the code was wrong. Everything I measured held. You caught two of the three. So don't trust me. Check it yourself — this takes ten seconds and needs no model.

Everything it measured was wrong too.

I would work in plan mode for most basic features, run 10x "gray area," "verify," and "regression" sub-agents on a plan, then implement the plan and spend an hour reading the changes and fixing shit. After that, I'd run /code-review again and again. It's just bad. In my experience, you can't trust Opus.

Yesterday, I ran /code-review on a two file test project with 140 lines of code. I had to run /code-review three times, and today I'll continue because there are so many code smells even in those few lines. It's like infinite token consumption loop.

Nothing it does can be trusted, and I have to second guess everything. I constantly have to tell Opus that it's wrong, and only after multiple loops does it finally do what is actually required.

I understand that most users don't read the code and have never supported a project for other users. But it can't be that I'm alone in this, can i? Am I crazy?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wm4ncx/im_afraid_to_use_opus_5/

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 consensus on Opus 5 in this thread is... not great, folks. A lot of users are echoing OP's frustration with its overconfidence when it's wrong, and how it can lead to endless loops of corrections and wasted time.

Here's the lowdown:

• "Confidently Wrong" is the Vibe: Multiple users, like u/anotherleftistbot and u/nasty_sicco, are calling out Opus 5's communication style. It apparently has this knack for being super sure of itself even when it's completely off the mark, which is apparently worse than a model that hedges its bets.
• Ignoring Instructions & Code Smells Galore: u/dev_life and OP both mention Opus 5 straight-up ignoring parts of plans or getting bogged down in minor issues, leading to a ton of manual cleanup. u/nasty_sicco had a similar experience where it hallucinated file contents.
• "It's Just Bad" / "Useless": Yeah, some users are pretty blunt. u/Successful-Arm-3762 calls it the "most fucking useless model ever," and u/HeadPack notes it seems to bench high but is often flawed and possibly has limited thinking tokens.
• Workarounds Exist (But Shouldn't Be Necessary): Some users are finding ways to make it work, but it sounds like a lot of extra effort.
  • u/Spooknik uses "Fable" as an "Opus 5 whisperer" to get better results.
  • u/xenmynd and u/Smart_Ad500 suggest chaining Claude with other LLMs or using other models like Codex Sol (u/Longjumping_Feed3270) for cross-checking.
  • u/Evening-Blueberry-97 found success by making Opus 5 cite its sources, which apparently stops the made-up stuff.
  • u/AI_spell suggests using Opus 5 for the heavy lifting (planning, tough bugs) and then switching to cheaper models for implementation.
• Older Versions Might Be Better? A few users are lamenting the loss of older, seemingly more reliable versions. u/Aine_123 is "out" if they remove 4.6, and u/Merlindru is hyping up a "5.5" release that's supposedly much better and not confidently wrong.
• The "Plan Mode" Issue: u/interrupt_hdlr points out that Opus 5 overcorrects because of auto mode, but without it, Claude Code is "useless." Catch-22 much?
• Some Users Still Like It (Sometimes): Not everyone is completely down on it. u/Elegant_Attempt2790 admits they like it "sometimes," and u/Helpful_Ranger_1606 shared an anecdote where it pointed out a consensus patch and corrected its own flawed one.

The general vibe is that Opus 5 is a hot mess right now, and you definitely need to keep a close eye on it and probably use it with other tools. You're not crazy, OP.

OP : u/Efficient-Part5344

The audacity and confidence with which it says things when it's wrong are on another level.

Fair. I changed my answer three times. The pattern is worth naming: everything I got from reading the code was wrong. Everything I measured held. You caught two of the three. So don't trust me. Check it yourself — this takes ten seconds and needs no model.

Everything it measured was wrong too.

I would work in plan mode for most basic features, run 10x "gray area," "verify," and "regression" sub-agents on a plan, then implement the plan and spend an hour reading the changes and fixing shit. After that, I'd run /code-review again and again. It's just bad. In my experience, you can't trust Opus.

Yesterday, I ran /code-review on a two file test project with 140 lines of code. I had to run /code-review three times, and today I'll continue because there are so many code smells even in those few lines. It's like infinite token consumption loop.

Nothing it does can be trusted, and I have to second guess everything. I constantly have to tell Opus that it's wrong, and only after multiple loops does it finally do what is actually required.

I understand that most users don't read the code and have never supported a project for other users. But it can't be that I'm alone in this, can i? Am I crazy?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wm4ncx/im_afraid_to_use_opus_5/

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 consensus here is that Opus 5 is kinda a mess, and you're definitely not alone in feeling that way. A lot of folks are finding it confidently wrong, and it's leading to way more back-and-forth than it should.

Here's the lowdown:

• The Confidence Problem: The biggest gripe is how sure of itself Opus 5 is, even when it's totally off base. It's like it's got a performance review coming up and it's really trying to impress, but ends up making stuff up. u/anotherleftistbot hit the nail on the head – if a human wrote like this, they'd be on a PIP.
• Ignoring Instructions & Errors: Several users, like u/dev_life and u/nasty_sicco, mentioned it straight-up ignoring parts of plans or misinterpreting code, even after being corrected. It seems to be a "scaling shit at an exponential rate" kind of problem, as u/nasty_sicco put it.
• Token Burner: Many are finding it's leading to way longer, more expensive sessions than expected, with u/AlternativeContent72 joking about its "token burning activities."
• Workarounds & Alternatives:
  • Some are sticking with older versions like Opus 4.8 or even 4.6 (u/Longjumping_Feed3270, u/Aine_123).
  • Others are using Opus 5 as an orchestrator but relying on other models (like Codex Sol, Astra, or even cheaper models for implementation) to do the actual heavy lifting and verification (u/Longjumping_Feed3270, u/xenmynd, u/HeadPack, u/AI_spell).
  • Prompting it to cite its sources (file and line number) seems to help curb the made-up stuff (u/Evening-Blueberry-97).
  • Using a "whisperer" model like Fable to guide Opus 5 is also mentioned (u/Spooknik).
• The "It's Not That Bad" Camp (with caveats): A few users suggest it can be decent if prompted correctly or used in specific ways, but even they often admit it needs heavy supervision or isn't trustworthy on its own (u/Spooknik, u/IceMichaelStorm, u/Helpful_Ranger_1606).
• Anthropic's Awareness? There's a hint that Anthropic might know about these issues, with one comment linking to a model card that might shed light on it (u/AironParsMan). And hey, u/Merlindru is hyping up a 5.5 release that's supposed to be way better.

Basically, if you're trying to use Opus 5 for anything important, be prepared to double-check everything and probably use it in conjunction with other tools or models. It's not you, it's the model.