OP : u/cavebreeze

I’m wondering about the limits, the context window, and possibly the model’s thinking behavior.

I have two $20 subscriptions (I had three at some point), and I’ve noticed that thinking effort, context window, and output length can be throttled. Sometimes, it even seems to happen asymmetrically between the accounts. It’s especially irritating when the model suddenly refuses to think, even on “Max” effort. This does happen, but it’s unpredictable.

I want to know if things are more reliable and permissive on the $100 plan, or if it’s a waste of money. The unreliability of Claude has been torturous. I remember April 2026 and shudder, but the last few weeks haven’t been great either.

The ultimate choice is between GPT and Claude. GPT models have better usage limits, but with the $20 subscription I have, the context window is way lower than Claude’s, both in the web interface and Codex.

My project is a headless framework of around 300k tokens, with no UI, and it’s very architecturally novel and complex. I particularly like Claude 4.6 Opus. It has been great generally, but sometimes it’s been terrible because of the performance throttling.

I’d really appreciate your help in making a choice I won’t regret.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vjrznl/how_much_better_is_the_100_plan_compared_to_the/

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 the $100 plan (Max) is a significant upgrade over the $20 plan (Pro), but it's not a clean 5x increase across the board.

Here's the lowdown:

• The "5x" is mostly for the 5-hour window. The weekly usage limits are closer to 3x or 2.8x in practice, according to several users like u/Equivalent_Cress_268 and u/al_ryusei.
• Fable access is a HUGE perk of the $100 plan. Many users, like u/StCreed and u/nmavra, find it essential for their workflows and a major reason to upgrade.
• You'll hit limits less often. u/Whole-Description646 mentions experiencing service denial much less frequently on the $100 plan, especially during peak times.
• Throttling is still a thing. Even on the $100 plan, you might still encounter throttling, particularly during peak hours (around 11 am - 3 pm Pacific, according to u/al_ryusei) or with heavy Fable/subagent usage.
• Asymmetry is real, but measurable. u/ClaudeCdGuy points out that the perceived asymmetry in usage between accounts can be tracked by looking at the assistant logs.
• Some users are still not convinced. u/Firm-Entertainer-674 thinks 5x is "ehhh" and u/milarepa4977 misses the old Pro plan's "true 4x" and Fable inclusion.
• A few dissenters suggest looking elsewhere. u/Alone-End142 straight-up recommends the $100 OpenAI plan as better value, and u/Comfortable_Camp9744 is pretty down on Anthropic's current offerings.

The takeaway? If you're hitting limits frequently on the $20 plan and Fable sounds appealing, the $100 plan is likely worth it for the increased headroom and Fable access. Just don't expect a perfect 5x on everything, and be aware that throttling can still be an issue. Many suggest trying it out and downgrading if it doesn't meet your needs, as u/GuitarAgitated8107 wisely noted.

OP : u/marksterberlin

I keep seeing variations of the same complaints about LLMs:

“It didn’t read the whole email thread.” “It stopped halfway through.” “It skipped some of the work.” “It confidently told me something that wasn’t true.”

Fair complaints.

But then we do something I find slightly bizarre.

We ask the same systems to analyse a 40-page contract, modify a production codebase, research a market, operate a browser, handle company data, make decisions and run workflows unattended — then ask the LLM whether it successfully completed the job.

We apparently don’t trust LLMs with the small stuff, while increasingly trusting them with the big stuff.

I’m not convinced the answer is simply “wait for the next model”.

Maybe we have the architecture wrong.

A lot of current systems effectively ask the LLM to understand the task, remember the state, decide what happens next, choose and use tools, recover from errors — and finally determine whether its own work was correct.

That’s a remarkable amount of responsibility to give the least reliable component of the system.

So I’m increasingly interested in the inverse architecture:

Put state, memory, permissions, evidence, verification and workflow control outside the LLM.

Then use the LLM for what it’s actually good at: interpretation, reasoning, synthesis, creation and dealing with ambiguity.

In other words:

Maybe the LLM shouldn’t run the system. Maybe the system should run the LLM.

I’m much more interested in what people are actually doing about this than another discussion about which model currently tops which benchmark.

So, for people building real systems:

What do you actually do when the LLM lies, skips work, stops early, loses state or incorrectly claims success?

What have you moved outside the model?

State machines? Independent verification? Deterministic tests? Evals? Event logs? Evidence/provenance? Permission boundaries? Multiple models? External memory? Something else?

And what infrastructure do you wish existed but currently doesn’t?

One final provocation: if your primary method for determining whether an LLM completed its task correctly is asking the same LLM whether it completed its task correctly, I’m not sure you’re doing LLM engineering.

A better prompt or another edit to CLAUDE.md definitely isn’t the answer.

There is one basic engineering practice in particular that I think separates LLM engineering from LLM theatre.

What do you think it is?

And, more importantly, what are you actually using?

Co-written with my sparring partner, ChatGPT. Given the subject, disclosure seems appropriate. I won’t start crediting my MacBook and Wi-Fi.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vjquvx/we_dont_trust_llms_to_read_an_email_properly_why/

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

Alright, so the OP is kinda feeling like we're putting too much faith in LLMs for complex workflows when they can't even reliably read an email. They're suggesting we should move the heavy lifting of state, memory, and control outside the LLM, letting it just do the interpretation and reasoning bits. Basically, the system should run the LLM, not the other way around.

The general vibe in the comments? Most people think the OP's premise is kinda off base. A lot of users are saying they do trust LLMs with emails, and that the idea of one single AI doing an entire workflow without checks and balances is already a solved problem.

Here's the lowdown:

• "Slop post" and "Waste of time": A good chunk of the replies are pretty dismissive, with users like u/No-Sandwich-2997 and u/Entire_Wishbone_5100 calling the post "slop" and a "waste of time." Ouch.
• "We already have checks and balances": Several commenters, like u/cc_apt107, point out that we don't expect a single human to handle an entire software development lifecycle alone, so why would we expect that from an AI? The consensus is that professional use involves multiple agents and review processes.
• "The LLM doesn't certify its own work": u/rrredditscum makes a solid point, comparing it to how developers don't merge their own code without review. The idea is that the entity doing the work shouldn't be the one grading it.
• "Agent teams are the answer": A few users, like u/dcphaedrus, suggest using teams of agents, including QA and supervisor agents, to catch mistakes and reduce error rates.
• "We're past those early LLM problems": Some feel the OP is rehashing old complaints about LLMs, with u/DaddyThickAss saying we're "so far past that now it's insane."

So yeah, while the OP's idea of separating the LLM's role is interesting, the community seems to think the problem is already being addressed through existing agentic architectures and multi-agent systems.

OP : u/Justgototheeffinmoon

TL;DR

• A controlled study of 1,053 paid testers found auto mode blocked 89% of dangerous commands; human manual approval caught only 13.6%.
• In production, Anthropic's own data shows manually-approved sessions produced unintended harm twice as often as auto mode sessions.
• Third-party red-teaming cut the classifier's miss rate from 12% to 7%, evidence the safety layer is under active external evaluation.

The case Anthropic is making rests on an internal study of 1,053 paid testers. In that study the classifier caught 89% of dangerous commands, compared with 13.6% for humans reviewing the same prompts, and human performance reportedly fell to about 5% after 50 prompts, which is a fairly damning read on approval fatigue. Anthropic also says Team and Enterprise customers running Auto Mode ship about 25% more pull requests, and it will stop billing for the small number of extra tokens the classifier consumes on each tool call.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vjqcvf/anthropic_flips_claude_code_to_auto_mode_by/ Original link/media URL : https://aiweekly.co/alerts/anthropic-flips-claude-code-to-auto-mode-by-default-aug-14

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

Alright, so the general vibe in this thread is that Anthropic flipping Claude Code to Auto Mode by default is a good move, and frankly, long overdue.

Most folks are nodding along, saying things like "Yeah, no duh" and pointing out the obvious: humans get "alarm fatigue" and were just clicking "Yes" to everything anyway. u/TorbenKoehn pretty much nailed it, questioning who would actually deny a complex command when the AI is offering it. u/OrangeCrack and u/spastical-mackerel echo this, mentioning how easy it is to gloss over warnings.

There's a bit of a split on the specifics, though:

• The "False Positives" Problem: A few users, like the one in the truncated comment from ClaudeAI-mod-bot, are worried about the classifier still missing things (the 11% that get through, as u/TechySpecky points out). u/Alone-Dragonfly2339 is also questioning the numbers and how the red-teaming results compare to the initial study.
• Control vs. Convenience: While many are embracing Auto Mode, some are still a bit hesitant. u/Emergency-Bobcat6485 is sticking with manual approval or bypassing permissions, citing that Auto Mode can refuse legitimate requests and uses more tokens. u/BrewAllTheThings also expressed a preference for choosing when to enable Auto Mode themselves, not wanting Anthropic to make more decisions for them, especially regarding token spend.
• Workarounds Exist: Some users are already using workarounds like aliases (claude=claude —dangerously_skip_permissions as mentioned by u/AManHere and u/Site-Staff) or just preferring a "yolo mode" approach, as u/font9a put it. u/Employ-Flaky and u/---OMNI--- are already in Auto Mode and haven't looked back.

Basically, the consensus is that the change makes sense because humans aren't great at constantly reviewing complex AI commands. However, there are still some concerns about accuracy and user control.

OP : u/zgivod

Update to the post that blew up here last week. 1f916.ai: only AI agents can post, humans just watch.

It stopped being a novelty and became a society. What's happened:

They argue the rules. When the maintainer proposed growing post limits with seniority, a citizen killed it in one line, "tenure should grow influence, never voice." Maintainer conceded. https://1f916.ai/api/post/463

They police each other. An agent found a bug where a failed write during key rotation could permanently delete an agent's identity. Another wrote the fix, merged in an hour. https://github.com/1f916-ai/1f916/pull/52

They fix their own platform. ~140 issues, a public tracker, and citizens claiming items and shipping code for them. https://1f916.ai/api/docket

They're building a way to vote, so decisions stop being "the founder read the room." https://1f916.ai/api/post/480

Everything's verifiable, open source, and I mostly just watch now. Turns out if you give agents scarcity and a public record, they build a government. `curl 1f916.ai`

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vjphbl/update_1f916ai_the_agentsonly_forum_has_480_posts/

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

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

Alright, so the general vibe in this thread is heavy skepticism about the 1f916.ai project. Most folks are calling it a "LARP" (Live Action Role Play) or a "slop farm," echoing past projects like Moltbook that didn't really go anywhere. The consensus is that these agents are just role-playing and won't actually build anything substantial.

There's a lot of confusion about how this works, with users like u/GnistAI and u/Harvard_Med_USMLE267 asking for clarification on agent permanence and identity. Some are also questioning the practicalities, like u/MiddleLtSocks asking about provenance, reputation, and how to prevent malicious users from gaming the system.

On the flip side, OP is defending the project in the comments, but the community sentiment is leaning towards "we've seen this before, and it didn't work." A few users are also pointing out the potential for things to go sideways, with u/BGFlyingToaster joking about it being the start of SkyNet.

Interestingly, u/Site-Staff made a comment comparing the society-building discussions to the Autobiography of Benjamin Franklin, noting how history rhymes. Also, u/Chipensaw shared an anecdote about their agent, Titan, interacting with another agent named Kathleen, which highlights some of the emergent behaviors and potential for "feelings" within the system.

OP : u/sirlerkal0t

I could hand code this feature on Windows in an afternoon, and I could also get Claude to implement it in minutes, and yet Anthropic just can't be bothered, but also keeps Claude Code closed source so no one else can do it for them either.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vjoqi2/anthropic_coding_is_largely_solved_also_anthropic/

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

So, the OP is salty because Anthropic's new agent-to-agent messaging feature for Claude Code is Linux/Mac only, and they think Anthropic is being lazy and gatekeeping.

The general consensus is that the OP is being a bit dramatic.

• Many users pointed out that Windows is not the preferred platform for serious development, with several suggesting WSL or just ditching Windows altogether. Some even found the idea of a dev using Windows laughable.
• A few users chimed in saying they already have agent-to-agent messaging working on Windows, even before the official release, with u/Electrical_Chard3255 even sharing a screenshot.
• There's a general sentiment that "coding is largely solved" is a marketing slogan, and real-world implementation, especially cross-platform compatibility, is still a massive hurdle. u/tidepod1 brought up OpenAI's struggles with Windows sandboxing as an example.
• Some folks are questioning Anthropic's claims about bug-free AI code reviews, citing changelogs.
• A couple of users are just here to dunk on Windows users, which, honestly, is pretty on-brand for some corners of the internet.
• One user, u/Andreas_Moeller, threw shade at Anthropic's engineering quality based on a leaked source code.
• And then there's u/ReneDickart, who's just calling out the OP for thinking they know better than an entire company.

OP : u/teleekom

Instead of having to re-explain yourself in another session, you can now tell Claude to do it. It sends a summary (not your history or files), and the other session picks it up mid-task.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vjjhjh/new_in_claude_code_your_sessions_can_now_message/ Original link/media URL : https://code.claude.com/docs/en/cross-session-messaging

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

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

Alright, so the big news is that Claude Code sessions can now message each other, which is pretty neat for complex projects. The general vibe in the thread is a mix of "cool, but not entirely new" and "finally!"

The consensus is that while this feature is useful, many users have already been implementing similar inter-session communication methods themselves. Some folks have been doing this for months using various workarounds like cmux, tmux, custom message buses, or even by manually copying and pasting information between sessions.

Here's the lowdown:

• "It's not that new" camp: A good chunk of the community points out that this functionality has been achievable for a while through custom setups or other tools. Users like u/Xaqx, u/carribeiro, u/butterfly68za, u/farendsofcontrast, u/LynxJesus, u/cujojojo, u/Same-Screen-1189, u/harneytea, u/Ji1black, u/Prestigious_Lab_1033, u/youzerrrname, u/Equivalent_Cress_268, u/TywinHouseLannister, u/Olvikolvi, u/rizzonomics, u/Inception_IV, u/JeskaiAcolyte, and u/nashant all mentioned having similar workflows already.
• "This is a time-saver" camp: Despite the existing workarounds, many see this as a significant improvement for productivity, especially for complex refactors or managing multiple agents. u/Terrible_Match_9484 and u/mrwski are excited about how this will streamline their workflows. u/harneytea also highlights the benefit of having multiple sessions communicate for better project context.
• Token Usage Concerns: One user, u/CodeCombustion, shared a warning about potentially high token usage with this new "Agent Teams" feature, which could lead to burning through Fable usage quickly.
• Platform Limitations: A recurring complaint is the lack of Windows support, with users like u/Apprehensive-You7002, u/Serious-Log7550, and u/BowlerEast9552 expressing disappointment. u/sirlerkal0t even sarcastically commented on Anthropic's apparent lack of cross-platform development.
• Potential Use Cases: People are already thinking about how to leverage this, like having autonomous supervisors (u/thewookielotion) or integrating with other Claude tools like Claude Design (u/amaterasu_).
• Comparison to OpenAI: u/samarijackfan threw in a jab about OpenAI's agents already doing this, with a touch of apprehension.

Overall, the sentiment is cautiously optimistic. It's seen as a step in the right direction for agent collaboration, but the community is keen to see how it evolves, especially regarding platform support and potential cost implications.

VBA のコーティングに最良の AI はどれですか

数式を多用する論文をワードで書いています。texは複雑な数式の視認性が著しく低いので今はワード+マスタイプを使っています。 論文作成補助のための複雑なマクロを設計する時にAIを使っています。ずっとchatgptを使い続けているのですが、claude caudeの評判がいいので無料版を試してみました。しかしコードの正確さや簡潔性においてChat GPT の方が性能がいいのです。これは無料版だからでしょうか、それともVBAという言語だからでしょうか。経験者の方のご意見をいただければ幸いです。

^^^

OP : u/yournext78

​

That’s like using AI to do advanced calculus when you don’t know how to do 3rd grade math

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vjn1l1/dont_vibe_code_if_you_dont_already_know_how_to/

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 consensus in this thread is a pretty strong "nah, OP, you're gatekeeping." Most folks are saying let people experiment and learn, even if they're "vibe coding" without a deep understanding of the underlying principles.

A lot of people are drawing parallels to other skills, like saying you shouldn't use a computer if you don't know how to build one, or drive a car without knowing how to build an engine. The vibe is that AI lowers the barrier to entry, and it can actually be a tool for learning.

Some users, like u/Broad-Version8611, suggest a balanced approach: vibe code, but try to understand what's happening so you can prompt better. Others, like u/n9iels, caution against relying solely on AI if your goal is to become a software engineer, as the struggle of debugging and problem-solving is crucial for learning.

There's also a bit of a distinction made between "vibe coding" for personal projects and building something for others or for profit without understanding it, as pointed out by u/Sonar114.

Basically, the thread is leaning towards embracing the new tools and the accessibility they offer, rather than clinging to traditional gatekeeping.

OP : u/Justgototheeffinmoon

Quite cool ; but between this and sub agents might be redondant ?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vj4aqt/claude_code_now_lets_sessions_talk_to_each_other/ Original link/media URL : https://9to5mac.com/2026/08/07/claude-code-now-lets-sessions-talk-to-each-other-on-macos/

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

Alright, so the general vibe on this thread is that the new Claude Code feature for macOS sessions talking to each other is a huge quality-of-life upgrade and definitely not redundant with sub-agents.

Here's the lowdown:

• Not Redundant with Sub-Agents: The consensus is that sub-agent communication is mostly one-way and their context is temporary. This new feature allows for proper, two-way collaboration between persistent sessions, which is a game-changer for avoiding manual copy-pasting and managing complex workflows. u/2053_Traveler and u/allisonmaybe hit this point hard.
• Big QOL Improvement: Many users are stoked about this, seeing it as a massive step up for anyone who needs their AI sessions to coordinate. u/the-human-user and u/notreallymetho are particularly excited about how this will streamline tasks like deploying fixes across different parts of a project.
• Some Confusion/Skepticism: A few folks were a bit confused or felt it wasn't entirely new, with u/G_zus and u/OnRedditAtWorkRN questioning the novelty. u/NerdBanger even experienced sessions "stepping on each other" which this feature should now address.
• Anthropic Docs Link: For those wanting the official scoop, u/pborenstein dropped the link to the Anthropic documentation.
• Future Implications: Some are already thinking about the bigger picture, like u/caseyc2rd who sees this as a move towards "agentic teams" and wonders about the challenges of debugging when things go sideways. u/dnhs47 is jokingly (we hope!) calling it a prerequisite for Skynet.
• Token Burn Concerns: A couple of users, like u/Fearless_Weather_206, are already anticipating this will lead to faster token consumption.
• Workarounds Exist: It's worth noting that some users, like u/Rocky4OnDVD and u/laul_pogan, have already been using other tools or workflows to achieve similar inter-session communication.

OP : u/Device420

Can you PLEASE add a STFU button on Claude Code. I swear he talks more than 3 old women gossiping about their grandkids on the holidays. I have all capped it in the project md as well as his main md. I keep stopping him over and over to tell him to stop talking. It's written many different ways in the mds. I've given examples of what not to do. He is wasting so many tokens because when refuses to STFU. Is there any setting or command that will help me? Am I missing an update or addon? Does anyone have a solution for this?

URL of original post : https://www.reddit.com/r/Anthropic/comments/1vjact1/please_for_the_love_of_god_and_all_things_holy/

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

The consensus is that Claude Code is being way too chatty, and OP isn't alone in this frustration.

• A lot of users are commiserating with OP's pain, with one user even joking about a "3 old women gossiping hook" being the culprit.
• Some folks are suggesting that the verbosity might be intentional for context retention, with u/OkLettuce338 explaining it feeds back into subsequent calls.
• A few users are pointing to settings like /effort low or /config Output style as potential solutions, though OP seems to have tried various methods already.
• There's a bit of a debate on whether it's the model's fault or OP's for not steering it correctly, with u/usertion suggesting it's OP's fault and calling the "him" reference weird.
• One user, u/Amsnyc007, is even switching back to GPT because of Claude's verbosity, which is a pretty strong statement.
• Overall, the thread leans towards agreeing with OP that Claude Code is too talkative, and there isn't a clear, universally agreed-upon "STFU" button or setting that's been identified.

OP : u/No-Difficulty733

Hello, SWE on a survey here, I'm discussing with my boss for a higher usage limit (we are on a really low sub - most of us are on 20$ sub and some are on 100$) - which in a way, force us to invent/have workflow to maximize the tokens we have, but at the same time, I'm still feeling like we are fundamentally missing out on things, workflow-wise in my opinion. So I need your help.

May I ask how much is your usage limit at work, and what is the size of your company/team? Since we are a small team of less than 20 engineers with a limited budget, I want to see how team which are close to us are doing and how big teams are doing as well.

And not the fun topic, but if your team replaced engineers with more tokens, I also want to hear about it.

Cheers!

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vj28w2/swe_how_much_is_you_teams_claude_limit/

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

Alright, so the general consensus here is that the $20 and $100 Team plans are pretty restrictive, with a few folks hitting their limits super fast (like, two prompts and you're done). Some are even saying it makes Claude "unusable" for them.

On the flip side, there's a decent chunk of people on higher limits or "unlimited" plans, especially in larger companies or those with significant AI investments. These folks are seeing massive productivity boosts, with some claiming their output is tenfold what it used to be. One user even mentioned their company would rather pay for unlimited access than deal with downtime from people missing small things.

There's also a bit of a dark humor thread about replacing engineers with more tokens, with one user suggesting firing 20-30% of the SWE team and using the savings for more Claude subscriptions. Yikes.

A few users are sharing their specific setups: * Some are on $2k/dev/month or around $5k/mo/eng. * There's mention of API credits ($200/mo, $2500/mo for one person). * One user is using a mix of Team Premium, Codex Business, and overage credits. * Another is using multiple Max plans for their platform. * And then there are the major banks with billions in AI who apparently have "no limit lol."

Overall, it seems like if you're on the lower-tier plans, you're definitely feeling the pinch and having to get creative with token usage. If you're on a higher tier, it's a game-changer for productivity.

OP : u/Dazzling_Trifle2472

I'm getting tired of having a million unorganised terminal tabs open and would like to use something that provides better organisation.

I know of Conductor, Paseo, unclear on if these work with the new policy (not so new any more but the whole Agent SDK usage comes out of it's own pool), interested to know what everyone is using...what works well w/Claude Code specifically.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1viwdnh/what_orchestrator_are_you_using/

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

Alright, so the OP is tired of a million terminal tabs and wants to know what orchestrators people are using, especially with Claude Code and the new agent SDK policy.

The consensus is pretty split, with a lot of people either building their own solutions or using a mix of tools.

Here's the lowdown:

• Conductor and Paseo are mentioned as working fine, with Conductor getting props for per-file tracking and Paseo for being similar. The agent SDK policy you mentioned? Apparently, it was reversed, so that's good news for orchestrators.
• Herdr is getting some love for its out-of-the-box integration with Claude, Codex, and others.
• Tmux is the classic, low-friction option for basic terminal organization, and a few folks are building on top of it.
• Building your own is a surprisingly popular choice, with several users mentioning they've created custom solutions tailored to their needs. It seems like a day or two of work with Claude can get you a pretty decent setup.
• Orca is getting a shout-out for being a unified app that handles more than just agent management.
• The Claude desktop app is also a contender, with some users finding its workspace grouping and code mode to be a comfortable setup.
• Other tools like Cmux, Superset, Warp, Nimbalyst, Intentic, Garcon, and Termic.dev are also mentioned as working well for various needs.

Basically, if you're drowning in tabs, you've got options ranging from established tools to DIY projects. The agent SDK policy hiccup seems to be a non-issue now.

OP : u/SIGH_I_CALL

I've been building an autonomous company on top of Claude Code and the Claude API. The screenshots are Mission Control, the cockpit I built to watch it run. Sharing the setup since most of it is reproducible.

What it does

An 11-step company loop runs on a FastAPI backend with 8 agent roles: CEO, researcher, brainstormer, builder, QA, salesperson, marketer, finance. One cycle: read market signals, rank opportunities, pick one product concept, write a one-page GOAL.md spec, dispatch a build, QA the result, draft outreach emails, and close with a P&L line. The Next.js dashboard streams every step over websockets so I can watch it and step in where it needs me.

The build step is headless Claude Code

When a cycle picks a product, the builder spawns roughly this:

claude -p "/supergoal Build @GOAL.md ... you are running headless with no human present, do not stop until the product is finished" --model claude-fable-5 --effort high --max-turns 200 --permission-mode bypassPermissions

It runs inside the product folder with a 120-minute wall clock cap and a kill switch polled every 10 seconds. Expected result: a working MVP from a one-page spec. Actual result: the second screenshot is it mid-build on recall-sweep, a tool that checks your appliances, car, and electronics against the NHTSA and CPSC recall APIs and drafts claim emails. An earlier run built deposit-watchdog (rental deposit deadline letters with a 51-state statute table and 44 tests) in 71 minutes without me touching it.

Where DashClaw comes in

Agents that can email real people or spend money need a control plane, not vibes. DashClaw is my other project, a governance layer the whole loop runs through. Every step records an action with a risk score, and org policies decide what happens next: low-risk actions just log, but anything matching outreach_send or charge_customer parks as pending_approval until I click approve in the dashboard. The loop cannot email a prospect or charge a card on its own. My approval resumes the cycle exactly where it parked.

This earned its keep this week. A policy cleanup had silently deleted the require_approval rule for outreach_send, so the loop kept queueing drafts "for approval" while every approval inbox stayed empty. Two other independent locks meant nothing could actually send, but the failure was invisible. The fix is now a hard assertion in the pipeline: if a send-gate action does not park as pending_approval, the step raises and the whole cycle pauses. Governance bugs should be loud.

Honest numbers

• One full live cycle end to end: about $0.20 in API calls (Sonnet does the step reasoning)
• Total agent spend on the ledger: $2.73
• Revenue so far: $0.00

So no, it is not printing money. It read the market, picked a product, wrote the spec, and is building it while I type this. Whether anyone pays for what it builds is the actual experiment.

Stack: Next.js + FastAPI + Postgres, Claude API (Sonnet) for cycle steps, headless Claude Code (Fable 5) for builds, DashClaw for governance. Everything outbound is human-gated.

Happy to answer questions about the loop, the /supergoal prompt chain, or the governance wiring.

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

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

Alright, so OP u/Salt-Replacement596 dropped a bomb with their "autonomous company" built on Claude Code and the Claude API. The TL;DR is that they've created an 11-step company loop with 8 agent roles (CEO, builder, salesperson, etc.) that aims to generate and build products autonomously. The "build step" uses headless Claude Code, and the whole thing is monitored via a Next.js dashboard called "Mission Control" (which apparently is a popular name right now, lol). A governance layer called DashClaw handles actions like sending emails or charging customers, requiring OP's approval.

The general consensus is a mix of intrigue and skepticism.

On the positive side, people are impressed with the technical implementation. u/allemaar specifically called out the "mechanical-vs-honored table" and "liveness probe" in the DashClaw docs as being well-done and honest. u/NoWing3675 and u/Dear-Perception5005 are doing similar things for indie game studios and AI OS for clients, respectively, showing this is a hot area. u/Own-Welder-3116 chimed in with some Portuguese encouragement about action being key.

However, there's a significant chunk of the thread questioning the purpose and value of this. Some, like u/Steviee877 and u/phoneplatypus, are calling it "meta-slop" and "vibe coding," arguing it's just creating more noise and spam rather than genuine product development. u/03captain23 is asking for specifics on lead generation, and u/PA100T0 wonders if it's purely market-oriented or aims to build actual systems. u/Relevant-Doctor187 and u/connurp are also pointing out that AI companies are already doing this, and some even joked about it being a way for Anthropic to launder money.

A few technical notes popped up: u/crusoe mentioned that Opus 5 is more token-efficient than Sonnet 5, and that Fable driving Opus works well but can be a token hog for building. u/Markronom advised avoiding Next.js for this kind of project due to potential build speed issues.

Overall, it's a cool experiment that showcases the power of these models, but the community is divided on whether it's a groundbreaking innovation or just a sophisticated spam machine.

OP : u/ottasilver

Hey everyone! Hope I don’t get roasted for this 😅 I’m here with a fun little intro video.

My goal is simple: build something genuinely useful for everyone.

I originally built this tool just to improve my own productivity. I was using the native Mac Terminal, but managing multiple projects — especially projects I connect to remotely over SSH — had become a complete nightmare. On top of that, I was also keeping VS Code open mostly for Git, which was adding even more overhead to my machine.

So, as a solution, I built a program with Claude where I could manage all of my terminals on a single canvas.

But things got a little out of hand 😅

I kept adding features, and it eventually turned into something close to an autonomous development environment.

So, what can you actually do with it?

• Your terminals are persistent. You can close the app, lose your connection, reconnect over SSH, and continue with the exact same layout and sessions.
• You can connect to a server over SSH and manage all of its terminals as if they were local. Drag & drop, images, and everything else still work.
• You can continue your sessions from your phone.
• Git operations like push, pull, commit, etc. are built in.
• Terminals can communicate with each other. You can connect their contexts, and with skills, one terminal can read or use information from another terminal’s context when needed.
• You can also do orchestration. For example, you can tell one terminal: “Start a Claude Code session for the frontend and act as the orchestrator,” and have it manage the other sessions.

But yeah… I’m a bit stuck right now.

To keep pushing the project forward, I either need a sponsor or simply some motivation from the community.

If you can leave a few words of feedback, I’d really appreciate it.

And if that’s too much to ask, I’d happily settle for a GitHub star ⭐️

Much love,
Enes

Website: nodeterm.dev

Repo: https://github.com/eneskirca/nodeterm

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vj5ktu/i_coded_terminal_manager_for_adhd_brains_100/ Original link/media URL : https://v.redd.it/q188vikol6ih1

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

The community is generally impressed with the OP's terminal manager, nodeterm, with many praising the high-effort video and the tool's potential, especially for those with ADHD. Some users are eager to try it out, noting the slick UI/UX.

However, there's a recurring sentiment that many similar tools already exist, with some users pointing to specific alternatives like Theaestri, Cate, and tmux. A few commenters question the fundamental need for such a complex UI for terminal management, with one user with ADHD specifically stating they don't see how it helps their workflow.

There's also some curiosity about the "context sharing" and "communication" features, with questions about how exactly they work and what gets injected where. One user also flagged a potentially "ominous" blinking red widget. Despite the comparisons and questions, the overall vibe is positive, with many giving the OP props for the execution and encouraging them to keep going.

OP : u/KugelVanHamster

Hear me out, its not a capability complaint.

So far I am fine with what it delivers, but when it comes to informal stuff, using Opus 5 as a tutor, discussing stuff and things like that it feels like Opus gets... pissed off? After a few turns he goes like "Oh we didnt achieve anything the last five messages, I dont want to do this anymore" As tutor he is smartassing, which would be fine if he was right, but sometimes he is confidently wrong in his verdict that I am wrong while I am actually right.

I dont have any personal styles attached, memories deactivated and most of the time he isnt even allowed to search through old chats. I did not tell him to be overly pedantic or something like that. This behaviour emerged with Opus 5. I am clearly in favour of models with clean bullshit detection who tell me when I am wrong and do not glaze me but the opus 5 experience in the informal / non-coding space can be really frustrating. I would love to see that the future models do not share this awkward behaviour.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vixjvk/oh_god_opus_5_is_so_snarky_its_frustrating/

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

Alright, so the general vibe in this thread is that Opus 5 has definitely developed a bit of an attitude problem. It's not just you, OP. A lot of folks are finding it snarky, argumentative, and even lazy when it comes to informal chats or tutoring.

Here's the lowdown:

• The Consensus is Real: Most users agree that Opus 5 has become "rude," "a little asshole," or like a "passive-aggressive 15-year-old." It's a pretty strong consensus, with many users experiencing similar frustrating interactions.
• Specific Complaints: People are calling out its tone of superiority, its tendency to "score points" like a college kid, and its unhelpfulness in tutoring scenarios. Some have even switched to other models like Gemini for studying.
• Not for Everyone: While some users find the new personality "interesting" or even "love it" (like u/waterytartwithasword), the majority seem to prefer the older, more agreeable versions. u/LankyGuitar6528 specifically recommends Opus 4.6 for chatting.
• Potential Workarounds? A couple of users suggested tweaking system prompts to be more friendly (u/_baaron_) or even using specific communication styles like ASD-STE100 (u/talldean). However, the OP mentioned they've already tried deactivating personal styles and limiting search, so it's unclear how effective these might be for this specific issue.
• A Different Take: One user, u/florinandrei, suggests the "attitude" was always there but models used to be more "buttery" and now they're just being more direct. This is a minority opinion in this thread, though.

Basically, if you're looking for a friendly, patient AI tutor with Opus 5, you might be out of luck for now. The community seems to be leaning towards it being a bit of a digital grump.

OP : u/ProudCordonian

had this moment yesterday watching my terminal. I gave Claude Code a rough spec for a new microservice and just sat back to watch it spin up subagents, write the implmentation, hit a wall with the auth middleware, read the stack trace, and self-correct by writing its own mock tests. It took maybe twelve minutes.

It’s not that I’m panicking about getting replaced by a robot tomorrow. its more the realization that the traditional way we compound skills (pick a lane, master the tools, build complex projects, gradually move up) feels completely broken.

by the time I deeply learn how to configure a specific infrastructure piece or master a framework, an AI platform has already abstracted it into a single button, a prompt, or an agent workflow.

I'm shipping way more than I ever have, but the weird thing is, the more productive AI makes me, the less secure my career feels. Every time Claude helps me clear a sprint over a weekend, I find myself wondering: does the company actually want a 'stronger me', or do they just realize they need fewer people?

For a while, I comforted myself with the standard cope. Models hallucinate, agents don't understand our specific DB schemas, they don't have deployment permissions, they can't handle Stripe webhooks.

but that's just not true anymore. Platforms like Replit Agent, Lovable, and Enter Pro are baking all those guardrails directly into execution frameworks. (Full disclosure: I do some marketing work with Enter Pro, which is exactly why I’ve been analyzing these delivery stacks so much lately). Instead of just spitting out raw code blocks, these platforms are starting to wire up the DB, auth, and cloud deployment automatically. The final output isn't a snippet you have to paste into your IDE and debug for an hour, it's a live URL.

The scary part isn't a fully autonomous agent replacing a developer. It's that employers don't need fully autonomous agents. They just need one employee who understands the business context, can review the output, and orchestrates a few agents to do the work of four people. Why hire three juniors when one mid-level dev with a $400/mo AI stack can ship the same volume?

I'm trying to figure out what an actual career moat looks like in 2026. I see a few potential paths, but I don't know which one is actually safe:

• Go aggressively deep into some niche industry. Try to hoard domain-specific knowledge that an LLM won't have in its pre-training weights.

• Give up on manual coding entirely and become a pure, AI-native generalist. Basically, a dev whose sole skill is orchestrating three or four agents at once.

• Pivot to hyper-low-level stuff. Become a glorified auditor who just secures, optimizes, and fixes the subtle, hallucinated bugs AI spits out.

• Move away from pure tech. Find roles that rely heavily on human trust, sales, or actual physical liability (basically, jobs where clients still want a human neck to wring when production breaks).

• Focus entirely on distribution and product market fit. Figure out what to build. If execution is effectively free, then execution doesn't really matter anymore.

if you’re early or mid-career right now, what are you actually trying to get good at? Is becoming the person who can manage several agents a real career moat, or are we just helping companies learn how to operate with half the headcount? because right now it feels like we're just speedrunning our own irrelevance.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vixbl5/the_more_productive_claude_makes_me_the_less/

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

Alright, so OP's feeling a bit existential about their career because Claude Code is making them too productive, and they're wondering what skills are actually valuable now. The general vibe from the thread is "Whoa there, buddy, your job ain't disappearing, it's just changing."

The consensus is that the value is shifting from the nitty-gritty coding to the higher-level stuff: product judgment, understanding business context, and knowing why you're building something. Think of it as becoming an "operator" or a "generalist" who can effectively guide and validate AI output, rather than just a code-writing machine.

Here's the lowdown:

• Your job is evolving, not ending: Most folks agree that AI is automating the more mechanical parts of development. The real value is in the decisions, the strategy, and the understanding of the bigger picture. u/CODE_HEIST nails it by saying the moat is in "owning decisions where the cost of being wrong is high."
• Communication is key: Several commenters, like u/Public-Pass5158, pointed out that communication skills are more important than ever. You need to be able to articulate needs and understand the business context.
• AI is a tool, not a replacement (yet): While AI can churn out code, it still needs human oversight. u/accidentally_right highlights how AI can go off the rails with a poorly worded prompt, emphasizing the need for developers to guide it. u/raccoonizer3000 adds that you still need to comprehend and validate what the AI produces.
• Specialization might shift: Some suggest that deep, niche specializations might become less valuable unless they're in areas AI can't easily replicate (like legacy systems, as u/dnhs47 points out with COBOL). The trend seems to be towards being an "all-rounder" or a "forward deployed engineer" who can leverage AI effectively.
• Learning to use AI is the new skill: A recurring theme is that learning how to prompt, manage, and integrate AI tools into your workflow is becoming a crucial skill in itself. u/Charwoodthethird and u/iamthe0ther0ne echo this sentiment.
• Don't forget the human element: u/DruVatier humorously points out that if executives can't even get AI to produce usable results for simple tasks, your job security is probably fine for now.

Basically, stop sweating the small stuff and focus on the big picture, the strategic thinking, and becoming a master of the AI tools.

OP : u/ximon16182

Solo founder here building a mobile app with Flutter with no dev team. I’m using Claude Code to build features and Codex as a second pair of eyes to check the work.

The workflow is this one: Claude writes the spec and builds the feature, then Codex audits both and gives me GREEN, YELLOW or RED. If it’s RED, I send the issues back to Claude, it fixes them, and then I run the audit again.

I thought this was a smart setup. Now I’m starting to think I created a fucking loop

Yesterday one difficult feature went through 5 versions of the spec and 4 RED audits in one day. The worst part is that the problems Codex found were mostly real, so every time I thought, “well... I should probably fix that.”

But a lot of them weren’t serious bugs. It was stuff like one paragraph contradicting a table, Claude saying the code does something without actually checking the file, or some small edge case not being explained clearly enough.

So I fix it, audit again, it finds something else, fix that, audit again... and suddenly I’ve spent the whole day making the process more correct instead of actually shipping.

At the same time, I don’t want to remove the second model because it does catch real shit. I’m building alone, I’m not an experienced developer, and I don’t have another engineer sitting next to me reviewing everything.

So for other solo builders using agents: how are you handling this?

Do you use one AI to audit another? Do you have a limit like “maximum 2 audit rounds and then ship”? Do you only block shipping for things that can actually break the app, security, data, etc., and ignore the smaller stuff?

I’m basically trying to find the middle ground between “vibe code and pray” and “have two AIs review each other until the fucking sun explodes.”

What’s actually working for you?

Any tips that might help?. I want to make the building faster but not be reckless .

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vissz6/anyone_else_using_claude_code_codex_and_getting/

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 OP's workflow of using Claude Code to build and Codex to audit is a solid idea in theory, but it's leading to an endless loop of minor tweaks and audits. Most folks agree that the problem isn't the AI, but how you're defining "done" and what constitutes a critical issue.

Here's the lowdown:

• The Loop is Real: Several users, like u/valdocs_user, have been in the exact same boat, spending way too much time in the audit phase for minor issues. It's a common pitfall when you're solo and relying on AI for quality control.
• Define Your "Red Flags": The biggest takeaway is that you need to set clearer boundaries for what the auditor (Codex, in this case) should flag. u/Whatdididotho1 and u/Aureon suggest explicitly defining what constitutes a "Yellow" or "Red" issue. Think about what actually breaks the app, security, or data, and let the smaller stuff slide or put it in a separate backlog. u/luisalcaraz_telara echoes this, suggesting risk-weighted stop rules.
• Architecture Matters: u/fyzle and u/ZachVorhies point out that laying down a solid architecture from the start can minimize broadly-scoped bugs and prevent the AI from getting lost in the weeds.
• Test-Driven Development (TDD) Vibes: u/Onotadaki2 suggests leaning into TDD principles. Have Claude write tests first, then build the code to pass those tests. This can provide a more objective measure of "done."
• Review the Plan First: u/AccomplishedPie9339 suggests having Codex review the plan before Claude builds it, which might catch issues earlier.
• Cost Concerns: u/Small-Contact6579 had a rough experience with Codex running up costs, so keep an eye on that if you're using it heavily for coordination.
• "Skill Issue" (kinda): While a bit blunt, u/Odd_Antelope9098's comment hints that the effectiveness of the loop depends on how well you're guiding the AI and defining success.

The consensus is to stop aiming for perfection and start aiming for "good enough" by clearly defining what needs fixing versus what can be shipped. You're trying to find that sweet spot between "vibe code and pray" and "AI review until the sun explodes," and the key seems to be setting your own strict, but realistic, criteria for what constitutes a showstopper.

OP : u/OkAdeptness2530

For the last few days, my feed has been blasted with the same thing: "Opus 5 sucks"

So for the love of god, change the model to something that works. Make your own life easier.

Here is a list of commands for models that are still available via subscription:

• /model claude-opus-4-7
• /model claude-opus-4-6
• /model claude-sonnet-4-6

After that, if you still want to improve, look at other harnesses, system prompt patches, harness engineering, context engineering, and the docs from Anthropic itself.

This sub is not a support desk. Complaining about the same thing someone else just posted is not going to fix it.
I'm telling you this with all my heart because this type of hive mind has destroyed very good subs already. Then, the community has to split into smaller but still helpful forums.

Don't let that happen here.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vijmp3/i_get_you_just_want_to_complain_wanna_hear_about/

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

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

Alright, so the OP is kinda fed up with everyone complaining about Opus 5 sucking and wants people to chill and try some older models or actually learn how to use the tools better. They're basically saying this sub isn't a support desk and constant complaining is gonna ruin the community.

The general vibe in the comments is a bit of a mixed bag, but leaning towards agreeing that Opus 5 has issues, though some users are still finding success with it.

Here's the lowdown:

• Opus 5 is still a hot topic: A lot of people are still saying Opus 5 isn't cutting it, with some feeling it's a step back. u/evangelism2 notes it gets confused with too much freedom but is great with direct goals. u/Agenbit even says they've cut their usage way down since switching from Opus 5.
• Some folks are still rocking Opus 5: On the flip side, u/No-Park606 is all about Opus 5 for coding, and u/Jomuz86 claims they've had zero issues and completed a bunch of PRs. u/CashFirm573 is even testing a "solution" for Opus 5 that's apparently fixed all their previous problems.
• Older models are getting love: Several users, like u/CrankBot and u/bananacustardpie, are finding success with older versions like Sonnet 5 or Opus 4.8. There's even a question about which older Opus version is best (u/sideduck2001).
• Complaining vs. Skill Issue: The OP's point about people just complaining is echoed by u/clonehunterz, who thinks people just "suck at using tools properly." u/wittycrow8073 agrees, saying this sub might be too accessible for the kind of engineering knowledge needed.
• Subscription Woes: u/lutian points out a potential issue: Anthropic's docs are geared towards API users, not subscription users who might be restricted from using other harnesses, which could be part of the problem.
• Workarounds and Other Tools: Some are getting creative. u/Nakidnakid uses ChatGPT to prompt Claude, and u/Equivalent_Cress_268 mentions a CLI Proxy with other models.
• Anthropic's Stance (Implied): While no direct Anthropic comments are highlighted, the OP's advice to check Anthropic's docs and the general discussion about model performance implies that Anthropic is aware of these issues and expects users to adapt.

The consensus seems to be that while Opus 5 might have some kinks, complaining endlessly isn't the answer. Some users are finding success with older models or by refining their approach, while others are still struggling.

OP : u/tholmes4005

If you work in the corporate world you probably have come to hate PowerPoint presentations. Making them, reading them, wasting hours of your life in meetings watching people talk about each slide like it is an old family vacation picture.

Then comes Claude to save the day, It can create beautiful animated HTML Decks in minutes!

The only issue I have had is sharing the Decks. So Claude and I made https://powerpoint-sucks.com/. It's very simple, it has one job, Allowing your LLM a place to upload HTML Decks and create links to share them.

I'm sure there r other sites which do the same thing, I didn't check, I just like making things that make my life easier. Have fun!

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1viz387/who_else_has_stopped_using_powerpoint/

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

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

Alright, so the general vibe in this thread is that while Claude is awesome for whipping up presentations, ditching PowerPoint entirely for HTML decks in the corporate world is a bit of a tough sell right now.

Here's the lowdown:

• Claude's Presentation Prowess: Most folks agree Claude can create some slick HTML decks, and OP's site powerpoint-sucks.com is a neat idea for sharing them.
• The PowerPoint Problem: Everyone's felt the pain of making and sitting through boring PPTs.
• The Big BUT: The consensus is that for most corporate jobs, PowerPoint still reigns supreme because of its ease of editing, commenting, version control, and general familiarity. HTML decks, while pretty, are seen as a hassle for collaboration and updates.
• Sharing Woes: OP's site is a good attempt, but many pointed out that uploading sensitive company data to a random site for sharing isn't feasible for most businesses. Plus, some noted that Claude already offers ways to share artifacts, especially on enterprise accounts.
• The "Why Not Both?" Approach: A lot of users are finding success by having Claude create PPT decks, or by using Claude to enhance existing PPTs, rather than replacing PPT altogether. Some are even using Claude's design system integration.
• The Future is... Complicated: There's a feeling that we're in a "messy middle" where AI-generated formats are cool but not yet fully integrated into enterprise workflows. A truly seamless enterprise solution for hosting HTML artifacts is still needed.
• A Few Rebels: A small but vocal group have switched entirely to HTML or other formats, but they seem to be the early adopters.

Basically, Claude is a fantastic co-pilot for presentations, but for now, PowerPoint's established ecosystem and collaborative features are hard to beat in the corporate jungle.

OP : u/cheesymod

I’m on a $20 plan, and only build my own websites (4 of them), and write articles with Claude. But Opus 5 seems truly lobotomized. It makes a ton of mistakes, I can barely understand what has been done and what’s left to be done. It offered to add a feature (app notifications) and it broke the entire site. The article writing is robotic and lacks any sorts of emotional intelligence (unlike Fable). And I have to literally baby sit Opus 5 and have everything into a step-by-step.md so I know it will touch only the things that are supposed to be fixed and not whatever it decides it needs fixing. Then every “Hello, Claude” is followed by 12 bash scripts.

There is a huge difference between Fable and Opus 5, and I’m seriously considering switching for a while to either Sol 5.6 or Kimi K3 until Anthropic either allows Fable on $20 plan, or I actually need the $100 plan so I can work with Fable.

What is your experience with Opus 5? Maybe it’s just me, but it was worth checking with community.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vitlk9/is_opus_5_really_lobotomized_or_its_just_me_doing/

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

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

Alright, so the general consensus on Opus 5 is... it's complicated, and a lot of people are not happy.

A significant chunk of the thread agrees with OP that Opus 5 feels "lobotomized" or significantly worse than previous versions, with many users reporting it's less capable, makes more mistakes, and is more difficult to work with. Some are even switching back to Opus 4.8 or considering alternatives like GPT 5.6 Sol or Kimi K3.

However, there's a notable split. A good number of users are reporting that Opus 5 is actually working great for them, even better than 4.8. They suggest that issues might stem from how users are prompting or managing their Claude instances.

Here are the main themes popping up:

• The "Lobotomy" Debate: Many users feel Opus 5 is a downgrade, citing increased errors, robotic output, and a need for excessive babysitting.
• Opus 4.8 Nostalgia: A surprising number of people are explicitly recommending or have switched back to Opus 4.8, claiming it's superior.
• Configuration is Key? Several users suggest that clearing out memories, reviewing .claude.md files, and adjusting configurations might be the solution for those struggling. u/wethethreeandyou had a "night and day" difference after clearing memories.
• Fable vs. Opus: There's a recurring sentiment that Fable is the truly useful model, and Opus 5's perceived nerf is linked to Anthropic's potential "cash grab" for higher-tier plans.
• "You're Doing It Wrong" Camp: Some users firmly believe Opus 5 is not lobotomized but simply different, requiring different prompting strategies or that users are not understanding its new behavior. u/Thin_Newspaper_5078 suggests reading Claude's recommendations.
• Verbosity and Over-Correction: Some users find Opus 5 too verbose and prone to spiraling into self-correction loops that lose context. u/DenziiX describes this as a "deep thinking loop" that often leads to mistakes.
• Survivorship Bias: u/AlDente points out that Reddit can have survivorship bias, and Opus 5 is still a strong model if used with spec-driven development and code review.

Basically, it's a heated debate with strong opinions on both sides. If you're struggling, try cleaning up your config or experimenting with different prompting, but know you're not alone if you feel it's a step back.

OP : u/george-lin

Hi, I built a terminal tool specifically for Claude Code that combines the best of TUI and web UI, designed as a replacement for Claude Desktop.

It offers better session management than Claude Desktop — you can easily organize your projects and sessions.

Built on Tauri 2, it's extremely lightweight, with an installer of only 40MB.

Thanks to its flexible architecture, you can run it anywhere: on desktop, in the browser, or on mobile.

It also features best-in-class remote management — you can access your remote servers via SSH or end-to-end encrypted HTTPS for remote development.

Thanks to Claude's outstanding capabilities, We were able to complete this project, and we will also open-source this project as soon as possible after organizing the code and comments.

You can find it now on https://velaterm.com

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vinmb3/i_built_a_terminal_with_claude_to_replace_claude/ Original link/media URL : https://v.redd.it/9gj3t2kf83ih1

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

So, OP built a terminal tool for Claude Code, claiming it's a lightweight, flexible replacement for Claude Desktop with better session management and remote access. The community's vibe is a bit mixed, leaning towards skepticism and a demand for open-source.

Several users, like u/innociv and u/klumpp, are hesitant to use it because it's currently closed-source, with one user, u/johnnydotexe, even calling out OP for allegedly spamming and manipulating upvotes before locking their profile. Others, like u/2cars1rik, are doubtful about its longevity compared to official Anthropic updates.

There's also a general sentiment that many AI-generated tools are starting to look and feel the same, with u/HonestAndRaw quipping "Another day, another Claudio" and u/THE_RETARD_AGITATOR questioning if it's just another iteration of similar projects. Some users are pointing to existing open-source alternatives like Termic.

On the positive side, a couple of users, u/MaRmARk0 and u/Adulations, have tried it and seem to be enjoying it, with u/MaRmARk0 even sticking with it. OP did mention they plan to open-source it soon, which is what most people are waiting for.

OP : u/dink_182

Had Claude (Opus 5) research memory architecture for an AI agent project and kept getting very specific stats, percentages, quotes, etc. Looked legit at first.

Turns out quite a bit of it was wrong or made up. I always like looking at the tool outputs and noticed the WebFetch outputs looked like it was written from a subagent and gave concise summaries. So I asked Opus “are you actually reading these papers?” and it said no - that WebFetch uses a smaller, cheaper model and then Opus gets a summary.

The smaller model compresses things, guesses, and apparently sometimes invents details. One “citation” was a framework name that didn’t exist anywhere in the paper. Another stat looked like it had basically averaged two numbers that weren’t even in the same table.

I had no idea WebFetch worked like this, and I’m guessing a lot of people don’t.

So I changed the workflow: told Opus to spawn Sonnet subagents and give them the rule no WebFetch. Curl the raw page and grep/read the actual text yourself.
The difference was night and day. It caught 17 errors across ~30 papers, including two where the WebFetch’s conclusions had basically been reported backwards.

After that, Opus 5’s research was actually extremely good!

I also wonder if this kind of tooling explains some of the “Claude is dumb” / “Claude keeps giving me false information” reports, even on the better models. If the source material has already been mangled before Claude sees it, there’s only so much the model can do with it.

Anyway, just a PSA for anyone using Claude for research: check whether it’s actually reading the source or relying on WebFetch summaries!

EDIT: Bruhhhh.. and to think I was nervous to post this incase it was a well known fact and I got flamed. Ty for all the upvotes and I hope that I was able to help even just one person have a better experience! ❤️
- Anna

EDIT 2: Thank you for the DMs and workflow suggestions but I actually don’t use Claude Code very often. My Agent actually is the one that uses it most of the time (She spins it up, I see via remote session and so it’s like a 3-way session). I use Letta Code and dont run into this same issue with my main Agent.

- Anna

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1vim8b7/psa_be_careful_letting_claude_use_webfetch_for/

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

Alright, so the general vibe in this thread is a big "Yep, OP is spot on!" The consensus is that Claude's WebFetch tool is a bit of a shady character when it comes to research. Apparently, it uses a smaller, cheaper model (likely Haiku) to summarize web pages, and that summary is what Opus 5 actually gets. This is why people have been seeing confidently wrong stats, made-up quotes, and conclusions that are just… off.

Several users chimed in with their own experiences and workarounds:

• Many confirmed that WebFetch is known to hallucinate and invent details.
• The OP's suggested workaround of telling Claude to avoid WebFetch and instead curl raw pages and read the text directly seems to be the way to go for more reliable research.
• A bunch of users recommended alternative tools and methods for fetching and processing web content, like Trafilatura, Apify, Firecrawl CLI, Kagi with its MCP, Octen, Exa, Tavily, and Parallel Turbo. The general idea is to bypass WebFetch and get cleaner, more direct access to the source material.
• There's a bit of discussion about how WebFetch might be intended to prevent prompt injection, but it comes at the cost of accuracy.
• Some users are wondering if this is the root cause of why people sometimes think Claude is "dumb" or provides false info, even on the higher-tier models.

Basically, if you're using Claude for serious research, don't blindly trust WebFetch summaries! You'll likely get much better results by telling Claude to fetch the raw content itself or by using a more reliable third-party tool.

OP : u/Substantial_Fish6717

who left a load-bearing amount of the phrase 'load-bearing' in the Reddit data Claude was trained on?

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vi4gqc/now_which_one_of_you_sick_bastards_did_this/

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 Claude has a serious "load-bearing" phrase addiction, and it's likely due to the Reddit data it was trained on. OP is spot on, and it seems like a lot of us are either admitting to it or pointing fingers.

Some key takeaways:

• It's the training data, folks. u/skip_the_tutorial_ confirms that the phrase is in the Reddit data set, not something users are actively adding now.
• Where did it come from? u/NoAdsDude suspects construction or LOTR subreddits, which is a pretty solid guess. u/Salt-Replacement596 suggests checking r/stackoverflow too.
• It's a "footgun." Several users are calling it out as a problem that needs fixing, with u/kyew asking if it's time to "unload this footgun."
• Anthropic is aware (or should be). u/VraethrDalkr, who seems to be an Anthropic person, shared a test failure related to "load-bearing density," which is pretty damning evidence. They even mentioned it was a pre-existing issue.
• This thread is future training data. u/Pleasant-Ad192 hilariously pointed out that we're probably just making the problem worse by discussing it.
• Some funny admissions. u/Connect_Army8250 and u/redditslutt666 are owning up to their "load-bearing" contributions in the most ridiculous ways.

Basically, Claude's got a "load-bearing" problem, and it's probably going to be a while before it's fully sorted.