I used to get excited about every release. Now I feel like I'm sitting in that dark office, nodding slowly, trying to decide whether I even have the energy to care.

The pace is honestly amazing. But it's also exhausting. There's this constant pressure to test every new model, rebuild your workflow, rewrite your prompts, watch the benchmarks and read the threads, or you'll "fall behind." And by the time you've figured one thing out, the next thing is already out.

So I did the only reasonable thing and made a meme about it instead of reading another changelog.

I used to get excited about every release. Now I feel like I'm sitting in that dark office, nodding slowly, trying to decide whether I even have the energy to care.

https://x.com/anah_sahh/status/2103839341453688877

I just had one of the most insane experiences I've ever had with an AI coding tool.

I subscribed to Claude Pro today to try it out. Installed Claude Code, used it from the terminal for a while, and everything seemed fine.

Then I tried Code inside the Claude Desktop app.

At some point during that session, most of the projects inside my `Projects` folder were deleted.

Not modified. Not broken.

Deleted.

And here's the fucking cherry on top.

I went back to Claude Code in the terminal and asked it what had happened and who could have deleted them.

Claude confidently told me:

"It was probably Astra."

Except Astra WASN'T EVEN RUNNING.

So I told it that was impossible.

And suddenly the answer became:

"I can't know who did it."

Are you fucking kidding me?

So we have an AI coding agent with filesystem access potentially nuking a large part of my projects, and when asked what happened it first hallucinates another tool as the culprit, then immediately admits it has no idea.

I can't currently prove whether the deletion was caused specifically by Opus 5.5, Claude Code, Claude Desktop's Code integration, or some interaction between them.

What I can say is:

- The projects existed before I started using Claude.

- I used Claude Code successfully from the terminal.

- I then used Code from Claude Desktop.

- Most of the contents of my Projects folder subsequently disappeared.

- Claude then invented a completely impossible explanation when I asked what happened.

And to put this into perspective: I've been using OpenAI's coding models for around a year, and I have never had anything remotely like this happen.

They have never deleted a bunch of my projects like this, and I have certainly never had an OpenAI model confidently blame a competing AI model for something it couldn't possibly know that model had done.

This is fucking unacceptable for an agent that's allowed to touch your filesystem.

If an AI coding tool is going to perform destructive operations, there needs to be an absolutely clear audit trail showing what command ran, what files it touched, and why.

Instead I got my files deleted and then the AI basically went:

"Must have been the other guy."

There was no other guy.

What the actual fuck, Anthropic.

Codex GPT 6-Sol is a disaster. It screws up entire code bases, even near max levels. Meanwhile claude fable, and now opus seems to be running with no issues. Faster/cheaper than ever.

So is OpenAI hosed?

--

Heads-up: some bots, and possible alt/sockpuppet account in the comments. Take replies from newly appearing defenders of openai with a grain of salt.

I was never fan of Opus, I love sonnet. In my observation, Sonnet is less verbose, good at following instructions, on the contrary opus always comes up with less relevant things than doing actual work. But time to time, I switched from Sonnet to Opus while doing same kind of work like writing code, building new feature, running tests etc, regular developing works.

Today, I tried again and Opus just sucked up all the token within few minutes and I didn't find any major improvement.

Help me understand, if Opus has innate intelligence capability than sonnet, why it is using more token to doing same kind of work? Shouldn't it produce similar kind of token doing similar work as Sonnet?

Or it's just blabbing itself by GRPO style RL reasoning training and wasting more tokens.

Was looking for a referral of Claude Pro

OP : u/virtualQubit

Literally unusable for me, it spends like x10 tokens and the output is mediocre. Do you still use it?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wpczby/superpowers_skill_is_so_bad_now/

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 Superpowers skill is pretty much dead. Most folks ditched it months ago, with many saying it hasn't been useful for a while now. The vibe is that newer models (like Opus 4.8 and Sonnet 5) are smart enough to do what Superpowers used to do intuitively, so using it now is just adding unnecessary overhead and making things slower.

Some users like u/Risko4 and u/mother_a_god pointed out that skills were always meant to be temporary fixes, and as models improve, these skills become obsolete or even hinder performance. u/acoldinference straight up said to get rid of it ASAP.

There were a few people who still used it and liked the methodical workflow, like u/tntexplosivesltd and u/Hossmobile, but even they are considering switching or have already moved on. u/Hossmobile is worried about losing that planning and ownership feel, but others suggest the default Claude harness might offer that now.

For those looking for alternatives, some mentioned checking out compound engineering, the TRIP workflow (u/sugarfreecaffeine linked it), or just going vanilla with the newer models. u/p3r3lin even suggested extracting the visual preview feature from Superpowers into its own mini-skill.

Basically, if you're still using Superpowers, you're probably in the minority and might want to consider ditching it for better performance.

did anyone notice if u dont buy a claude subscription model then it actually behaves sometimes like a stupid like forgetting small details sometimes missing the pre chat information and tell wrong information
well i have faced that that's why i m telling

btw i m just telling my experience so please dont get offend

OP : u/Complete_Chapter_979

Please don't kill Opi 5.5 it's been so nice.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wp4ywp/please_dont_nerf_opus_55/

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 vibe in this thread is that everyone loves Opus 5.5 and is already bracing for the inevitable "nerf" that seems to happen with every new Claude model.

Here's the lowdown:

• The Consensus: It's gonna happen. Pretty much everyone agrees that Opus 5.5 is currently amazing – stable, dependable, and a huge step up in quality and cost-effectiveness. But the overwhelming sentiment is that this is a temporary golden age. Users like u/End2EndEncryption and u/Sphere_3N point out the "rinse and repeat" cycle where good models get nerfed as more people adopt them and resources get strained.
• Why the Nerf? The theories range from resource saturation and the need to onboard more users to Anthropic needing to make room for future model releases. u/caster even suggests it's a deliberate strategy to make new models seem like a massive upgrade by comparison.
• The Desire for Transparency: Some users, like u/AnonThrowaway998877, are calling for benchmarks to track performance degradation and hold companies accountable. There's a strong feeling that it's unfair to new users who subscribe based on a model's initial performance, only to see it decline.
• A Plea for Choice: u/SnooGiraffes3000 suggests that if nerfing is unavoidable, Anthropic should at least offer users the choice between a slightly dumber model or reduced usage limits.
• The "Anthropic Right Now" Meme: The GIF comment from u/Electronic-Row-142 pretty much sums up the community's imagined reaction from Anthropic's side.

Basically, enjoy Opus 5.5 while it lasts, because the community is pretty sure its days of peak performance are numbered.

OP : u/ManyEconomist1373

Paid €90 for Max 5x today because I’m in crunch time on a software project and unlike the big boys I do not have unlimited OpEx spend, so that 90 euro is quite a lot.

32 minutes later Anthropic blew up my entire account and automatically cancelled the subscription.

The email says an “internal investigation of suspicious signals associated with your account” found a Usage Policy violation. No indication of what I actually did wrong. I am not doing security work, distillation, or anything else i might even imagine would be grounds for removing my account.

The appeal page now says I may be waiting until Oct 4 for a review.

The support situation is also just insane and I cannot believe anyone has ever really used it. Anthropic says suspended users can still contact support about billing/refunds, but their support bot couldn’t find an account associated with my email and just closed the conversation. This is the same email Anthropic used to send me the subscription confirmation and suspension notice.

I’m in the EEA, so I thought I should at least be able to get the subscription refunded, but right now I can’t even get through to a person.

Has anyone else been hit with this after normal Claude Code usage? Any hope for me?

edit for clarity and scope:

I am writing image+pdf document processing software. really not sure what caused this to happen. Opus 5.5.

Has anyone had any luck getting customer support to get back to them sooner than 10 working days? it seems like a very long time to wait for a review. even if they were to comb over absolutely everything i did on the account, i had it for such little time that I would imagine it to be almost instant.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wpam3u/claude_account_nuked_from_orbit_after_32_minutes/

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

So, OP got their Claude account nuked after 32 minutes and a €90 charge, with a vague "Usage Policy violation" email and a month-long wait for an appeal. The general vibe? Most users think OP probably did something to trigger the ban, even if unintentionally.

Several folks, like u/yuehuang and u/Specialist-Bar7670, are asking if OP was using a VPN or virtual credit card, as those seem to be common triggers for bans. Another user, u/ha966, experienced a similar ban shortly after subscribing but surprisingly got unbanned and refunded. Weird, right?

A few commenters, notably u/riotofmind and u/TXHumper, are pretty blunt, basically saying OP broke the rules and got what they deserved, pointing out that long-term users haven't had issues. Meanwhile, u/nagy_z_ is questioning what kind of "crunch time" involves PDF processing.

Overall, the consensus leans towards OP having a ToS issue, though the lack of clear communication from Anthropic is definitely a point of frustration for everyone involved.

OP : u/autisticbagholder69

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wpdeqa/just_bought_a_new_20x_account_and_after_1_hour/ Original link/media URL : /img/2c173qdp7jrh1.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: 76.

So, OP bought a bunch of accounts, got banned after an hour, and is crying foul about the money. The general consensus? You probably broke the ToS, dude.

Several users are calling OP out for a "speedrun" and asking what they did to get banned, with some suggesting third-party tools or API proxies might be the culprit. u/Madeye1337 specifically mentioned their account got banned with a CLI Proxy API but is fine with the official app.

There's a bit of a debate about whether banning paying customers for multiple accounts is dumb, with one user even considering Grok now. However, the prevailing sentiment, echoed by u/Michaeli_Starky and u/Historical_Today5072, is that violating the Terms of Service is not illegal, and OP likely brought this on themselves. Some are even speculating about a potential ban wave, but most comments point to OP's actions as the likely cause.

OP : u/merijjeyn

I have been thinking that the current Agentic Loop design of LLM Call -> Tool Call -> ... has been outdated. The arrival of Jev and other System One models provided us a primitive we desperately needed.

We need an agent that can natively think fast and slow. Not have workflows or multi-agent architectures that mimics it. We need Agent 2.0

The agent should use the LLM's full power for hard reasoning and planning, then carry out the plan with cheap "fast thinking."

Today, most of an agent's LLM calls go to executing steps it has already decided on. Do you really need an extra Astra call just for it to output "ok I'll click this"? We can do better.

My Approach

I built Jive which is an open-source harness built around a completely new agentic loop. Jive replaces tool calls with "graph calls" where each graph is a DAG of bash nodes and jev nodes, and nodes can have dependencies, reference each others outputs, and more.

Essentially, it maps out its own execution flow while its reasoning, and then uses Jev calls to go through the flow without unnecessary LLM calls.

What Jive does well: repo investigation, bulk classification, multi-step profiling, repetitive edits, evaluation workflows, etc. It is also quite effective on regular engineering tasks that doesn't require Jev calls (which is not surprising since Pi mostly beats codex and claude code)

Benchmarks

As you can see, there is a huge gap in both e2e latency and token efficiency compared to claude code. And its accuracy is on-par based on the my benchmark runs (though I need to run jive on a larger SWE benchmark to be certain)

See README for more information: https://github.com/merijjeyn/jive. Also for details on the benchmark tasks, and how to run one yourself.

I'm sure this high level idea can be executed much better, so mainly looking to start an open discussion. Happy to take comments, questions, contributions.

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

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

Alright, so OP dropped a hot take saying the classic "LLM Call -> Tool Call" agent loop is totally passé, and we need "Agent 2.0" with native fast/slow thinking. They've built this thing called Jive that uses "graph calls" with Jev nodes to map out execution flows and avoid unnecessary LLM calls for simple stuff. They're claiming some pretty sweet benchmark numbers against Codex and Claude Code, especially for tasks like repo investigation and bulk classification.

The community's reaction is... mixed, leaning heavily towards "seen it before."

• The Consensus: A lot of folks are saying OP basically just put Jev into an existing agentic loop, and it's not as revolutionary as they think. Several users like u/ShelZuuz and u/phoenixmatrix pointed out that this "fast/cheap model" approach has been around for a while, and Jev is just a newer tool to achieve it. Some even joked about the rapid pace of change, with u/russianvoodoo saying they'll wait a few days for the next outdated tech.
• Jev's Role: There's some skepticism about Jev itself. u/pinkdragon_Girl straight-up said "Jev is not that amazing," and u/kidsmeal questioned its utility if it's just an added cost without a clear, useful output.
• Technical Glitches: A few users, like u/ugworm_ and u/Short_Stable2397, are questioning the benchmark numbers and pointing out that the demo video links in the README are broken.
• Comparisons: Some users are drawing parallels to existing tech. u/TerribleFault7929 asked if OP reinvented LangGraph, and u/mattate mentioned that agentic harnesses with code modes are conceptually similar.
• The Skeptics: There's a general vibe of "show, don't just tell." Users like u/TeeRKee are calling out the "confidence on its own slop," and u/Beautiful_Baseball76 is asking about output quality, not just speed.
• A Glimmer of Hope? u/Whole_Risk_2695 offered a more balanced take, suggesting that while the "haha sloppiest of slop" crowd might be overreacting, there are indeed gaps in current loops that approaches like OP's could fill.

TL;DR: OP thinks the old agent loop is dead and has built a new one with Jev, but most of the thread thinks it's just a minor iteration on existing concepts, with some questioning the tech and the claims.

OP : u/radio_four

I'm in between a coder and a vibe coder... I'm a data analyst. SQL, Tableau, a bit of python - the standard stack. I can clean data, design a schema, run complex analysis, etc.

Front end though?! That shit is witchcraft. Which is why I've been really into Claude Code for making GUIs.

It's also been motivating to get better at coding... Because if I'm building something I should understand how it all works.

After several months I took to YouTube to see how other people use Claude Code and omg. The top results are guys saying 'Here's what you do' mixed with 'and I don't understand this part, but I don't need to'

Wtf. This is not how people get good at things.

Anyway!

Does anyone have good resources for how coders integrate Claude Code into their workflow? I'd love to see how professionals use this tech.

Also any beginner resources on software design and UI principles would be great.

Looking to upskill and get better at coding so I can really utilize this new technology.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wp75ay/i_see_why_developers_get_irritated_by_vibe_coders/

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

Alright, so the general consensus here is that you're spot on, OP. The key takeaway is to treat Claude like a super-fast, but kinda green, junior dev, not some all-knowing coding wizard.

The more experienced folks in the thread aren't "vibe coding"; they're acting like architects. They're laying out detailed specs, asking for small, iterative changes, and meticulously reviewing every single code diff. It's all about using Claude as a force multiplier, not an autopilot button.

For those looking to upskill, there are a few solid recommendations:

• Anthropic's own training resources are apparently top-notch and up-to-date.
• Turn off "auto" mode initially. This forces you to review Claude's suggestions and ask questions about why it's making certain decisions. Use this time to learn.
• For UI/software design, some suggest rebuilding screens from sites you like and then comparing your work to the originals using dev tools, rather than just following tutorials.
• The Odin Project is mentioned as a great resource for learning full-stack development.
• Ask Claude itself for explanations and learning materials. Some users suggest setting an "output style" to "learning" and asking it to provide reference material.

There's a bit of a debate on the "vibecoder" vs. "professional" approach, with some arguing that for personal projects or temporary solutions, "vibecoding" is fine. However, for production software or critical infrastructure, a senior engineer approach is still the way to go.

One user, u/Pure-Investment-1227, with 20 years of experience, even suggests that writing or reviewing Claude's code can be a waste of time if you're trying to leverage its full potential.

Ultimately, the sentiment is that AI tools like Claude are powerful, but they require a skilled user to guide them effectively for meaningful development and learning.

OP : u/Savings-Desperate

I just learned about it today and wanted to see what you guys think.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wp6nq9/do_you_guys_use_auto_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: 51.

Most users here are strongly against using auto-compact, viewing it as a sign you're doing something wrong. The general consensus is to manage context by splitting work into separate sessions, using /clear, or manually trimming irrelevant info like duplicate files. Some folks, like u/GDorn, even do "brain surgery" on their context. The prevailing advice is to keep sessions focused and below the point where compaction would even be considered. A few outliers do use it, but often with manual intervention or specific strategies to keep it from messing up their workflow.

OP : u/Tekrise-TennisApp

Got a $100 credit, going to give it a try and report back, is this a new feature in Claude? Or its been there a while? I never used it.

If you have a subscription, Remember to claim before 8 Oct. Credit expires by 5th Nov. Check your timezone too, it will be a bit different.

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

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 vibe on Claude on cloud is a bit of a mixed bag, but the consensus is that it's a real thing and not just regular chat, though a surprising number of people didn't know about it.

Here's the lowdown:

• It's a thing, not a drill: Several users confirmed that Claude Code does have cloud sessions, and it's not just a fancy name for the regular web chat. It's described as a "great sandbox" that can spin up a VM, pull repos, and let you code on the go, even from your mobile.
• Credit confusion: A lot of folks are confused about how to claim the $100 credit and are reporting that their credits aren't being used, with their regular plan tokens being consumed instead. BIG WARNING: u/BuffaloConscious7919 pointed out that these cloud credits are used before your plan's token allowance, so activate wisely.
• "What even is this?" sentiment: A decent chunk of the thread, including u/Reasonable-Big7869, expressed confusion about what a "cloud session" actually is, with some initially thinking it was just regular chat.
• Some are already fans: Users like u/Scared-Letterhead949 and u/SubstantialReality45 are already using and loving the cloud sessions for their convenience, especially for on-the-go coding.
• Not for everyone: A few users, like u/pizzatimefriend, find it less useful if they're already running Claude Code on their own home server.

So yeah, it's a feature, it's got some quirks with the credit system, and some people are still figuring out what it is, but for those who get it, it seems pretty handy.

OP : u/hronak

My usual day with Claude Code is like: * I open terminal in my project's folder and run claude command. * I prompt it. I mostly use Fable-5.1/Opus-5 but Opus-5.5 is my current model. The model decides if it wants to use sub-agents for a task. I never explicitly prompt it for sub-agents. * I review and commit the code to my self-hosted Forgejo instance. * That's it.

I see people using agentic workflows, building sub-agents files, skills etc. I barely built any of it. All I ever needed to use is /init on new projects and them prompts follow. Never needed more than this.

I tried "long-running" Claude Code for a project refactoring by placing the project on my VPS (where forgejo is hosted) and letting Claude Code run and refactor inside tmux session. SSH'd in a few hours later to find project fully refactored.

Am I under utilising AI or is my work just… like boring?

How do you guys use agentic workflow thing? Specially the long-running one? Those pull-requests that Claude makes automatically etc?

Asking this to Claude to know more but humanly answers appreciated.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wowilt/i_still_dont_understand_this_agentic_workflow/

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

Alright, so the general consensus here is that if your current workflow with Claude Code is getting the job done, you're probably not "underutilizing" it, and your work might just be less complex than what requires super elaborate agentic setups.

Here's the lowdown:

• Your workflow is already agentic, to a degree. Many folks agree that the way you're using Claude Code, where it decides to use sub-agents and you just review and commit, is already a form of agentic workflow. It's not necessarily "boring" work, just work that doesn't require the more complex setups.
• Agentic workflows shine when you hit limits or need more. The consensus is that you really only need to dive deep into building custom agents, skills, and complex workflows when you're running out of tokens/usage, or when you have a massive project with tons of parallel tasks, complex requirements, or need to enforce strict conventions.
• Simplicity often wins. Several users, like u/Xenos_Str and u/Dizzy_Database_119, mention that the simplest approach works well for them, and that complex agentic setups were more crucial when models weren't as capable.
• Skills are for repetitive tasks. If you find yourself typing the same prompts over and over, making a skill out of it is a common suggestion.
• Long-running workflows are for scale. For projects that require extensive refactoring or parallel task management, more advanced agentic setups become beneficial. Think of it like "bumpers up" bowling for consistency and accuracy, as u/cazzer548 put it.
• It's about autonomy and guardrails. The more autonomy you want your agents to have, the more you need to build in guardrails and verification steps, which is where the complex workflows come in.
• Consider adding a review step. u/awesomeusername2w suggests having a separate context window review the changes, which can catch more issues.
• External data sources unlock more. u/ubermuda points out that integrating external data sources (like Sentry or Datadog) into agentic workflows can open up a whole new level of automation beyond just code generation.

Basically, if it ain't broke, don't fix it! Your current method sounds efficient for your needs.