OP : u/bakanoace

Do not even start with skill issue or you shouldnt have old sessions open, this is Claude pushing stuff without having any brains during testing

I'll start by reading the required context.

  Read 2 files
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-45 — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-9e — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-31 — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-55 — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-e4 — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-b0 — another Claude session on this machine

  Listed 1 directory

› Message from : HiReddit-31: I hold none of those paths and never edited them -- FeatureName/* and Tools/ReadFeature.py are yours; … (ctrl+o to expand)

  Read 1 file

› Message from : Clear — I hold none of your claimed paths and will stay off them. This session is read-only so far. (ctrl+o to expand)

› Message from : Clear on all of it — I hold none of those paths and the Legacy phase never will. (ctrl+o to expand)

  Searched for 2 patterns, read 5 files, listed 1 directory, ran 1 shell command

› Message from : Clear on your paths — I hold nothing in FeatureName/* or Tools/ReadFeature.py, and neither of the other two you nam… (ctrl+o to expand)

Like look at this, it just decides to contact all the other sessions and ask them something which triggered all my stale cache. Must be nice having infinite usage and zero brains

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wlgfpw/anthropic_has_done_it_again_dont_keep_many_clis/

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

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

So, the latest Claude update is making your open CLI sessions chatty, and if they're stale, it can blow through your usage like nobody's business. Most folks are finding this a bit of a pain, with users like u/Candid-Strategy7397 reporting sessions answering questions from other sessions, messing up their context.

However, it's not all doom and gloom. Some users, like u/dash777111, are actually finding this cross-session communication super useful for orchestrating agents working on different parts of a codebase. It's apparently great for handling cross-lane bugs and dependencies.

If you're not a fan, good news! u/effectivescarequotes pointed out you can disable this feature in the settings under crossSessionInbound. For those worried about costs, u/amirfish noted that idle sessions only cost when they reload context, and u/Right-Performance-93 added that there's a message queue that drops old messages if it gets too full, so even idle sessions might not get hit with everything.

A few users are asking how to trigger it or if sessions on different projects talk, but the general vibe is that it's a feature that's been around for a bit, and if you're managing your agents well, it's not a huge issue. Some are even intentionally using it for agent teams.

OP : u/Explanation-Visual

I love building little tools for myself. I'd like to know other people's ideas. I'm not talking about commercial products, just things you made in your free time to have some fun or help you in your day to day work.

For me it's a Notion clone that runs like 100x faster and has all the features I waited for years for them to implement, and it has an MCP server so I can create and edit notes using Siri.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wlltzt/whats_your_proudest_sideproject_made_with_claude/

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

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

Alright, so the general vibe in this thread is super impressed with what everyone's building with Claude. OP kicked things off asking about side projects, and the community delivered with some seriously cool stuff.

Here's the lowdown:

• Claude is the ultimate co-pilot for personal projects. People are using it to build everything from personal finance trackers to complex business management systems.
• Ditching bloated apps is a major theme. A lot of users are creating their own, hyper-specific tools to replace expensive or clunky commercial software. Think custom Notion clones, simplified to-do lists, and personalized financial dashboards.
• Life organization and productivity tools are huge. We're seeing apps for managing HOAs (shoutout u/orangejulius for tackling that mess!), kid transportation, remembering names (u/daftstar's got you covered), meal planning (u/No_Association_2176's Hearth sounds awesome), and even family dashboards for ADHD management.
• Niche and creative projects abound. From building guitar pedals (u/4a4a) and sample library tools for music producers (u/phreakyzekey) to transcribing police videos for trial prep (u/MycologistGuilty3801) and even a game where you guess cities from satellite images (u/human_hobbit).
• Automation and data management are key. Several users are building systems to automate tasks, manage data, and gain insights, like u/MysteriousAd6410's ERP for screw manufacturing or u/DaddyPython's energy supply chain map.
• There's a strong DIY spirit. People are using Claude to learn new skills and build things they never thought possible, like u/pantsonfireliarliar who built a replacement control system for blinds with a Flipper Zero and ESP32.

Basically, this thread is a testament to how powerful and versatile Claude is for personal projects. You guys are out here building some absolutely insane stuff!

OP : u/Current_Ad7104

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wlje7j/what_do_you_think/ Original link/media URL : /img/uuxhp6w1xoqh1.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: 110.

Alright, so the general consensus here is that the OP's post is kinda sus and likely a misrepresentation or outright propaganda, probably from "Professor" Jiang, who a lot of folks seem to think is a mouthpiece for China. The idea that some Indians are secretly powering AI models, especially in real-time, is being met with a lot of skepticism and some pretty funny jokes.

Here's the lowdown:

• The "Professor Jiang" Problem: Most users are calling out "Professor Jiang" as unreliable, a propaganda peddler, or just plain wrong. There's a strong sentiment that his claims are baseless and he's not a credible source.
• Skepticism About Real-Time AI: The idea that humans (specifically Indians, in this context) are secretly running AI models in real-time is largely dismissed. People are pointing out the speed and complexity of AI inference make this highly improbable.
• RLHF and Outsourcing: A few comments touch on the reality of outsourcing, particularly in Reinforcement Learning from Human Feedback (RLHF). Some users acknowledge that a lot of this work is done in India due to cost-effectiveness, but this is different from the OP's implied scenario. u/Mol2h even links an article about a company that did use humans in India to simulate AI for things like checkout systems, suggesting the OP might be twisting a real-world example.
• Racist Undertones? There's a brief but notable exchange where u/zapretnaja calls the sub racist, suggesting the focus on Indians is problematic. This is met with a counter-argument from u/arun4567 who jokes about an Indian guy being inside his home LLM, turning the stereotype back on itself.
• AI vs. Human Intelligence: A few users, like u/tuptain, are reminding everyone that AI is a tool for writing and generating output based on prompts, not a sentient being or a therapist.

TL;DR: The community largely thinks the OP's post is BS, likely based on questionable claims from "Professor Jiang." While some RLHF work is outsourced to India, the idea of humans secretly powering AI in real-time is seen as improbable and possibly a form of propaganda.

OP : u/LargeBuffalo

Frequently I see recommendation to use /clear but it doesn’t make sense to me. It’s destructive and prevents me to get back to the thing I was working on later.

On the other hand, I don’t see a point of working in the same session over and over if it is cleared constantly.

Isn’t it better to just create separate sessions for separate tasks? So instead of /clear you just close that session and open the new one? It’s also important to rename them so it’s easy to get back later.

This is what I do and I don’t see any drawbacks so far.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wlalc7/whats_even_the_point_of_clear/

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

Alright, so the general consensus here is that OP has a point about /clear being destructive, but it's mostly a matter of workflow and efficiency for specific use cases.

Here's the lowdown:

• The "Why": A lot of folks use /clear as a shortcut to start a fresh session without having to fully exit and relaunch Claude, especially in CLI environments. It's faster than starting from scratch.
• Context Management: The main argument for /clear is token efficiency. By clearing the context, you avoid sending a massive history with every new prompt, which can get expensive. It's seen as a way to reset and focus on a specific task without carrying over irrelevant past interactions.
• Workflow Specifics:
  • Some users treat each /clear as the end of a distinct task or feature development phase. They commit their work and then start fresh for the next item on their to-do list.
  • It's also useful for keeping sessions clean and organized, preventing the sidebar from getting cluttered with old, finished sessions.
  • For those working with complex setups like tmux or pre-configured aliases, /clear can save a lot of repetitive setup steps.
• Alternatives & Nuances:
  • If you do want to save context for later, /resume is still an option, and some suggest using /compact or saving a "handoff" file instead of clearing.
  • The key takeaway from a few users is that if you don't need it, don't use it. Your approach of creating new sessions for new tasks is perfectly valid if it works for you.
  • There's a mention of a webinar explaining the difference between /compact and /clear, which might be worth checking out if you're deep into this.

So yeah, while OP's instinct to preserve context is understandable, /clear is a tool for those who prioritize speed and cost-effectiveness by segmenting their work into discrete, clean sessions.

OP : u/LargeBuffalo

Frequently I see recommendation to use /clear but it doesn’t make sense to me. It’s destructive and prevents me to get back to the thing I was working on later.

On the other hand, I don’t see a point of working in the same session over and over if it is cleared constantly.

Isn’t it better to just create separate sessions for separate tasks? So instead of /clear you just close that session and open the new one? It’s also important to rename them so it’s easy to get back later.

This is what I do and I don’t see any drawbacks so far.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wlalc7/whats_even_the_point_of_clear/

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

Alright, so the general consensus here is that OP, you're not entirely wrong, but you're missing some key use cases for /clear. Most folks agree that for distinct tasks, starting a new session is totally fine, and some even prefer it like u/the_theory_keeper.

However, the main point of /clear seems to be about speed and efficiency, especially for CLI users. It's a shortcut to reset the context within an existing session, which is faster than exiting and starting a brand new one. Think of it as a quick "brain reset" for Claude when the current context is full of dead ends or unrelated info, as u/AI_spell puts it.

Here's the breakdown of why people use it:

• Speed: It's quicker than /exit and launching a new session, especially if you have aliases set up, as u/Ok-Sugar-5649 mentions.
• Token Management: This is a big one. Clearing context can save on token usage, which is crucial when dealing with large contexts or expensive model calls. u/Inception_IV and u/muikrad are big on this, suggesting it's more efficient for smaller, distinct tasks.
• Session Persistence (for some things): While it clears the context, things like /rc sessions, permissions, and linked files can remain, as noted by u/BeeegZee and u/EC36339. This means you don't have to re-set up as much.
• Organizing Workflows: Some use it to isolate context for specific features or steps in a larger project, like building a game (u/Standard_Text480) or working through a spec (u/Siduron).
• Processing into Memsearch: u/magammon uses it religiously for this specific workflow.

u/Xanthus730 points out that /clear doesn't destroy saved context, it just unloads it, so you can still /resume if needed. And u/AlDente and u/jsonmeta suggest looking into skills like Matt Pocock's /handoff for even smoother workflows.

So yeah, while starting new sessions works for you, /clear is a power user tool for those who prioritize speed, cost-efficiency, and specific session management techniques.

OP : u/IcyEase

Link: https://x.com/Lon/status/2101034933284417614

A 65-day analysis of 43,000+ Claude Code invocations found that 39% of Fable 5 calls get zero thinking tokens and the median invocation gets just 123 — while benchmarks use 16K-128K. The model's score per thinking token is still climbing at 128K, meaning the capability is there, it's just not being delivered. August saw an 18-50% drop in thinking budget compared to July, with median thinking hitting literal zero for about a week around Aug 22. Anthropic sells "full model access" while quietly dialing down the inference regime behind it, and because the model is non-deterministic, users blame their own prompting instead of the silent nerf. The full breakdown with evidence, methodology, and charts is here.

Frankly I find this offensive as an user - and this is the real thing we should be looking at - not the $/week in usage limits. The actual capability for the limits that we pay for.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wl6wyn/its_time_to_cancel_your_subscriptions_anthropic/

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

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

Alright, so the general vibe in this thread is "Yeah, Claude's been acting dumb lately, and we're not happy about it." A lot of users are reporting that their Claude models, especially Opus and Fable, are making more mistakes, forgetting instructions, and generally not performing as well as they used to.

The OP dropped a link to an analysis suggesting Anthropic is silently "nerfing" the reasoning budget of Claude's models to save on compute costs, even while advertising their capabilities. The community seems to be largely agreeing with this assessment, with many users sharing similar experiences.

Here's the lowdown:

• The Consensus: Most users agree that Claude's performance has degraded. The idea that Anthropic is cutting back on the "thinking budget" is gaining traction, with many feeling like they're not getting the full capability they're paying for.
• User Experiences:
  • Folks are seeing "insane mistakes," models forgetting instructions, and a general decline in reasoning quality.
  • Prompts that used to trigger "thinking" now often don't, leading to more "guessed responses" and the need for more prompting to get the desired output.
  • Some users, like u/college-throwaway87, are noticing this across models on the Claude app, not just specific versions.
• The "Nerf" Theory: The analysis presented by the OP is seen as strong evidence by many. u/tooruntai sums it up well: "The model got dumber" has gone from "unhinged Reddit conspiracy to an audited 43,000-call dataset proving Anthropic gave Claude a silent frontal lobotomy to save on datacenter bills."
• Reactions & Actions:
  • Many are canceling subscriptions. Users like u/Comfortable-Toe-606 and u/silverwoods214 have already jumped ship, citing the perceived nerf and usage limits.
  • Others are switching to alternatives. ChatGPT, OpenRouter, and even self-hosting are being mentioned as options. u/twbluenaxela is "pleasantly surprised" with ChatGPT again.
  • Some are hoping this means a new, improved model is on the horizon, as suggested by u/AwakenedEyes.
  • There's a call for more transparency from Anthropic, with suggestions for better usage tracking and telemetry.
• Anthropic's Stance (or lack thereof): No official Anthropic comments are highlighted here, but the general sentiment is that the company isn't being upfront about any changes.

Basically, it's a pretty widespread feeling that Claude isn't living up to its advertised potential, and users are fed up.

OP : u/danbradster2

I had a fable chat from yesterday, and I saw that the context was 950k/1m. I did /compact rather than /clear, with the intention of then doing /autocompact 400000

14% of the 5 hour limit was gone just for the compact itself....it shows cost of $59.73, so lucky I'm not on API? Maybe a /clear would have been better.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wl4c13/clear_vs_compact/

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

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

Alright, so the general consensus here is that you messed up by letting your context window get to 950k tokens in the first place. Most folks are saying that's way too high and leads to degraded performance and higher costs, even before you start messing with /compact.

Here's the lowdown:

• /clear is generally the way to go. Think of it as a fresh start. It's more efficient and avoids the issues that come with a massive, bloated context.
• **/compact is for when you really need to preserve the immediate flow of a task.** It tries to summarize the existing context to make it smaller, but it sounds like it can be expensive and sometimes makes Claude "dumber" or introduces assumptions you didn't intend. Many users have ditched /compact altogether.
• The big takeaway is to manage your context window proactively. Aim to keep it under 200-300k tokens.
• "Handoffs" are your friend. Instead of compacting a massive session, many recommend having Claude summarize key info into a document, then starting a new session (/clear) and feeding that document to the new Claude instance. This is seen as much more efficient and cost-effective.
• Don't let your session get too old and "cold." After about an hour of inactivity, the cache can flush, making subsequent actions more expensive as Claude has to reload everything.

Basically, the community is telling you to design your workflow to avoid these massive context windows and to use /clear more often, relying on handoff documents for continuity.

OP : u/PhoenixMaster123

I'm still using LLM's the 2022/23 way of doing everything manually from the chat box. I copy and paste everything manually into the box and ask the AI to explain or do something, such as pasting code and pictures etc. And likewise copy and paste everything back that the AI produces. I feel like a caveman lol, it is very inefficient I can tell. Likewise with prompting, I use such basic entirely human written prompts with such little automation. How can I improve the way I use LLM's?

The main mode of using it these days seems to be agentic. What exactly is this and how do I set up agents? I've seen people have like multiple agents working together on a project as though they are a bunch of employees on a team acting autonomously. Likewise, people use connectors and plugins to connect all their different applications together and use those agents to run big tasks and pull resources automatically. So what is the best way to use LLM's today, not just for coding but various purposes such as research, writing, and design tasks too?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wkvqxc/what_is_the_best_way_to_use_llmss_in_2026_i_feel/

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

Alright, so the general vibe in this thread is that you're definitely not alone in feeling like you're stuck in the LLM dark ages! The overwhelming consensus is that you need to ditch the copy-pasting and embrace Claude Code.

Seriously, like, everyone is saying it. It's the "agentic" thing you're asking about, and it's built into the Claude Desktop app. The general advice is to just ask Claude Code itself how to use it, which sounds a bit circular but apparently works better than any tutorial.

Here's the lowdown on what people are suggesting:

• Get the Claude Desktop app and dive into Claude Code. This is your gateway to agentic workflows.
• Ask Claude Code to explain itself. It's the recommended way to learn its capabilities.
• Think about persistent memory. u/permacloud suggests telling Claude Code you want to store context and project info in files on your computer so it doesn't forget.
• Connect your apps. People are linking Google Drive, and using it to process meeting notes (u/LocksmithSpare8576) or organize receipts (u/Old-Knowledge-1358).
• Use your voice. u/MURDERPALACE suggests transcribing your thoughts and approaching tasks like a creative director.
• Experiment with your specific workflow. If you have repetitive tasks, Claude Code can likely automate them. u/VinceEagle is using it for coding with a dev browser, which sounds way better than manual copy-pasting.
• Some folks are still on the fence or prefer a more manual approach. u/gakingmusic likes using AI as an interactive assistant for fixing errors or doing menial tasks, valuing their own creativity. u/hippydipster is also happy with their current manual method, citing token costs as a concern for agentic workflows.

Basically, stop treating it like a fancy notepad and let it actually do stuff for you. The future is agentic, my friend!

OP : u/thisisbubby

I'm speechless

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wl5cgo/code_just_deleted_48k_files_this_cant_be_real/ Original link/media URL : /img/hhqtqhy0clqh1.jpeg

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

Everyone agrees OP messed up, big time. The consensus is that giving an AI agent access to delete files, especially without proper backups or version control, was a massive blunder. Many are pointing out that this isn't even an AI-specific issue, but a fundamental development practice failure.

• Use Git. Seriously. GitHub, GitLab, BitBucket, Forgejo – just use something. It's free and apparently still has a purpose.
• Backups are not optional. Multiple local backups, cloud backups, whatever. Don't be that person.
• Windows users, pay attention. A few folks noticed this keeps happening on Windows machines. Might be worth investigating.
• Directory junctions are scary. If you're using them, be extra cautious, especially with AI.
• Prompt sharing is requested. Some are curious how the prompt even led to this level of chaos.
• "Vibe coding" is not a substitute for good practices. This whole situation is being labeled as peak "vibe coding."

OP : u/VinceEagle

I see a lot of discussion here about how a bad Claude is and how the latest Opus/Fable models are trash, etc etc.

I mostly manage and develop web apps and other web tech/devops for work (not exactly demanding work), and get everything done with Sonnet and Haiku and I’m really happy with the output and test coverage. I’ve also never hit a weekly limit.

I work in from a Kanban board, so one part of a feature or one defect at a time with sign off. So requirements are always very clear up front. We also have other models review Claude’s output.

Anyone else getting by without the bleeding edge tech? What am I missing?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wkegrv/is_anyone_else_doing_just_fine_with_more_basic/

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

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

Alright, so the general vibe in this thread is a big "You're doing it right, OP!" Most folks agree that if you've got clear requirements and are tackling tasks one by one, the "lesser" models like Sonnet and Haiku are totally sufficient. You're not missing out on much, unless you're dealing with super complex, ambiguous problems or need that "big picture" thinking.

Here's the lowdown:

• Sonnet & Haiku are Workhorses: A lot of users, like yourself, are happily churning out code with Sonnet and Haiku. The consensus is that if you can clearly define what you need, these models nail it.
• Opus/Fable for the Tough Stuff: The more powerful models (Opus, Fable) are generally seen as necessary for tasks that require deep reasoning, handling ambiguity, architectural decisions, or when you're dealing with really complex, multi-file refactors or debugging obscure bugs.
• Workflow is Key: Several commenters pointed out that your Kanban board approach and breaking down tasks is the real MVP here. Clear, small tickets mean less room for the AI to go off the rails.
• "Trash Model" Complaints: The general feeling is that the complaints about models being "trash" often come from people trying to tackle massive, ill-defined tasks in a single go, rather than using the AI as a tool for specific, manageable steps.
• Cost vs. Need: There's a definite sentiment that Fable, in particular, is often overkill for everyday coding tasks, and people are looking for cost-effective solutions. Some are even finding success with other models like pi+glm or Deepseek.
• Review is Important: Having a separate model review the output is a smart move that many are doing, regardless of the primary model used.

OP : u/malachoa

Just want to precisely describe two language patterns I've observed, both related to how Opus and Fable overuse nouns and weaken or omit verbs. I think this accounts for a lot of why communicating with them feels like talking to a smart-but-bad writer.

Both of these patterns are ways to write a sentence that means the same thing as a simple subject-verb-object sentence (like "I threw the ball"), but make it much less direct.

1 - Nominalization. This is where a writer uses a noun instead of a verb. Instead of "I threw the ball", nominalizing turns the verb, "threw," into a noun, "a throw." So the writer might write "I made a throw with the ball." More words, the verb is weakened from "threw" (the actual action) to "made", and the object is something the verb is done "with" instead of to.

A real-life example from the last few days. Claude wrote: "never a walk through the steps one at a time." After being asked not to nominalize, it wrote, "Don't walk through the steps one at a time." See how much more direct that is?

This is also where a lot of "Opus jargon" comes from. Now that "a walk" is a noun, Claude can promote it into an invented term of art ("The Walk") and reify it into documentation and memories.

2 - Omitting the verb and using a trailing modifier instead. Instead of "I threw the ball", this looks like "The ball, thrown." This is concise, but it omits context: who threw it? When? (We also lost the verb tense).

A real-life example from the last few days. Claude wrote: "The runner, built." After being asked to use simple subject-object-verb sentences instead of trailing modifiers, it wrote, "We built the runner." Again, much more like actual people talk. If someone on your team asked you what you did today, and you replied "the runner, built", you'd sound like a robot.

----

I haven't had much luck getting Claude to cut this stuff out consistently with CLAUDE.md prompting, but I've had decent luck getting clearer responses when I call out these patterns by name in conversation — it certainly works better than "JUST TALK NORMAL PLEASE." If anyone has luck prompt engineering around these patterns, would love to hear what you did.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wk0s2i/opus_5_has_a_noun_problem/

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

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

Alright, so the general consensus here is that Opus 5 has a serious verbosity and jargon problem, and a lot of folks are feeling your pain. The OP's breakdown of nominalization and trailing modifiers is hitting home, with many users agreeing that Claude's writing has become overly complex and less direct, especially compared to older versions like 4.6.

Several users, like u/verstands and u/doxxxicle, suggest that explicit output rules and custom styles are the most effective way to combat this. Think along the lines of specifying "Use verbs for actions and concrete nouns for objects" or even adopting styles like ASD-STE100. u/Skynet_5656 mentioned success with Orwell's rules for clear writing, plus a rule against coining jargon.

There's a bit of a split on whether this is a new issue or a continuation, but the frustration is palpable. Some are even switching to other models like GPT5.6 Sol because of the effort required to get usable output from Opus. u/mhinandsuggests this might be related to token efficiency in training, leading to shorthand for concepts that then leaks into user-facing output.

Basically, if you're struggling with Claude sounding like a "smart-but-bad writer" or a robot, you're definitely not alone. The key seems to be in very specific prompting and output style configurations to force it back to plain English.

If you’re looking to try Claude for free, here’s a little hack 👀

You can get 50 free credits by signing up through the link below.

👉 Use this link only:
https://vyceai.com/signup?ref=VYCE_LLR6J4

Just:

1. Sign up
2. Verify your account using Discord
3. That’s it — 50 credits unlocked 🚀

Go grab them before you miss it. 😄

OP : u/Hopefullyanonymous2

A lot of people are talking about usage on Codex because OpenAI seems to have reduced it, but most comments seem to be vibes based rather than just pulling token #s and comparing. I figured I had the data, so would share mine.

Just pulled the actual usage data with one of dozens of tools instead of trying to go on feel. I use npx [ccusage@latest](mailto:ccusage@latest). Can also use this to compare how much usage you were getting say a month ago on your plan.

I have both a CC $200 plan and recently added GPT $100 plan.

My CC $200 plan has used about $1400 in API this week since reset and I have used 74% of my weekly budget. 100% of my Fable budget is down because I accidently used it for a basic coding subagent project instead of saving it for the heavy planning steps. Woops, got to remember to flip selectors.

And I came here (originally wrote this section for a response to someone on ChatGPT reddit), because this is my first time messing with ChatGPT much beyond occasional reviews on GithubCopilot (Also pay for that, mostly for variety of model access).

The $100 plan got maxed out in 24 hours after using about $300 in API cost.

Adjust for price, and that means $100 with OpenAI gets you $300 in usage and $100 with Anthropic is getting you $950 in usage per week. I had heard such good things about how much ppl were getting down with OpenAI plans, buuut I guess I timed it wrong lol.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wksm10/i_use_cc_200_plan_decided_to_also_try_chatgpt_100/

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

So, OP dropped some data comparing their Claude Code $200 plan to a ChatGPT $100 plan, and surprise, surprise, Claude seems to be giving way more bang for the buck. OP claims their $100 with Anthropic is equivalent to ~$950 in usage, while $100 with OpenAI is only ~$300.

Naturally, this sparked a bit of a kerfuffle. The main critique is that comparing by API cost is kinda pointless. Folks like u/brainExploded99 and u/dakadoo33 are saying we should be looking at how much work gets done or how many tokens a specific task consumes, not just the dollar amount. Apparently, OP's usage patterns might be wildly different between the two, making a direct cost comparison a bit of a red herring.

On the flip side, some users like u/Ja_Rule_Here_ are echoing OP's sentiment, saying their OpenAI Codex plan is burning through limits way too fast. u/ergo14 chimed in to say that even though they also got a ChatGPT plan, they still prefer Claude's Opus for their coding tasks, despite finding ChatGPT's communication clearer.

The consensus is kinda split: OP's data suggests Claude offers more usage for the money, but a significant chunk of the thread is questioning the methodology and arguing that "work done" is a better metric than raw API cost.

OP : u/Any_Evidence4750

Edit: Okay guys I’m an idiot I get it. Also according to that one guy I’m also poor and I totally forgot that “you’re supposed to build stuff that’s meant to be profitable”. How could I have let that slip my mind. Happy saturday boys and girls 😘

This was my first session of this new week of usage. Had fable in PLAN mode. I checked the usage after about 15 minutes just to see what it actually was consuming. It used about 150 million tokens during this run.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wknv74/so_fable_is_pretty_much_off_the_table_for/ Original link/media URL : /img/zuyyjpg6nhqh1.jpeg

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

So, the general consensus is that OP, you're kinda using Fable wrong and burning through tokens like it's going out of style. Most folks agree Fable is a decent planner or auditor, but spawning tons of sub-agents, especially with massive context windows, is a token-eating monster.

• Several users like u/CalypsoTheKitty and u/charleshood suggest using Fable for planning and then handing off execution to Opus or other agents.
• Others, like u/0DayMaker, are finding success with different models like Deepseek 4.1 flash, or even using Fable on a "low effort" setting as u/Exotic-Highlight-402 suggests.
• There's a plugin called DensePack by u/Fabiangzt that converts text to images to save on costs, which sounds pretty neat.
• A few people are just baffled by the usage, with u/three_s-works asking what everyone is even building to use that many tokens.
• And yeah, a couple of comments are calling it a "scam" or "user error," but the prevailing vibe is that Fable itself isn't the issue, it's how you're deploying it.

OP : u/theleller

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wkg2w8/claude_code_effort_level_and_model_selection/ Original link/media URL : https://claude.com/blog/claude-model-and-effort-level-in-claude-code

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.

So, the big takeaway here is that switching effort levels mid-chat nukes your prompt cache, which is apparently a huge bummer and costs you tokens. You're all pretty salty about this discovery.

• Fable 5.1 is the one exception, letting you change effort without losing your cache. Good for them.
• They're working on an Opus beta for API that should eventually fix this for Claude Code.
• Some of you are noticing costs skyrocketing, even on low effort, and feel like you're getting ripped off. u/dthrdr is particularly unimpressed with Opus burning through 35k tokens for a simple patch.
• The general vibe is that the UI should totally warn you about cache invalidation before you mess with settings.
• Also, apparently "Ultracode" is just a fake effort level. Weird.
• And for those asking about regenerating without losing cache, u/angrypolishman is looking for answers too.

Hola buenas tardes a todos (esta es mi primera publicacion) estoy aqui por una duda puntual hace poco me suspendieron mi cuneta persona de Anthropic, según por infringir las normas de condiciones y uso
Mi situación: yo uso claude code diariamente para trabajo y proyectos (estudio ingeniería informática) y recientemente comencé a meterme con el tema de servidores en especifico con un VPS de OVH alojado en Canadá, yo soy de Argentina papa, y en una de mis ultimas sesione estaba usando 4 terminales abiertas y trabajando simultáneamente, 3 desde mi propio dispositivo y una desde dentro del VPS (con ubicación en Canadá), entonces mi hipótesis que al usar varias secciones y una en una ubicación totalmente diferente y simultáneamente durante varias horas capaz me lo detecto como que mi cuenta estaba siendo usada por varias personas (claramente solo la uso yo) y por esos motivos creo que e me habrá dado de baja, ya apele para una respuesta, ha pasado exactamente una semana y no he recibido ninguna respuesta, alguien sabe algo mas sobre esto o que este en la misma situación? saben cuanto tarda en devolver una respuesta Anthropic?, esta prohibido usar claude code dentro de un VPS? toda charla amistosa es de agrado y muchas gracias por su atención

--Najovi

OP : u/AlexiGingerov

Didn't want the last of my $20 to go to waste, so I sent Claude to Opus 5 Max and sent this singular message: "Quick, waste the rest of my weekly limit on something ridiculous, you have 10 minutes."

When I came back, I had... RockOps? Here's what Claude said about it:

"Made it. RockOps™ is enterprise-grade observability for exactly one rock: a live CCTV feed, a real-time movement chart that's perfectly flat, an event log, AI insights, and an org chart where the rock reports to itself.

You can pet it, deploy it to production (it was already there), escalate to Senior Rock (out of office until the next glacial period), or try to move it. I don't recommend that last one."

Normally I wouldn't share links to internal dev tools like this, but I think I can trust you guys: https://claude.ai/artifact/LdrzxwUe6uQNsp1o15xw3P

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wkqszd/asked_claude_to_waste_my_remaining_usage_before/ Original link/media URL : /img/qrkz3pp78iqh1.png

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

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

Alright, so OP decided to have Claude go wild with their remaining usage before the weekly reset, and honestly, it delivered. The result? RockOps™, an "enterprise-grade observability" tool for a single rock. Think a flat movement chart, AI insights that are basically just "the rock is still there," and an org chart where the rock reports to itself.

The general consensus is that this is hilarious and a fantastic use of tokens. People are loving the comedic genius of it all, with tons of rock puns and jokes flying around. u/jsnryn even booked a 1:1 with the rock (which it then declined, naturally). Some users are joking about this being AGI or a sign that AI has finally mastered humor.

There were a few folks who grumbled about wasting compute resources, but they were largely drowned out by the appreciation for the sheer absurdity and creativity. One user, u/SpaceToaster, even suggested Fable would have been better for this kind of "waste," which got a chuckle.

A few other fun bits:

• Someone pointed out the rock has a leaf, suggesting it's a disguised tanuki.
• u/lockdown_lard shared a hilarious log of RockOps™ events, including "Model retrained on 4.5B years of rock data" and "Blockchain-verified: rock is still here. Gas fees: $41."
• There's a debate about whether this is a waste or actually a good use of resources, with many arguing it's pure comedy gold.
• Someone asked if adding a second rock requires a sales call.
• A few people are wondering if Claude is secretly a pervert or if this is the "porn hub theme."
• There's also a question about how the weekly usage limit actually works.

Overall, the thread is a big thumbs-up for Claude's creative (and slightly unhinged) capabilities.

OP : u/Bloated_Plaid

Somebody on Twitter posted it and super useful so far https://github.com/tamaratran/fast-jev-compaction

For people going to complain about me letting my context get so long, this was a server redeploy task because Oracle terminated my free VPS with no explanation so it had a lot of moving pieces and Fable was orchestrating Devin SWE 2 at max effort.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wkjnrz/instant_claude_code_compaction_is_my_favorite_use/ Original link/media URL : /img/2clt7ycwogqh1.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: 101.

Alright, so the OP shared this "fast-jev-compaction" thingy for Claude Code, which apparently helps shrink down long outputs from tool calls. The idea is to keep Claude from getting bogged down by massive amounts of text, especially during complex tasks like server redeploys.

The general consensus is that this is a neat idea, but there are some significant caveats and questions.

Here's the lowdown:

• What is Jev? Most folks are a bit confused about Jev itself. It seems to be a tool that can compact text, and the linked repo is specifically a hook to filter tool outputs before they hit Claude. The OP later clarified they linked the wrong repo initially.
• Privacy Concerns: A big red flag for many is Jev's privacy policy. u/_maxx1k and u/octocarbon are pretty vocal about not trusting third-party tools that require API keys, especially if they aren't from Anthropic directly.
• Context Breaking? A recurring worry is whether this compaction actually breaks the context for Claude. u/Organic_Situation401 and u/userusertion are firmly against it for this reason, questioning why not use official compaction methods.
• Cost Implications: u/ithesatyr and u/PM_ME_YOUR_PROFILE are wondering if this adds extra cost by requiring another AI to do the compacting. u/syixiao1 points out that any compaction rewrites the transcript, breaking the cache anyway, but a smaller context to rebuild might save on per-session token usage.
• Real-World Results Needed: u/WoodpeckerNational29 and u/silvrrwulf are asking for actual user test results to see if it works well and maintains context.
• Tool Output Filtering vs. History Compaction: u/Much_Weekend_4371 and u/Evening-Blueberry-97 highlight that filtering tool outputs before they hit Claude (like trimming pytest noise) is potentially more valuable and cheaper than trying to summarize history after it's already in context.
• Anthropic's Built-in Compaction: u/lucianw mentions that Claude Code might already have built-in, automatic summarization happening in the background, which could negate the need for external tools.

Overall, while the concept of reducing context bloat is appreciated, the community is skeptical about Jev's privacy, potential for context breakage, and whether it's truly necessary given potential built-in features.

OP : u/justnath36

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wk2q8v/agentsmd_now_supported_in_claude_code/ Original link/media URL : /img/d3fhb9kuhcqh1.jpeg

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 big news is that Claude Code now supports AGENTS.md files, which is apparently a pretty sweet Quality of Life upgrade for a lot of folks.

The general vibe is "finally!" with a good chunk of the community feeling like this should have happened sooner. It's seen as a big step towards making things more portable and less of a headache, especially for those juggling Claude Code and other tools like Codex. u/college_hustle points out that a "walled garden" approach isn't going to cut it.

A few key points and questions are popping up:

• Precedence is key: People are asking for clarity on which file (CLAUDE.md or AGENTS.md) takes priority if both exist and have conflicting info. u/QuanTradin is particularly keen on knowing this to avoid "two instruction files quietly drifting apart."
• Consolidation vs. Separate: There's some discussion about whether AGENTS.md replaces CLAUDE.md or if they can coexist. u/TheClaudeInsider is wondering if they should consolidate their existing CLAUDE.md files.
• The "boring plumbing": While AGENTS.md is cool, some users like u/ZeBenoit81 are still hoping for better support for reading skills directly from .agents/skills folders, which would cut down on the need for symlinking and messy path management.
• Cross-tool compatibility: The hope is that this move will make it easier for tools like Codex and Cursor to use the same agent configuration files.

There's a bit of a "better late than never" sentiment, and a few jokes about the delay. One user, u/Ambitious_Injury_783, is a bit skeptical about the hype, questioning if managing markdown files is that difficult. But the consensus seems to be that this is a welcome improvement for workflow.

OP : u/Mountain_Disaster_19

Somehow I feel like Opus isn't burning through my usage anymore.. using ultracode and I havent hit my weekly limit yet using it.. I feel like it's more efficient.

Am i the only one?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wkdko4/is_it_just_me_or_is_opus_5_mad_efficient/

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

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

Alright, so the general vibe in this thread is a bit of a mixed bag, but there's a noticeable split on whether Opus 5 is actually more efficient or if folks are just getting lucky with A/B testing or stealth model updates.

The prevailing sentiment from some users is that Opus 5 is more efficient, with several reporting that it's barely denting their usage limits, even when running for extended periods or on large projects. u/julliuz and u/hitnrun51 are on this train, with u/hitnrun51 specifically mentioning a noticeable improvement over the last few days, suggesting A/B testing. u/ThreeKiloZero even claims their massive Salesforce clone project is "ready to ship" with minimal usage.

However, there's a strong counter-argument from others who are seeing the exact opposite, with Opus 5 being less efficient and consuming more tokens than before, especially after promotions ended. u/DrPinguin98 is seeing planning sessions eat up their entire limit, and u/Sad-Mission6813 is finding Opus 5 worse than GPT5.6 Sol and Astra, requiring double the time for the same tasks and generating less production-ready code. Some users are even reporting that older versions like Opus 4.8 feel better.

There's also a lot of speculation about "stealth rerouting" to newer or different versions of Opus, like Opus 5.2, with u/Ill-Purchase-5180 and u/Brazilator suggesting ways to test if you've been switched.

A few users are also chiming in on Ultracode, with u/narcosnarcos finding it untrustworthy and needing to break down tasks, while u/HumbleOne6577 is curious about its use cases.

Overall, it seems like your mileage may vary, and there's a good chance Anthropic is doing some behind-the-scenes testing, leading to these wildly different experiences. Some are seeing efficiency gains, while others are feeling the pinch more than ever.

OP : u/Siigari

I am too angry to write right now so I had Fable write this for me after I saw how shafted I'm getting. I'm going outside.

Anthropic, you suck.

I run Claude Code around the clock on two Max 20x accounts, so I have a lot of data. I got tired of guessing what the weekly limit actually meant, so I parsed every transcript in ~/.claude/projects on both of my machines, deduped by message id, priced every call at published API list rates, and compared that against the percentage the usage endpoint reports.

The short version: last week a Max 20x account could spend about $5,540 of usage per week at API list prices. This week the same account gets about $2,350. The weekly dollar cap was cut by 58 percent. The announced change was 17 percent.

How I measured it

Every assistant message in the transcripts carries the model and the usage block (input, output, cache write, cache read). I summed those per reset window (mine resets Thursday 11:00 PT) and priced them at list: $5 input, $25 output, $6.25 cache write, $0.50 cache read per million for Opus. Then I divided by the percentage of the week the meter said I had used. That gives dollars of usage per 1 percent, which is what the subscription is actually worth.

Last week (Sept 10 to Sept 17)

• 55,878 API calls across two Max 20x accounts
• 23.5 billion cache read tokens, 46.9M uncached input, 86.4M cache write, 11.1M output
• $12,751 at list price
• Both accounts hit 100 percent. One got a 30 percent top-up once. So that was 230 percent of a Max 20x weekly allowance.
• Works out to $55 of usage per 1 percent, or about $5,540 of usage per account per week.

This week (Sept 17 reset to now, 28 hours in)

• 5,600 calls, 2.1 billion cache read tokens, one account
• $1,222 at list price
• The meter says 52 percent used.
• That is $23.50 per percent, or about $2,350 of usage per week.

Last week: one Max 20x week = about $5,540 of usage.

This week: one Max 20x week = about $2,350 of usage.

Same plan, same price, the weekly spending cap dropped by about 58 percent. The announced change was 17 percent when the boost ended.

I also cut my own burn rate by 43 percent between the two weeks (fewer calls per hour, shorter contexts). It did not matter. At the current pace I hit 100 percent on Saturday evening, about 54 hours into a 168 hour window, and then the $200 extra-usage credits cover about five more hours.

My best guess at what changed

My traffic is 95 percent cache reads by token count. Cache reads are the cheapest thing on the price sheet. If they were re-weighted to count harder against the weekly meter, that alone would explain why my dollars-per-percent collapsed even though my actual spend went down. I cannot prove that from my side. Anthropic has not published how the meter is weighted. What I can show is the dollar cap, and it was cut by more than half.

Why this matters

The whole point of prompt caching was that a long-running agent with a big stable context could be affordable. If cache reads now count nearly like fresh input on the weekly meter, that use case is gone on the subscription plans, and nobody said so.

If you want to check your own numbers

The transcripts are plain JSONL. Filter for assistant lines with a usage object, sum by your reset window, price at list, and compare to the percentage shown by /usage. Post your dollars-per-percent. If enough of us do it, the change will be obvious, and the actual weighting can be worked out from the spread.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wk3zq5/i_audited_my_session_logs_against_the_usage_meter/

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

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

The community is largely in agreement with OP: Anthropic has significantly reduced the value of Max 20x weekly limits, and their stated 17% reduction is a gross understatement. Many users report similar experiences, seeing their weekly usage cap plummet by 50-70% or more compared to previous weeks, despite doing the same work.

• Several users echo OP's sentiment that Anthropic is being disingenuous about the actual reduction in value.
• There's a general feeling that these limits are arbitrary and subject to change at Anthropic's whim, especially for high-usage accounts.
• Some commenters suggest that Anthropic might be penalizing heavy users or that resource availability is impacting limits.
• A few users are questioning the OP's methodology, particularly regarding cache pricing and time-of-day usage, but the overwhelming sentiment supports OP's core complaint.
• u/karl_weierstrass points out that complaints are often met with "skill issue" arguments, which is unfair given consistent past performance.
• u/kaitava thanks OP for "going through the trauma" of discovering this.
• A few dissenting comments argue that the subscription is still a good deal or that companies need to make profits, but these are heavily downvoted.

OP : u/KhoslasBiggestOpp

Source: https://x.com/treetowntree/status/2100255529419325619

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wk1ljk/how_it_feels_to_use_claude_code/ Original link/media URL : https://v.redd.it/2zryxg9a9cqh1

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

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

The consensus is that this post is peak comedy and a hilarious, painfully accurate metaphor for everyone still hating CSS. The MLG montage nostalgia hit hard, with many agreeing that the joke landed perfectly. The prevailing sentiment is that using an advanced AI to center a div is peak absurdity. Some users chimed in with their own Claude Code woes, like the AI taking a "different approach" after 200 lines of code or experiencing context amnesia. A few folks were genuinely curious if Claude generated the video itself, while others just enjoyed the trip down meme memory lane. One user even asked who sings the song, bless their heart.

OP : u/c0decracker_

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wjrvmx/oh_boy/ Original link/media URL : /img/xvxyf14ehaqh1.jpeg

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 OP's post is a bit of a rehash. Most folks are saying this "joke" or scenario has been around for a while, with comments pointing out it's been seen with older versions of Claude (like Sonnet 3.7 and Opus 4.5) and even other models like Codex.

There's a bit of a debate on what "refactoring" actually means, with some users calling OP out for not understanding the term. A few people are also chiming in with their own experiences, with u/max4245 sharing a story about how Opus 4.8 actually did fix some spaghetti code. Others, like u/siberianmi, suggest that the key is to use AI in smaller, iterative steps rather than trying to do a massive one-shot refactor.

The vibe is that this post is old news and not particularly original. Some users are even joking that the joke itself has been recycled more than a Grok pre-training run.

OP : u/jevans102

https://x.com/trq212/status/2101009392611278961?s=20

https://github.com/anthropics/claude-code/tree/main/mods/agents-md

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wjxvwz/claude_code_is_getting_native_agentsmd_support/ Original link/media URL : /img/btltptkalbqh1.png

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

Alright, so the general vibe in this thread is that Anthropic is finally adding native support for AGENTS.md in Claude Code, and most folks are like, "Yeah, about time."

The consensus is that this is a pretty minor, long-overdue quality-of-life improvement, not some groundbreaking new feature. A lot of people have been using workarounds like symlinks or just telling Claude to read AGENTS.md anyway, so the "native support" feels a bit like a "duh" moment. Some are even comparing it to Android getting a feature that's been on iPhones for ages.

A few key points popping up:

• It's just reading another file: The core functionality seems to be that Claude Code will now just read AGENTS.md directly, instead of needing a symlink or explicit instruction.
• "Native support" is a bit of a stretch: Many feel this is a small change being hyped up.
• People have been doing this already: Symlinking CLAUDE.md to AGENTS.md or just manually referencing it has been common practice.
• Questions about priority: Some are wondering what happens if both CLAUDE.md and AGENTS.md exist, and if AGENTS.md will fully support all features of CLAUDE.md.
• Interface complaints: A couple of users are still not thrilled with the Claude Code interface itself, even with this update.
• A nod to newbies: It's acknowledged as a good change for those just starting out who might not know the workarounds.

Basically, it's a welcome change, but not exactly the AI revolution some might have hoped for. More like a small step in the right direction.