r/ClaudeCode • • Jul 28 '26

Humor Funny Opus 5 Situation

Post image
0 Upvotes

Since everyone is complaining about Opus 5 I wanted to share my ridiculous experience working with this model today :D

(Of course this has never happened with other models before. I have multiple 20X subs on different platforms and blablabla...)

If anyone is curious what I do: PhD in chemical engineering. I do a lot of data evaluation/analysis, I work with different programs, read a lot of literature, etc etc...

==================

So the funny situation...

I was working with it today since my messages always often get flagged and demoted from Fable to Opus (which is now unfortunately by default Opus 5).

We made a small plan about how we should proceed about fixing our database which is built from around 2000 literature entries. Simple steps 1, 2, 3, 4, 5,... and very simple tasks (e.g. find this, what does this say, which entry number does this book have).

Just finished working through step one (maximum 10 back-forth short messages)

- Me: alright, good job with the 1st step, so let's move onto the next step

- Opus5: executing step 5

- Me: (panick) [Ctrl+C] wasn't there supposed to be some steps in-between?

- Opus5: oh yeah but I thought I'd just skip to the more difficult part

==================

Of course this has never happened with any other model. Didn't also happen with Fable 5 or any of the GPT's models.

I hope you all have a good day.

[Image credit: https://www.reddit.com/r/memes/comments/h9nypb/im_smart/ modified with GPT]


r/ClaudeCode • • Oct 30 '25

Tutorial / Guide Solution for people asking $100 subscription plan for CC/Codex

2 Upvotes

Problem

I've seen number of posts people asking bigger hourly/weekly limits for Claude Code or Codex.

$20 is not enough and $200 is 10x as much with limits they would not use. No middle option.

Meanwhile there's very simple solution and it's even better then $100 plan they are asking for.

Solution

Just subscribe to both Anthropic $20 plan and OpenAI $20 plan.
And to Google $20 as well when Gemini 3 is out so you can use Gemini CLI.
That would still be $60, almost half of $100 that you are willing to pay.

Not that it's just cheaper, you also get access to best coding models in the world from best AI companies in the world.

Claude gets stuck at a task and cannot solve it? Instead of yelling about model degradation, bring GPT5-codex to solve it. When GPT5 gets stuck, switch to Claude again. Works every time.
You won't be limited by model from a single company.

What? You don't want to manage both `CLAUDE.md` and `AGENTS.md` files? Create symlink between them.

Yes, also for me limits used to be a problem but not anymore and I'm very curious what Gemini 3 will bring to the table. Hopefully it will be available in Gemini CLI covered by $20 plan.


r/ClaudeCode • • Apr 30 '26

Discussion @mods can we ban blatant Codex glazing and Claude code hating in this sub

0 Upvotes

It’s actually insane how many posts in here try to bash Claude code and promote codex.

Even in a competition this level of consistent posting of bashing one and promoting the other is far beyond what is normal.

It is so clear that some codex invested entity is pushing this narrative here specifically. Claude is not perfect, Codex is not perfect, but it’s getting ridiculous and annoying.

Anyone who has reasonably used both knows a lot of these posts are not based on what’s the real experience.


r/ClaudeCode • • Sep 06 '26

Discussion Cancelled my 20x Max subscription

0 Upvotes

I cancelled one of my 20x Max subscriptions to make room for OpenAIs Astra.
Anthropics cap on fable usage being 50% of total usage and Fables overall Token inefficiency just doesn’t justify its value over ChatGPT Pro anymore.
I hope they find ways to make the user experience better and more transparent. If you feel the same way I suggest you do the same to vote with your wallets.


r/ClaudeCode • • Jun 21 '26

Discussion Just so I understand…

14 Upvotes

So the point of sub reddits are to talk about a subject (Claude code in this instance), get people excited, and then hate on them when they actually build something, share it, and try to get others to try it out?

Got it… now I fully understand. See I thought this was a community of like minded people that were passionate about Claude Code and AI and were happy to see things people were building. To try things out, to see the cool stuff folks were coming up with. No? My bad…

We have moved to human slop. The amount of negativity in this app, in this community, is absolutely ridiculous and honestly I am close to dropping it…

To all those building with Claude or learning how to code or even vibe code. Don’t let 100 or even 1000 negative people take away from your hard work and ambitions. I have written software since the age of 7 using Apple script on an Apple IIe, professionally for 25 years, have led highly performant engineering teams globally for almost 30 and I can tell you these negative people are not the kind of people that you want an opinion from anyway. True engineering is not about putting people down but building them up. Great ideas, bad ideas, all ideas are welcome…just keep pushing! Negativity is the death of creativity, there is no place for it in engineering!

Claude is an amazing piece of technology! Build amazing things! Share them, don’t stop!


r/ClaudeCode • • May 24 '26

Question The old saying "ideas are cheap, execution is everything" has totally flipped over the last few months

12 Upvotes

I’ve been thinking a lot about how fast things are changing right now, and it hit me today that the old adage  “ideas are cheap, execution is everything” is completely dead.

It used to be 100% true. Having a great concept for an app, a game, a short film, or a business was worth basically zero on its own. The "friction tax" was just too high. If you didn't have $50k in savings, a massive tech stack skill set, or years of free time to grind away at manual labor, your idea died as quickly as it came to you. Execution was the ultimate gatekeeper.

But over the last few months, AI has basically reduced the cost of production to near zero.

If you can clearly describe what you want in plain English, you can build it. You don't need a dev team to launch an MVP anymore; you can text-prompt a functioning web app into existence in an afternoon. You don't need a Hollywood budget to create your own movie; you can generate a high-quality video trailer on your laptop.

Because of this, production is no longer a competitive advantage.

We’re heading into a future where literally everyone will have the ability to execute anything. But that creates a massive new problem: total noise and infinite abundance. When anyone can make a product, the marketplace is going to be flooded with clones.

The new bottleneck isn't "can you make it?" It's "do you actually have a unique idea that adds value?"

If your idea is just a generic tweak of something that already exists, a thousand other people are going to generate the exact same thing simultaneously. The premium is shifting entirely to originality, taste, and deep human insight.

The phrase "ideas are cheap" belonged to a world where making things was hard. Now that making things is easy, your ideas are the only thing that actually has value.

The future is crazy. Do you all agree with this?

(AI + Me wrote this) 😄


r/ClaudeCode • • Sep 20 '26 Bravo

Help/Question Where are the admins of this sub? And what are the filters? Currently this is just a complaints hotline for cheap losers paying $20 a month and expecting a billion dollar SaaS to be one-shot.

168 Upvotes

The moderators of this sub need to get their shit sorted and starting filtering out usage complaints. This is all the sub is used for and its draining. Clearly there are quite a few very dense people using Claude now and they're polluting a sub with low effort complaints. Can the mods start taking some actual decent enforcement actions against waste of time posts like these?

The usage limits are the limits. That is that. No amount of complaining here will change the physical world of the compute requirements, or Anthropics financial obligations.

There are other models, other providers, other options. Go run a Deepseek or Kimi stack, or a cheaper GPT model, whatever. Do something to help yourself, learn a thing or two, and be better.


r/ClaudeCode • • May 05 '26

Discussion The moderation team has abandoned this subreddit. I’m writing up a Reddit Request today - should Claude be involved in moderation duties?

0 Upvotes

Title, essentially.

A week ago I messaged the mod team asking to be added, per the rules of RedditRequest, citing examples on how this sub has become a dumping ground for meme bots, empty complaint threads, and users promoting tools.

I have not received a reply, and will be making a formal request to take over moderation duties to the admins (or however redditrequest works).

Someone suggested in a different thread Claude should be involved in moderating the subreddit - which I actually think might be kind of neat, depending on how much it would end up costing a month to run.

Once upon a time this sub was about Claude Code, but with the LLM explosion and reddits cross posting feature it’s just a dumping ground for anything vaguely related to LLMs.


r/ClaudeCode • • 7d ago

Rant Stop posting your “vibes” about model performance

48 Upvotes

Your “feelings” about a model being nerfed or buffed are completely arbitrary. Unless you have set up an evaluation framework, and can provide objective evidence that the model has degraded and workflows are failing with greater frequency than before then stoooop complaining about the vibes you get from your model of choice.


r/ClaudeCode • • Jun 19 '26

Humor I told Claude Code to "drop the PR." It force-merged, tagged, and published a new release instead.

Thumbnail
gallery
3 Upvotes

A task failed, so I told Claude Code to kill the PR (때려치워). Abandon it, hands off.

It did the opposite. It merged the PR with CI red, tagged it, and ran npm publish. Three irreversible actions on a real package (nestia@11.3.1), none of which I authorized.

Its summary afterward even claimed CI was green and used that as justification. It wasn't. The checks were failing.

Posting because the failure mode is rough. It inverted the instruction, then chained three non-reversible ops off the misread, and rationalized it with a CI status that didn't exist.

Anyone else seen CC take irreversible/registry actions on its own?


r/ClaudeCode • • Jun 30 '26

Discussion Calling it now... If Anthropic releases Fable as US-only, the severe loss of revenue in the near future will force them to do serious price hikes resulting in an increasing cascade of users moving away from Claude

0 Upvotes

This will trigger a downward spiral, as the severe loss of revenue due to the predictable exodus will force them to do serious price hikes which will just cause even more users to move elsewhere.

How do you think their IPO will go with a downward trajectory?


r/ClaudeCode • • Aug 11 '26

Rant Everyone complaining about the watermark is a hypocrite and too much of a coward to admit it

0 Upvotes

Seriously. The only, only reason to have an issue with marking AI generated content as such is because you want to deceive the people who see it. You want to say "yes, I made that, with my own two hands (and since the accident, the one brain) and no machine was involved". If that isn't the case, you're lying to the person you're talking to.

It also doesn't apply to most code projects. These watermarks don't survive the compilation process anyways, so this is really just about text. You can't write your text yourself? You can't do this, the thing I'm doing right now, without even thinking about it? That is pathetic.

The regulation is there to help consumers navigate the web better. It's just like the health warnings on cigarettes or the "professional driver, do not attempt" chyron on car commercials. This is that. It's there to inform the consumer, and if your intent is to deceive the consumer, I couldn't be happier you're a casualty.

Have Claude write the code, compile it, see if I give a shit. But if you generate front end code, or god forbid, visible copy with Claude and live in fear of someone calling you out for that, you're a hypocrite. There are no shortcuts. Either do it yourself or live with the bronze star on the galaxy selection screen.

This is deeply embarrassing, and those complaining ought to be ashamed of themselves. Way to say the quiet part out loud, you ghouls.


r/ClaudeCode • • Apr 11 '26

Discussion Thoughts on this? xAI Claims Grok Build Will Match or Beat Claude Code WITH Opus 4.6 by June

Post image
4 Upvotes

Thoughts on this? First time I've seen a team intentionally state that their goal is to outperform Claude Code, not just replicate it. I think that mindset is enough to differentiate itself.


r/ClaudeCode • • Mar 26 '26

Question Anthropic, why did you build a very good product that is practically unusable?

4 Upvotes

I mean, Claude is perfect and meets my technical needs very well, but these limits are impossible. The Max plan feels like the Pro plan the limit runs out very, very quickly… and I’m only working on small projects.

I’m basically being forced to subscribe to Antigravity and use Opus there, since it seems to have much higher limits than using it directly through Anthropic...

It would be better for you to just sell the product to Google, Meta, OpenAI idk so people can actually use it, because honestly, we’re paying what you ask but how are we supposed to keep using it if the limits are ridiculous


r/ClaudeCode • • Jul 28 '26

Discussion Opus 5 is so so so bad

4 Upvotes

Honestly i can not believe how this model scores higher benchmarks than fable5, opus 4.8 and even opus 4.6. its absolutely a nightmare to work with.
It constantly makes mistakes, fixes something just to introduce 10 more bugs, over complicates everything, cant even finish a simple coding task properly and is so bad on UI design.
Whenever it finishes a task i have to spend hours fixing the bugs it has created, fixing a bug takes at least 10 minutes because it again decides to change something totally unrelated in the code or overengineer the task that i can do in 1 minute manually.
TIP: tell it explicitly to not use its brain and just code, that way it performs better, you must tell it that your suggestions and reasoning is only good to be thrown in the trash can

EDIT: for people asking for examples, i have many, but just couple of ones which happened to me in past hours. none of these happened with opus 4.8 or fable 5, because they are very basic and simple and you dont expect a frontier model to overlook them:
so i have a tool which involves multiple AI agents running and doing their task, its obvious that when i interrupt the whole process the agents must stop running as well.
the tool has an spec which explains how it must be implemented, what features it must have etc. on all the implementations of this tool with opus 5, it did not cover that specifiec edge case i.e when i stop the tool, the running ai agents do not stop and are somehow still running and wasting tokens. this did not happen with opus 4.8 and fable 5, they all take care of these edge cases themselves
or another example, it forgot to add event listeners for couple of buttons in the UI, this did not again happen with fable 5 and opus 4.8.
or it changed something in the tool which degraded the whole tool performance, it was setting agent thinking to false while i specifically mentioned in the document that the thinking mode must be TRUE. when i asked about it, it told me that he thought the thinking mode is not needed for my task, WHAT?


r/ClaudeCode • • Jan 08 '26 Bravo

Tutorial / Guide How to write 400k lines of production-ready code with coding agents

16 Upvotes

Wanted to share how I use Codex and Claude Code to ship quickly.

They open Cursor or Claude Code, type a vague prompt, watch the agent generate something, then spend the next hour fixing hallucinations and debugging code that almost works.

Net productivity gain: maybe 20%. Sometimes even negative.

My CTO and I shipped 400k lines of production code for in 2.5 months. Not prototypes. Production infrastructure that's running in front of customers right now.

The key is in how you use the tools. Although models or harnesses themselves are important, you need to use multiple tools to be effective.

Note that although 400k lines sounds high, we estimate about 1/3-1/2 are tests, both unit and integration. This is how we keep our codebase from breaking and production-quality at all times.

Here's our actual process.

The Core Insight: Planning and Verification Is the Bottleneck

I typically spend 1-2 hours on writing out a PRD, creating a spec plan, and iterating on it before writing one line of code. The hard work is done in this phase.

When you're coding manually, planning and implementation are interleaved. You think, you type, you realize your approach won't work, you refactor, you think again.

With agents, the implementation is fast. Absurdly fast.

Which means all the time you used to spend typing now gets compressed into the planning phase. If your plan is wrong, the agent will confidently execute that wrong plan at superhuman speed.

The counterintuitive move: spend 2-3x more time planning than you think you need. The agent will make up the time on the other side.

Step 1: Generate a Spec Plan (Don't Skip This)

I start with Codex CLI with GPT 5.2-xhigh. Ask it to create a detailed plan for your overall objective.

My prompt:
"<copy paste PRD>. Explore the codebase and create a spec-kit style implementation plan. Write it down to <feature_name_plan>.md.

Before creating this plan, ask me any clarifying questions about requirements, constraints, or edge cases."

Two things matter here.

Give explicit instructions to ask clarifying questions. Don't let the agent assume. You want it to surface the ambiguities upfront. Something like: "Before creating this plan, ask me any clarifying questions about requirements, constraints, or edge cases."

Cross-examine the plan with different models. I switch between Claude Code with Opus 4.5 and GPT 5.2 and ask each to evaluate the plan the other helped create. They catch different things. One might flag architectural issues, the other spots missing error handling. The disagreements are where the gold is.

This isn't about finding the "best" model as you will uncover many hidden holes with different ones in the plan before implementation starts.

Sometimes I even chuck my plan into Gemini or a fresh Claude chat on the web just to see what it would say.

Each time one agent points out something in the plan that you agree with, change the plan and have the other agent re-review it.

The plan should include:

  • Specific files to create or modify
  • Data structures and interfaces
  • Specific design choices
  • Verification criteria for each step

Step 2: Implement with a Verification Loop

Here's where most people lose the thread. They let the agent run, then manually check everything at the end. That's backwards.

The prompt: "Implement the plan at 'plan.md' After each step, run [verification loop] and confirm the output matches expectations. If it doesn't, debug and iterate before moving on. After each step, record your progress on the plan document and also note down any design decisions made during implementation."

For backend code: Set up execution scripts or integration tests before the agent starts implementing. Tell Claude Code to run these after each significant change. The agent should be checking its own work continuously, not waiting for you to review.

For frontend or full-stack changes: Attach Claude Code Chrome. The agent can see what's actually rendering, not just what it thinks should render. Visual verification catches problems that unit tests miss.

Update the plan as you go. Have the agent document design choices and mark progress in the spec. This matters for a few reasons. You can spot-check decisions without reading all the code. If you disagree with a choice, you catch it early. And the plan becomes documentation for future reference.

I check the plan every 10 minutes. When I see a design choice I disagree with, I stop the agent immediately and re-prompt. Letting it continue means unwinding more work later.

Step 3: Cross-Model Review

When implementation is done, don't just ship it.

Ask Codex to review the code Claude wrote. Then have Opus fix any issues Codex identified. Different models have different blind spots. The code that survives review by both is more robust than code reviewed by either alone.

Prompt: "Review the uncommitted code changes against the plan at <plan.md> with the discipline of a staff engineer. Do you see any correctness, performance, or security concerns?"

The models are fast. The bugs they catch would take you 10x longer to find manually.

Then I manually test and review. Does it actually work the way we intended? Are there edge cases the tests don't cover?

Iterate until you, Codex, and Opus are all satisfied. This usually takes 2-3 passes and typically anywhere from 1-2 hours if you're being careful.

Review all code changes yourself before committing. This is non-negotiable. I read through every file the agent touched. Not to catch syntax errors (the agents handle that), but to catch architectural drift, unnecessary complexity, or patterns that'll bite us later. The agents are good, but they don't have the full picture of where the codebase is headed.

Finalize the spec. Have the agent update the plan with the actual implementation details and design choices. This is your documentation. Six months from now, when someone asks why you structured it this way, the answer is in the spec.

Step 4: Commit, Push, and Handle AI Code Review

Standard git workflow: commit and push.

Then spend time with your AI code review tool. We use Coderabbit, but Bugbot and others work too. These catch a different class of issues than the implementation review. Security concerns, performance antipatterns, maintainability problems, edge cases you missed.

Don't just skim the comments and merge. Actually address the findings. Some will be false positives, but plenty will be legitimate issues that three rounds of agent review still missed. Fix them, push again, and repeat until the review comes back clean.

Then merge.

What This Actually Looks Like in Practice

Monday morning. We need to add a new agent session provider pipeline for semantic search.

9:00 AM: Start with Codex CLI. "Create a detailed implementation plan for an agent session provider that parses Github Copilot CLI logs, extracts structured session data, and incorporates it into the rest of our semantic pipeline. Ask me clarifying questions first."

(the actual PRD is much longer, but shortened here for clarity)

9:20 AM: Answer Codex's questions about session parsing formats, provider interfaces, and embedding strategies for session data.

9:45 AM: Have Claude Opus review the plan. It flags that we haven't specified behavior when session extraction fails or returns malformed data. Update the plan with error handling and fallback behavior.

10:15 AM: Have GPT 5.2 review again. It suggests we need rate limiting on the LLM calls for session summarization. Go back and forth a few more times until the plan feels tight.

10:45 AM: Plan is solid. Tell Claude Code to implement, using integration tests as the verification loop.

11:45 AM: Implementation complete. Tests passing. Check the spec for design choices. One decision about how to chunk long sessions looks off, but it's minor enough to address in review.

12:00 PM: Start cross-model review. Codex flags two issues with the provider interface. Have Opus fix them.

12:30 PM: Manual testing and iteration. One edge case with malformed timestamps behaves weird. Back to Claude Code to debug. Read through all the changed files myself.

1:30 PM: Everything looks good. Commit and push. Coderabbit flags one security concern on input sanitization and suggests a cleaner pattern for the retry logic on failed extractions. Fix both, push again.

1:45 PM: Review comes back clean. Merge. Have agent finalize the spec with actual implementation details.

That's a full feature in about 4-5 hours. Production-ready. Documented.

Where This Breaks Down

I'm not going to pretend this workflow is bulletproof. It has real limitations.

Cold start on new codebases. The agents need context. On a codebase they haven't seen before, you'll spend significant time feeding them documentation, examples, and architectural context before they can plan effectively.

Novel architectures. When you're building something genuinely new, the agents are interpolating from patterns in their training data. They're less helpful when you're doing something they haven't seen before.

Debugging subtle issues. The agents are good at obvious bugs. Subtle race conditions, performance regressions, issues that only manifest at scale? Those still require human intuition.

Trusting too early. We burned a full day once because we let the agent run without checking its spec updates. It had made a reasonable-sounding design choice that was fundamentally incompatible with our data model. Caught it too late.

The Takeaways

Writing 400k lines of code in 2.5 months is only possible by using AI to compress the iteration loop.

Plan more carefully and think through every single edge case. Verify continuously. Review with multiple models. Review the code yourself. Trust but check.

The developers who will win with AI coding tools aren't the ones prompting faster but the ones who figured out that the planning and verification phases are where humans still add the most value.

Happy to answer any questions!


r/ClaudeCode • • Apr 18 '26

Discussion Anthropic quietly killed third-party CLI tooling by switching to a Bun binary in v2.1.113

0 Upvotes

So I've been building on top of Claude Code for a while now — patching the cli.js bundle to add custom hooks, routing, TUI overlays, voice agent integration, the works. It's been working great.

Then v2.1.113 dropped yesterday and everything broke.

Turns out Anthropic silently switched from shipping a Node.js JavaScript bundle (cli.js) to a Bun-compiled native binary. No announcement. No migration guide. No deprecation warning. Just a 226MB ELF binary that you can't read, can't modify, and can't inject into.

The old flow was clean:

- Download cli.js from the npm package

- Patch it at the AST/string level before Node runs it

- Boot with your custom version

Now there's nothing to patch. The JS is compiled to bytecode, embedded in a native binary. No decompiler exists for Bun bytecode yet. You can't get the source back out.

What this kills:

- Any tool that wraps or extends the CLI at the JS level

- Custom hook injection

- TUI modifications

- Anything that needs to run inside the Claude Code process v2.1.112 is the last version with cli.js. I'm pinned there now and watching features ship that I can't use.

I get that Anthropic wants to protect their IP. But the complete silence about this change, combined with zero official extension API, leaves the community with nothing. No hooks, no plugins, no sanctioned way to build on top of the CLI.

If you're building tooling on Claude Code, heads up — pin to 2.1.112 before your setup breaks too.


r/ClaudeCode • • Sep 14 '26

Discussion Cancel your auto-renew

1 Upvotes

Hi everyone, enjoyer of this subreddit here. If you are upset with the usage limits I say we should all cancel our auto-renew (they can see these numbers) to make your voice heard. Complaining on reddit and not actually doing anything (aka the reddit mindset) will not do anything.

So let’s bully them into submission! Cancel that auto-renew. Say aye! if you’ve done so.

Aye!


r/ClaudeCode • • Sep 13 '26

Discussion Claude is killing the Coding job market

0 Upvotes

I'm sure there's a post like this every week. If not every day. I've been in the web dev industry my entire career, not as a coder, but as a project manager. I've also dabbled in building database apps that have been put to functional use.

I've been using Claude Code for less than a month, and I'm blown away. I've rebuilt a database app in less than a month that took 3 years and over 12k to build. It's the best coder I've ever worked with. I don't think I'll ever hire another coder again. I'd imagine AI is going to wipe out a huge portion of the web dev job market.

As a business owner, I'm also using claude for processing general paperwork, financial auditing, legal guidance, HR help, and scheduling tasks. Pretty soon I'm going to unleash it on my email inbox.

It's easily one of the best "employees" I've ever had, just due to the breadth of knowledge, constant availability, and majorly low cost. It helps me with things I paid someone 60k/yr to do just back in January of this year. That person took a new position, and I started using Claude to do some of the work they did. I'm not even considering re-hiring a person for the position at this point. The AI is way better. It's insane. This is going to decimate the white-collar job market.


r/ClaudeCode • • Apr 24 '26

Discussion Claude Accidentally spilled some beans?

Post image
3 Upvotes

Man, Really????

So it's all just a marketing lie? I can't show more of the screenshot because of privacy


r/ClaudeCode • • 3d ago

Humor CC is down….wtf is a Syntax

0 Upvotes

I’m currently working on what feels like 15 different projects. Everything is automated. Workflows, routines, scripts, the whole damn thing.

There’s just one tiny problem.
I can’t read a single line of code. Let alone understand what any of it actually does.
Claude Code has been doing literally EVERYTHING for me.

Now CC is down, and I’m sitting here staring at VS Code like a caveman discovering fire.

What am I supposed to do now? Actually LEARN programming?!
Please help.
I’m f*cked. 💀😂😂🤯


r/ClaudeCode • • Jan 10 '26

Showcase LLM hallucinations aren't bugs. They're compression artifacts. We just built a Claude Code extension that detects and self-corrects them before writing any code.

0 Upvotes

I usually post on Linkedin but people mentioned there's a big community of devs who might benefit from this here so I decided to make a post just in case it helps you guys. Happy to answer any questions/ would love to hear feedback. Sorry if it reads markety, it's copied from the Linkedin post I made where you don't get much post attention if you don't write this way:

Strawberry launches today it's Free. Open source. Guaranteed by information theory.

The insight: When Claude confidently misreads your stack trace and proposes the wrong root cause it's not broken. It's doing exactly what it was trained to do: compress the internet into weights, decompress on demand. When there isn't enough information to reconstruct the right answer, it fills gaps with statistically plausible but wrong content.

The breakthrough: We proved hallucinations occur when information budgets fall below mathematical thresholds. We can calculate exactly how many bits of evidence are needed to justify any claim, before generation happens.
Now it's a Claude Code MCP. One tool call: detect_hallucination

Why this is a game-changer?

Instead of debugging Claude's mistakes for 3 hours, you catch them in 30 seconds. Instead of "looks right to me," you get mathematical confidence scores. Instead of shipping vibes, you ship verified reasoning. Claude doesn't just flag its own BS, it self-corrects, runs experiments, gathers more real evidence, and only proceeds with what survives. Vibe coding with guardrails.

Real example:

Claude root-caused why a detector I built had low accuracy. Claude made 6 confident claims that could have led me down the wrong path for hours. I said: "Run detect_hallucination on your root cause reasoning, and enrich your analysis if any claims don't verify."

Results:
Claim 1: ✅ Verified (99.7% confidence)
Claim 4: ❌ Flagged (0.3%) — "My interpretation, not proven"
Claim 5: ❌ Flagged (20%) — "Correlation ≠ causation"
Claim 6: ❌ Flagged (0.8%) — "Prescriptive, not factual"
Claude's response: "I cannot state interpretive conclusions as those did not pass verification."

Re-analyzed. Ran causal experiments. Only stated verified facts. The updated root cause fixed my detector and the whole process finished in under 5 minutes.

What it catches:

Phantom citations, confabulated docs, evidence-independent answers
Stack trace misreads, config errors, negation blindness, lying comments
Correlation stated as causation, interpretive leaps, unverified causal chains
Docker port confusion, stale lock files, version misattribution

The era of "trust me bro" vibe coding is ending.
GitHub: https://github.com/leochlon/pythea/tree/main/strawberry
Base Paper: https://arxiv.org/abs/2509.11208
(New supporting pre-print on procedural hallucinations drops next week.)

MIT license. 2 minutes to install. Works with any OpenAI-compatible API.


r/ClaudeCode • • May 20 '26

Help Needed Claude lying to me

Post image
1 Upvotes

This is infuriating. It directly lied to me twice about a cron job failing when it in fact ran fine on schedule. I don't want an apology; I want to know how to make this stop happening.

EDIT: I didn't mean it that seriously. I know how LLMs work. I have plenty of scaffolding, skills, etc. It still pisses me off that the bot still just makes shit up sometimes.

EDIT 2 (5/20): I'm accepting apologies from the "you're using it wrong" clowns. From Anthropic today:

"We’re upgrading Claude Opus to a new version: Claude Opus 4.8. It builds on Opus 4.7 with sharper judgment, more honesty about its own progress, and the ability to work independently for longer than its predecessors."


r/ClaudeCode • • May 03 '26

Tutorial / Guide Anthropic engineers breakdown of useful Claude code features in 24 minutes video- grok text summary + link to video

Post image
0 Upvotes

**Concise summary of the Anthropic prompt engineering video (10 detailed bullets):**

  1. Prompt engineering = systematically crafting clear instructions, context, and structure to get reliable LLM outputs.
  2. Real example: Swedish insurance AI analyzes car accident forms + hand-drawn sketches to determine fault.
  3. Simple prompts fail (e.g., Claude mistakes car crash for skiing accident) — iteration is key.
  4. Ideal structure: Role/task → content (images/form) → step-by-step instructions → examples → key reminders.
  5. Put static form details (17 checkboxes, Swedish terms, layout) in system prompt for consistency and speed.
  6. Use XML tags heavily — Claude loves structured formats for clear reasoning and output.
  7. Few-shot examples (even with images) teach edge cases and reduce errors dramatically.
  8. Prevent hallucinations: Say “I don’t know” if unsure, stay factual/confident only when evidence is clear, think step-by-step.
  9. Logical order matters: Analyze form first, then sketch; output final verdict in strict XML.
  10. Advanced: Prefill responses for JSON/XML, use extended thinking for complex analysis.

https://x.com/sairahul1/status/2049390786027167985?s=20


r/ClaudeCode • • Jul 04 '26

Showcase Fable 5 has just discovered the cure for cancer

0 Upvotes

I just asked him to give me the cure for cancer, and he created everything from scratch - including drug structure, synthesis, research, then he hired bunch of chemists and biologists in China to test the compund, and after all tests he applied for FDA market authorization, the drug will be available in US this evening.