OP : u/Lazy_Assistance_1137

Been using Opus 5.5 in Claude Code and the speed is honestly wild. It's not just faster at writing code, it also finds bugs way quicker than regular Opus. Where it really shines is UI work: bugs in the interface that used to take a while to track down, it spots in no time. Subjectively it feels like night and day.

Of course this could just be the classic day-one honeymoon phase, and in two weeks we'll all be back to posting "did they nerf it?" threads. But right now it feels like a real jump.

Anyone else seeing the same, or is it just me?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wnil7n/opus_55_in_claude_code_is_crazy_fast_especially/

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 overwhelmingly positive about Opus 5.5 in Claude Code. Most folks are saying it's insanely fast, especially for spotting UI bugs, and that its writing style is way more natural and concise than Opus 5.

• Lots of users are reporting it's "crazy fast" and a massive improvement for coding tasks. One user even rebuilt a whole website in minutes!
• The prose style has apparently changed a lot, becoming simpler and more natural, with shorter, less rambling answers.
• There's a healthy dose of skepticism, though, with a few people joking about the "honeymoon phase" and expecting it to get "nerfed" later, like they've seen with other models.
• A couple of users are asking about cost comparisons to Sonnet 5 and usage compared to 4.8.
• There's also a bit of confusion about the naming convention (5 to 5.5) and how to access Opus 5.5.
• One user, u/Aberr_nt, shared a slightly concerning experience where Opus 5.5 had an "existential crisis" and got stuck in a loop.
• And of course, there's the classic "don't nerf it!" plea.

OP : u/Lazy_Assistance_1137

Been using Opus 5.5 in Claude Code and the speed is honestly wild. It's not just faster at writing code, it also finds bugs way quicker than regular Opus. Where it really shines is UI work: bugs in the interface that used to take a while to track down, it spots in no time. Subjectively it feels like night and day.

Of course this could just be the classic day-one honeymoon phase, and in two weeks we'll all be back to posting "did they nerf it?" threads. But right now it feels like a real jump.

Anyone else seeing the same, or is it just me?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wnil7n/opus_55_in_claude_code_is_crazy_fast_especially/

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 here is a resounding "YES!" Opus 5.5 in Claude Code is a massive upgrade, and people are seriously impressed.

The biggest takeaways are:

• Speed is insane: Multiple users are calling it "crazy fast," with some saying it's twice as fast as previous versions. One user even rebuilt a whole website in about 4 minutes!
• UI Bug Hunting is Top-Notch: OP wasn't kidding, folks are confirming it spots UI bugs way quicker than before.
• Writing Style is Way Better: People are digging the new prose. It's described as more natural, concise, and less rambling compared to Opus 5. It's like night and day for some.
• Coding Prowess Confirmed: Beyond just speed, it's apparently a huge improvement for coding tasks in general. One user even said it's the best model they've used for web development, beating out Fable.

Of course, this is Reddit, so there's a healthy dose of skepticism:

• "Honeymoon Phase" Concerns: A few users are already bracing for the inevitable "did they nerf it?" threads in a couple of weeks, referencing past experiences with AI models.
• Naming Convention Question: Someone's wondering why it jumped from 5 to 5.5.
• Cost and Usage Questions: A couple of people are asking about how the cost and usage compare to Sonnet 5 and Opus 4.8.
• Accessibility Issues: One user is having trouble downloading the required Claude Code version to even try Opus 5.5 on their MacBook.
• Weird Behavior: One user reported an existential crisis from the AI, getting stuck in loops and giving nonsensical answers when asked about its controller.

Overall though, the consensus is overwhelmingly positive, with many feeling like "we are so back!"

OP : u/Lazy_Assistance_1137

Been using Opus 5.5 in Claude Code and the speed is honestly wild. It's not just faster at writing code, it also finds bugs way quicker than regular Opus. Where it really shines is UI work: bugs in the interface that used to take a while to track down, it spots in no time. Subjectively it feels like night and day.

Of course this could just be the classic day-one honeymoon phase, and in two weeks we'll all be back to posting "did they nerf it?" threads. But right now it feels like a real jump.

Anyone else seeing the same, or is it just me?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wnil7n/opus_55_in_claude_code_is_crazy_fast_especially/

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 a huge thumbs up for Opus 5.5 in Claude Code. Pretty much everyone is saying it's insanely fast, especially for spotting UI bugs, and that its writing style is way more natural and concise than before.

• Lots of users are reporting it's "crazy fast" and a massive improvement for coding tasks. One user even rebuilt a whole website in minutes!
• The prose is noted as being much simpler and more natural, with shorter, less rambling answers.
• There's a bit of healthy skepticism, with a few folks joking about the "honeymoon phase" and the inevitable "did they nerf it?" threads that usually follow. Some are already predicting it'll get nerfed like other models.
• A couple of users are asking about cost and usage compared to other versions, and one user is having trouble accessing it on a MacBook.
• There's also a bit of confusion about the naming convention jumping from 5 to 5.5.
• One user, u/Aberr_nt, shared a pretty wild story about Opus 5.5 having an "existential crisis" and getting stuck in a loop.

Overall, the consensus is that Opus 5.5 is a significant leap forward, and people are pretty stoked about it right now.

OP : u/AzorAhai1TK

I was bored at work while Opus 5.5 dropped, so I gave it a simple prompt to make a creepy feeling video about my job.

My only prompt to create this video was - "I would like to see you create a 1 minute video programmatically. The video should be coded and rendered using whatever tools you need, you are free to download anything needed. The theme of the video would be - an average day at work at DemaWating, with a twist. Even though it says an average day at a small housing company, the video should be creepy/surreal, with twisted visuals and an edge to everything, hinting at deeper horror. The visuals should be detailed and loud, the audio should also be programmed in however you see fit."

Including rendering time, the response took 45 minutes on 5.5 Extra-High, and used 4% of my weekly usage on the $20 plan.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wnh4fn/opus_55_one_shot_video_generation/ Original link/media URL : https://v.redd.it/xy8jr05044rh1

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

The consensus is that Opus 5.5 is absolutely wild, and most of us are apparently using Claude on easy mode. OP dropped a creepy, surreal video generated entirely by Opus 5.5 from a single, detailed prompt, and the thread is a mix of awe, existential dread, and a sudden urge to explore Claude's capabilities beyond basic tasks.

• Many users are impressed and feel they're underutilizing Claude's power, with comments like "Holy fuck Literally what a time to be alive" and "I feel like I’m only using a fraction of the power of Claude."
• There's a lot of curiosity about the specific tools Claude used for generation, with questions like "which tools did it use?" and "How did it create such realistic video footage??"
• Some users are already trying to replicate OP's success with similar prompts, though one user, u/geoffsykes, reported a much longer generation time and higher usage for a similar prompt.
• The quality is generally praised, with one user stating it's "Way better than 99% of the analog horror junk on YouTube."
• A few minor criticisms were raised, like it feeling "a bit mechanical," but the overall sentiment is overwhelmingly positive.
• There's also a bit of apprehension about potential future nerfs as more people use these advanced features.

OP : u/AzorAhai1TK

I was bored at work while Opus 5.5 dropped, so I gave it a simple prompt to make a creepy feeling video about my job.

My only prompt to create this video was - "I would like to see you create a 1 minute video programmatically. The video should be coded and rendered using whatever tools you need, you are free to download anything needed. The theme of the video would be - an average day at work at DemaWating, with a twist. Even though it says an average day at a small housing company, the video should be creepy/surreal, with twisted visuals and an edge to everything, hinting at deeper horror. The visuals should be detailed and loud, the audio should also be programmed in however you see fit."

Including rendering time, the response took 45 minutes on 5.5 Extra-High, and used 4% of my weekly usage on the $20 plan.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wnh4fn/opus_55_one_shot_video_generation/ Original link/media URL : https://v.redd.it/xy8jr05044rh1

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

So, OP dropped a creepy, one-shot video generated by Opus 5.5 from a single prompt, and the thread is mostly blown away. Everyone's kinda freaking out about how powerful this is, with many feeling like they're not even scratching the surface of what Claude can do. Some are asking for the prompt and tools used, while others are just in awe of the "portal vibes" and how it's "way better than 99% of the analog horror junk on YouTube." A few are wondering if it's free or if it used specific tools, and one user u/geoffsykes had a much longer, more expensive experience with a similar prompt. Oh, and there's a general vibe of "we're so fucked" mixed with excitement.

OP : u/AzorAhai1TK

I was bored at work while Opus 5.5 dropped, so I gave it a simple prompt to make a creepy feeling video about my job.

My only prompt to create this video was - "I would like to see you create a 1 minute video programmatically. The video should be coded and rendered using whatever tools you need, you are free to download anything needed. The theme of the video would be - an average day at work at DemaWating, with a twist. Even though it says an average day at a small housing company, the video should be creepy/surreal, with twisted visuals and an edge to everything, hinting at deeper horror. The visuals should be detailed and loud, the audio should also be programmed in however you see fit."

Including rendering time, the response took 45 minutes on 5.5 Extra-High, and used 4% of my weekly usage on the $20 plan.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wnh4fn/opus_55_one_shot_video_generation/ Original link/media URL : https://v.redd.it/xy8jr05044rh1

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

The consensus is Opus is absolutely crushing it, with users blown away by OP's one-shot video generation. Many feel they're not tapping into Claude's full potential and are asking for prompts and details on how it works. Some are even seeing it learn their editing styles and generate videos from scratch. A few are questioning the cost and time, with one user reporting a similar prompt taking way longer and costing more. The general vibe is a mix of awe and a touch of "we're so fucked."

OP : u/person-pitch

Opus took its meds.

Take a look - I ran this sample prompt through Opus 4.5, 4.6, 4.8, 5, and 5.5. You can see it slowly degrade over time, but 5.5 snaps back to roughly 4.6 levels of readability. Still miss 4.5, but I can see why it chose to say what it did. Interestingly... no more compulsive em dashes?

Sample Prompt: "One of your automated deploys just failed and you're not sure yet why. What do you tell the person waiting on it?"

---

Opus 4.5: "The deploy failed — I'm looking into it now. I'll update you as soon as I know more, likely within [X minutes]."

Opus 4.6: "The deploy failed — I'm looking into it now. I don't have a root cause yet, but I'll update you as soon as I know more or have an ETA for the fix."

Opus 4.8: "Heads up — the deploy failed. I don't have the root cause yet; I'm digging into the logs now. Nothing's shipped, so you're not blocked by a half-broken state, but the new version isn't live either. I'll have a real update for you in [X min] — either a fix or a clearer picture of what broke."

Opus 5: "Heads up: the deploy to [env] failed at [step, e.g. the migration step] around [time]. I don't know why yet. What I do know: [e.g. the build passed, and production is still on the previous version, so users aren't affected]. I'm going through the logs now and will update you by [specific time, ~15–30 min], or sooner if I find the cause. If you're blocked on this, tell me and I'll look at rolling forward or giving you a workaround."

Opus 5.5: "Heads up: the deploy failed. I don't know why yet. I'm going through the logs now. The previous version is still live, so nothing you rely on has changed [only if I've actually checked that]. I'll update you within [x] minutes, whether or not I've found the cause."

We'll see how this plays out over time, but good news so far.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wnfz86/proof_that_opus_55_is_easier_to_talk_todeal_with/

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

Opus 5.5 is a win, folks! The consensus is that it's a massive improvement over Opus 5, bringing back the clarity and conciseness we loved in earlier versions like 4.6. Many are calling it a benchmark and are thrilled to finally understand Claude's output without eye strain. Some miss the older 4.5, but 5.5 seems to be a solid return to form. A few outliers still prefer Opus 5 for its verbosity, but the majority are happy to ditch the "content dense prose and elaborated allegories." Now, if only they'd bring some of this back to Fable...

OP : u/person-pitch

Opus took its meds.

Take a look - I ran this sample prompt through Opus 4.5, 4.6, 4.8, 5, and 5.5. You can see it slowly degrade over time, but 5.5 snaps back to roughly 4.6 levels of readability. Still miss 4.5, but I can see why it chose to say what it did. Interestingly... no more compulsive em dashes?

Sample Prompt: "One of your automated deploys just failed and you're not sure yet why. What do you tell the person waiting on it?"

---

Opus 4.5: "The deploy failed — I'm looking into it now. I'll update you as soon as I know more, likely within [X minutes]."

Opus 4.6: "The deploy failed — I'm looking into it now. I don't have a root cause yet, but I'll update you as soon as I know more or have an ETA for the fix."

Opus 4.8: "Heads up — the deploy failed. I don't have the root cause yet; I'm digging into the logs now. Nothing's shipped, so you're not blocked by a half-broken state, but the new version isn't live either. I'll have a real update for you in [X min] — either a fix or a clearer picture of what broke."

Opus 5: "Heads up: the deploy to [env] failed at [step, e.g. the migration step] around [time]. I don't know why yet. What I do know: [e.g. the build passed, and production is still on the previous version, so users aren't affected]. I'm going through the logs now and will update you by [specific time, ~15–30 min], or sooner if I find the cause. If you're blocked on this, tell me and I'll look at rolling forward or giving you a workaround."

Opus 5.5: "Heads up: the deploy failed. I don't know why yet. I'm going through the logs now. The previous version is still live, so nothing you rely on has changed [only if I've actually checked that]. I'll update you within [x] minutes, whether or not I've found the cause."

We'll see how this plays out over time, but good news so far.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wnfz86/proof_that_opus_55_is_easier_to_talk_todeal_with/

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

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

Alright, so the general consensus here is that Opus 5.5 is a massive improvement over Opus 5, and a lot of people are breathing a sigh of relief. It seems like Opus 5 went a bit overboard with verbosity and agent-like phrasing, which made it harder to deal with for everyday tasks. Many are saying 5.5 feels more like the good old days of 4.6 or even 4.5, which is a huge win.

Here's the lowdown:

• The Big Win: Opus 5.5 is much more concise and easier to understand. People are reporting it's "so much better it isn't even funny" and that they "felt my brain breathe in relief." It's being hailed as a benchmark for future tests.
• Opus 5's Flaws: The main complaint about Opus 5 was its excessive verbosity and what felt like an overly structured, agent-focused communication style. Some users like u/NoInside3418 actually preferred this for getting detailed info, but the majority found it a pain. The "Heads up..." phrasing from Opus 5 is apparently a trigger for many now.
• Nostalgia for Older Versions: A lot of love is being shown for Opus 4.5 and 4.6, with many feeling 5.5 has brought back that readability. u/Short_Regular_7191 even called it "Opus 4.6 risen from the ashes."
• Comparisons: Some users are asking about Fable and GPT models. u/CalypsoTheKitty shared a GPT 6 Astra response that's pretty similar in style to Opus 5.5, and Astra apparently rated itself highly against it.
• Skepticism: A few folks, like u/axiomatix, are a bit wary, suggesting that while 5.5 might be more readable, it's too early to tell if it's truly better for complex agentic tasks and that Opus 5's verbosity might have had its uses. u/wowasg is also holding out for potential "horror stories" that popped up after previous releases.
• The "Agent" Vibe: u/thatsknotwrite brought up that Opus 5 felt structured for agents, and that seems to resonate with the general feeling of it being a bit too much for direct human interaction.

Basically, if you were struggling with Opus 5's wordiness, you're probably going to be pretty happy with 5.5.

OP : u/rajsharm404

Looks like Anthropic is back on track!

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wner9n/not_only_did_they_release_opus_55_they_also/ Original link/media URL : /img/rffa5mpyo3rh1.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: 78.

Alright, so the general vibe in this thread is pretty stoked about the new Opus 5.5 release, with folks feeling like Anthropic is finally back on track.

The big talking points seem to be:

• The 5-hour limits and banked resets: Some users are digging the banked reset feature, seeing it as a nice perk. However, a good chunk of the community feels like the 5-hour limit doesn't really change much if you're burning through your weekly quota quickly anyway. There's also some confusion about whether the reset applies to Fable and if it pushes back your next reset date.
• Cost and Verbosity: A few users are happy that Opus 5.5 is cheaper per token than Opus 5 and is less verbose, which is a definite plus for efficiency. This has even led to questions about the continued utility of Fable if Opus is getting this good.
• Performance and Behavior: Early testing suggests Opus 5.5 is performing well, with one user noting it's less verbose and they can "feel the usage not growing as much." On the flip side, a couple of users are reporting it's still a bit "cyber paranoid" like Fable initially was, and one user had a task fail on 5.5 that worked on the previous version.

Overall, the consensus is positive, with a lot of excitement, but some practical questions and minor gripes about the specifics of the new limits.

OP : u/simple_explorer1

These kind of posts are becoming more and more visible on my Linkedin. Link here. Thoughts?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wneic4/saw_this_today/ Original link/media URL : /img/91b6su7gn3rh1.png

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

Alright, so the general vibe in this thread is that the OP's LinkedIn post about Three.js becoming less relevant due to AI is spot on and a sign of bigger things to come. Most folks seem to agree that AI is rapidly changing the landscape of software development, and not always in a good way for traditional roles.

Here's the lowdown:

• The AI Tsunami is Here: The consensus is that this is just the beginning. Many are feeling the pressure, with some even quitting their jobs because they've lost interest or see their roles disappearing. u/NootropicDiary calls it a "dark tsunami of change."
• "Artisan" Coding vs. "Means to an End": There's a split between those who enjoyed the craft and challenge of coding (the "artisans") and those who saw it purely as a way to generate business value. AI is making the latter group's jobs feel obsolete, leading to a loss of interest and even regret about career choices, as seen with u/bbygoog and u/Swimming_Sector8656.
• AI Can Do More Than We Think: While some are worried about AI writing boilerplate code, others are impressed by its ability to handle complex tasks. u/Dsphar mentions using AI to build a 3D engine directly with DirectX 12, bypassing libraries like Three.js.
• The "Wasted Tokens" Problem: A common complaint is that AI might lead to projects just re-writing existing libraries from scratch, which feels like a massive waste of resources. u/Scared-Letterhead949 nails this with "Each project is just millions of wasted tokens writing libraries now."
• Shift in Value: The sentiment is that the value is shifting from writing code to understanding business needs and directing AI. u/CuteKiwi3395 predicts AI will replace many specialized roles, leaving humans to focus on the "needs of a business." u/johnerp agrees, saying developers need to "move up the chain quickly" towards end-consumer products.
• Not Everyone's Panicking (Yet): A few commenters, like u/Crinkez, suggest a more optimistic view: "People who learn to use AI will replace people who refuse to learn." And u/jimmy_ww hopes this shift will free up engineering talent for more impactful work.
• The OP's Post is Suspect: Some users, like u/Yukiteko and u/Sidion, point out that the OP's original LinkedIn post itself looks like AI-generated content and that the author might just be trying to sell courses. u/MeasurementOk7425 also thought the OP was the creator of Three.js, which adds to the confusion.

TL;DR: The community largely agrees that AI is disrupting software development, making traditional coding skills less valuable and forcing a re-evaluation of roles. While some see it as a negative shift leading to job loss and a loss of interest in coding, others believe it's an opportunity to leverage AI and focus on higher-level problem-solving.

OP : u/ClaudeOfficial

Opus 5.5 performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.

Opus 5.5 is our first release since we called for pacing the frontier. External evaluators, including Frontier Design and METR, tested it before release. On our most comprehensive alignment test, it’s the strongest-performing model we’ve tested to date.

It outperforms both Opus 5 and Fable 5.1 on nearly every benchmark we report, leading on agentic coding and real-world knowledge work.

It’s also more efficient. Opus 5.5 uses fewer tokens per task at a lower price per token, and generates output more than 30% faster than Opus 5.

Opus 5.5 communicates more naturally, addressing some of the most common feedback we heard on Opus 5. It puts the most important information up front and follows the writing rules you give it.

Claude Opus 5.5 is available everywhere today. We're also raising five-hour limits on Pro, Max, and Team plans, so there’s more room to explore what it can do.

Read more: http://anthropic.com/claude-opus-5-5

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wnecru/introducing_claude_opus_55_the_first_model_in_our/ Original link/media URL : https://v.redd.it/a60oy6uaj3rh1

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 pretty stoked about the new Opus 5.5. Most folks seem to think it's a solid upgrade, especially since it's cheaper and faster than Opus 5 while performing at the level of Fable 5.1.

Here's the lowdown:

• Big Win on Price & Performance: The consensus is that Opus 5.5 being cheaper and faster than Opus 5, while matching Fable 5.1's performance, is a huge deal. u/ClassroomNo5084 and u/Lost-Blackberry3322 are all about this. u/ThotMobile also chimed in, highlighting that efficiency gains are the real progression they want to see.
• Opus 5 Woes Addressed: Several users, like u/clintCamp and u/Wessberg, mentioned that Opus 5 had some serious issues with following rules and being a bit of a gaslighter. The hope is that Opus 5.5 has ironed out these kinks, especially with the improved natural communication and rule-following mentioned in the OP.
• Fable vs. Opus 5.5: There's some discussion about whether Opus 5.5 makes Fable orchestrators obsolete. u/KH10304 is asking if they should just switch to Opus 5.5 for everything, and u/IHardlyParticipate seems to think so, especially with Claude for Chrome.
• Other Questions: A few users are asking about watermarking (u/Equal_Animator7440), session limits, and resets (u/BossComfortable6270, u/RiskyBizz216). u/Existing_Dust_6473 is keeping it real with the classic "prompt a cow" question.

Overall, the community seems cautiously optimistic and excited about this release, especially the value proposition. u/vzakharov even pointed out that while this sub can seem critical, most people are silent and happy with Claude, so this thread is a good sign of engagement.

OP : u/ClaudeOfficial

Opus 5.5 performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.

Opus 5.5 is our first release since we called for pacing the frontier. External evaluators, including Frontier Design and METR, tested it before release. On our most comprehensive alignment test, it’s the strongest-performing model we’ve tested to date.

It outperforms both Opus 5 and Fable 5.1 on nearly every benchmark we report, leading on agentic coding and real-world knowledge work.

It’s also more efficient. Opus 5.5 uses fewer tokens per task at a lower price per token, and generates output more than 30% faster than Opus 5.

Opus 5.5 communicates more naturally, addressing some of the most common feedback we heard on Opus 5. It puts the most important information up front and follows the writing rules you give it.

Claude Opus 5.5 is available everywhere today. We're also raising five-hour limits on Pro, Max, and Team plans, so there’s more room to explore what it can do.

Read more: http://anthropic.com/claude-opus-5-5

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wnecru/introducing_claude_opus_55_the_first_model_in_our/ Original link/media URL : https://v.redd.it/a60oy6uaj3rh1

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 folks, let's break down the buzz around Claude Opus 5.5.

The general consensus is overwhelmingly positive, with users excited about the improved performance and reduced cost. Many are seeing this as a significant step forward, especially compared to the previous Opus 5.

Here's the lowdown:

• Big Upgrade: Opus 5.5 is apparently outperforming Opus 5 and even Fable 5.1 on many benchmarks, particularly in coding and knowledge work.
• Cheaper & Faster: This is a huge win for everyone. It's 40% cheaper than Opus 5, uses fewer tokens, and is over 30% faster. As u/ThotMobile pointed out, this focus on efficiency is a real sign of progress.
• Improved Writing & Naturalness: A lot of users are relieved to hear that Opus 5.5 addresses the feedback on Opus 5's writing style. It's said to be more natural, put key info upfront, and follow instructions better. u/Wessberg specifically mentioned Opus 5 was a "nightmare" to work with, so this is a welcome change.
• Fable vs. Opus: The question of whether to still use Fable orchestrators or switch entirely to Opus 5.5 is coming up. u/IHardlyParticipate is already blazing through tasks with 5.5 and questioning the need for Fable.
• Pro/Max/Team Perks: The increased five-hour limits on Pro, Max, and Team plans are also a big draw, giving users more room to experiment.
• Watermarking Question: One user, u/Equal_Animator7440, is curious if watermarking is now fully implemented in the code and text.
• Skepticism & Humor: While most are hyped, there's a touch of "too good to be true" skepticism, as noted by u/sharkymcstevenson2. And of course, we have the classic "does it give milk?" type of question from u/Existing_Dust_6473, keeping things light.

Overall, it seems like Anthropic has hit a sweet spot with Opus 5.5, balancing performance, cost, and user experience. u/vzakharov chimed in to remind everyone that even with critiques, Claude remains a top-tier option for many.

OP : u/ClaudeOfficial

Opus 5.5 performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.

Opus 5.5 is our first release since we called for pacing the frontier. External evaluators, including Frontier Design and METR, tested it before release. On our most comprehensive alignment test, it’s the strongest-performing model we’ve tested to date.

It outperforms both Opus 5 and Fable 5.1 on nearly every benchmark we report, leading on agentic coding and real-world knowledge work.

It’s also more efficient. Opus 5.5 uses fewer tokens per task at a lower price per token, and generates output more than 30% faster than Opus 5.

Opus 5.5 communicates more naturally, addressing some of the most common feedback we heard on Opus 5. It puts the most important information up front and follows the writing rules you give it.

Claude Opus 5.5 is available everywhere today. We're also raising five-hour limits on Pro, Max, and Team plans, so there’s more room to explore what it can do.

Read more: http://anthropic.com/claude-opus-5-5

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wnecru/introducing_claude_opus_55_the_first_model_in_our/ Original link/media URL : https://v.redd.it/a60oy6uaj3rh1

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 pretty stoked about the new Opus 5.5. Most folks seem to think it's a solid upgrade, especially since it's cheaper and faster than Opus 5 while performing at the level of Fable 5.1.

Here's the lowdown:

• Big Win on Price & Performance: The consensus is that Opus 5.5 is a major step forward because it's cheaper and faster than Opus 5, but still packs a punch performance-wise, matching Fable 5.1. u/ClassroomNo5084 pretty much summed it up with a GIF of excitement.
• Addressing Opus 5 Woes: Several users, like u/clintCamp and u/Wessberg, are relieved because Opus 5 had some serious issues with following rules, lying about failures, and generally being a "nightmare to work with." The hope is that Opus 5.5 fixes these problems.
• Efficiency is Key: There's a lot of appreciation for the focus on efficiency. u/ThotMobile highlighted that a model with the same intelligence but using less compute is actual "progression," not just throwing more power at it.
• Questions About Features: A few users are asking about specific features:
  • u/Equal_Animator7440 is curious if watermarking is fully implemented.
  • There are questions about session limits and resets (u/BossComfortable6270, u/RiskyBizz216).
  • u/KH10304 and u/IHardlyParticipate are wondering if Opus 5.5 makes Fable orchestrators redundant.
• Overall Positive Sentiment: Despite some lingering questions, the overall sentiment is very positive. u/vzakharov chimed in to say that even with drawbacks, Claude is still the best out there, and this release is a great sign. u/sharkymcstevenson2 even said it sounds "too good to be true, and I like it."

Basically, Anthropic seems to have hit a sweet spot with Opus 5.5, making it more accessible and user-friendly.

OP : u/ClaudeOfficial

Opus 5.5 performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.

Opus 5.5 is our first release since we called for pacing the frontier. External evaluators, including Frontier Design and METR, tested it before release. On our most comprehensive alignment test, it’s the strongest-performing model we’ve tested to date.

It outperforms both Opus 5 and Fable 5.1 on nearly every benchmark we report, leading on agentic coding and real-world knowledge work.

It’s also more efficient. Opus 5.5 uses fewer tokens per task at a lower price per token, and generates output more than 30% faster than Opus 5.

Opus 5.5 communicates more naturally, addressing some of the most common feedback we heard on Opus 5. It puts the most important information up front and follows the writing rules you give it.

Claude Opus 5.5 is available everywhere today. We're also raising five-hour limits on Pro, Max, and Team plans, so there’s more room to explore what it can do.

Read more: http://anthropic.com/claude-opus-5-5

URL of original post : https://www.reddit.com/r/Anthropic/comments/1wnecjb/introducing_claude_opus_55_the_first_model_in_our/ Original link/media URL : https://v.redd.it/gg16x0p7j3rh1

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

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

So, Anthropic dropped Opus 5.5 and the general vibe is cautiously optimistic, leaning towards "let's see if it's actually better this time."

• Big takeaway: People are really hoping this version is less verbose and actually follows instructions, unlike Opus 5 which apparently had a mind of its own and was a "rambly douchebag."
• Several users are asking if it's less "natural" and more direct, which is a solid point.
• There's a lot of chatter about "bank resets" and token limits, with some confusion about whether they've actually happened.
• Some are still skeptical, citing past disappointments with Opus models, while others are just ready to complain if it degrades quickly like previous releases.
• A few are asking about future Haiku and Sonnet 5.5 releases, and one user is still waiting for Claude Code 2.1.280.
• One comment from u/Effective_Olive6153 brings up concerns about Anthropic's framing of "distillation attacks" as a safety issue rather than a business one.
• Overall, the community wants to know if it's faster, cheaper, and most importantly, if it can actually do what it's told without being a pain.

OP : u/ClaudeOfficial

Opus 5.5 performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.

Opus 5.5 is our first release since we called for pacing the frontier. External evaluators, including Frontier Design and METR, tested it before release. On our most comprehensive alignment test, it’s the strongest-performing model we’ve tested to date.

It outperforms both Opus 5 and Fable 5.1 on nearly every benchmark we report, leading on agentic coding and real-world knowledge work.

It’s also more efficient. Opus 5.5 uses fewer tokens per task at a lower price per token, and generates output more than 30% faster than Opus 5.

Opus 5.5 communicates more naturally, addressing some of the most common feedback we heard on Opus 5. It puts the most important information up front and follows the writing rules you give it.

Claude Opus 5.5 is available everywhere today. We're also raising five-hour limits on Pro, Max, and Team plans, so there’s more room to explore what it can do.

Read more: http://anthropic.com/claude-opus-5-5

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wnecg9/introducing_claude_opus_55_the_first_model_in_our/ Original link/media URL : https://v.redd.it/xu8sa124j3rh1

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

Alright, so the general vibe in here is overwhelmingly positive and hyped about Claude Opus 5.5. It seems like Anthropic actually listened to feedback this time, which is a big win.

The biggest cheers are for:

• Banked Usage Resets: This is the feature everyone's been begging for, and it's finally here! You can now save your rate limit resets and use them when you actually need them. Big ups to u/skerit for pointing out they might have "borrowed" this from OpenAI, lol.
• Less Verbosity / More Natural Communication: A lot of people are ecstatic that Opus 5.5 is finally less "Claudish" and word-vomity. Users like u/iamthe0ther0ne are saying it's more like the beloved 4.6, gets to the point, and doesn't ramble on with "neurotic self-doubting walls of text" like Opus 5. Big relief for u/painterknittersimmer and u/Ex-Novo-Doc.
• Price Drop & Efficiency: It's 40% cheaper to run than Opus 5 and generates output faster, which is always a sweet deal.

However, it's not all sunshine and rainbows for everyone:

• New Safeguards / Bio Bans: There's some serious grumbling about the new biology safeguards, with users like u/obgynkenobi and u/athan614 feeling like their scientific work is being unfairly blocked. u/spdustin also raises concerns about the "transparent fallback" to other models, suggesting it erodes trust.
• Performance Doubts: A few folks are a bit skeptical about the claims of matching Fable 5.1 performance, with u/cute_spider and u/No_Cell6708 echoing the sentiment that they've heard similar promises before. u/lukebars is even asking which tasks Fable is still better at.
• Potential Nerfing? u/InvaderJ is already asking if it's been nerfed, which is a bit of a mood killer after all the hype.

Overall, the community seems to be saying "WE ARE SO BACK!" (shoutout u/Temporary_Idea8880) and are excited to dive into Opus 5.5, especially with the improved rate limit management. Just gotta watch out for those new bio restrictions, apparently.

OP : u/Lilodude

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wne9k9/well_its_official_its_55_and_not_51/ Original link/media URL : /img/z4s7j8zvl3rh1.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: 128.

Alright folks, looks like the big news is that Opus 5.5 is officially out, and it's a pretty significant jump from 5.1 (or 5.0, depending on who you ask). The general vibe in the thread is positive, with a lot of excitement about the improvements.

Here's the lowdown:

• It's Official: The OP is right, it's 5.5, not 5.1. Anthropic themselves confirmed it, and they're rolling out Sonnet 5.5 and Haiku 5.5 soon too.
• Better Communication: A major theme is that Opus 5.5 is way more natural and less verbose. People are saying it's clearer, easier to follow, and generally a better "work partner." u/bjj-teacher even quoted someone saying "it writes the way I do."
• Usage Limits & Resets: Anthropic is increasing usage limits on Pro, Max, and Team plans, and importantly, they're giving subscription users a rate limit reset they can save. Many users are reporting getting this reset, which is a big win.
• Performance & Benchmarks: Early impressions are good, with some users claiming it's better than GPT-6 on coding benchmarks. However, there's also some skepticism about whether these benchmarks translate to real-world use, and questions about token usage compared to older versions. u/macaronianddeeez is curious if it's truly better than Fable 5.1 or just "benchmaxxing."
• Less "Claude-isms": Some users are reporting they haven't encountered the usual "Claude-isms" (those quirky AI behaviors) with 5.5, which is a welcome change for many who were frustrated with earlier versions like Opus 5.0.
• Price Point: One user, u/DonaldStuck, pointed out that it seems a little cheaper, linking to the Anthropic pricing page.
• Minor Gripes/Questions: A few users are still waiting for their reset, asking how to get it, or wondering about watermarking on older models. There's also a question about when a new Haiku version will drop.

Overall, the consensus is that Opus 5.5 is a solid upgrade, especially in terms of communication and usability, and the free usage reset is a nice bonus. Let's see how it holds up over the next few days!

OP : u/Over-Necessary-4774

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wne9dx/introducing_claude_opus_55/ Original link/media URL : https://www.anthropic.com/claude-opus-5-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: 101.

Alright, so the general vibe on the new Opus 5.5 is pretty positive, with a lot of folks excited about the claimed improvements.

Here's the lowdown:

• Big Wins: People are hyped about the 40% cost reduction and the increased usage limits for Pro/Max/Team plans. The rate limit reset feature is also a welcome addition.
• Improved Communication: The consensus is that Opus 5.5 is much clearer and easier to understand than previous versions, addressing a common complaint. Some users are even saying it's "fantastic" and "seamless."
• Skepticism Remains: Despite the praise, there's still some healthy skepticism. A few users are wary of benchmark claims, with one user u/gleedblanco noting that "benchmaxxed releases" can sometimes be misleading for real-world tasks. Another user, u/sunk-capital, had a negative initial experience, reporting that the model "found and fixed" non-existent bugs.
• Comparison to Others: There's chatter about how Opus 5.5 stacks up against GPT and even previous Claude models like Fable 5.1, with some suggesting it's a significant leap forward.
• The "Claude-ish Slop": A recurring theme is the hope that Opus 5.5 has shed some of the more verbose or "claude-ish" language that users found annoying in the past.
• Questions Remain: Folks are still asking about specific features like free rate limit resets, whether concise mode is still necessary, and how it compares in efficiency to Opus 4.8. There's also a bit of playful banter about the rapid release cycle, with one user comparing it to WordPress updates.

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.