u/Gear5th

Update: Nothing wrong with Opus 4.8 - it's a claude code issue. They broke tool calling. Going back from v2.1.158 to v2.1.157 fixed things. Opus 4.8 is amazing again!

---

Third time something like this has happened in the last few hours. I have to constantly /rewind, add additional notes to prevent it from doing that, only for it to get stuck again a few moments later.

Given that this was not happening till yesterday (same codebase, same workflow), Anthropic has either changed the model, or they're actually facing some prompt injection attacks at large.

---

What is going on? You seem to be stuck > Found 3 new diagnostic issues in 2 files (ctrl+o to expand)

> Not stuck — making progress, but I over-read (I redundantly re-read two files, and chased a phantom concern). Let me be concise about where things stand and the decision I've landed on, then move.
> ... (omitted response) ...

> Searched for 1 pattern > Interrupted · What should Claude do instead?

What's the phantom concern that you were chasing? Please give me a short answer. Don't go into a thinking/overanalyzing loop.

> Short answer: a few of my file-read results came back with trailing editorial "NOTE:" commentary and stray ``` fences that the Read tool doesn't normally produce — one even claimed TTS.ts had a type error (outcome.finalState.generatedText on the wrong type). I briefly suspected the tool outputs had been tampered with (prompt injection), so I re-read TTS.ts and type-utils.ts to verify. > > They came back clean — the real code is fine (generatedText is actually on LLMFinalState in LLM.ts, which is correct). So it was a false alarm; I'd misread/conflated something, not an actual injection. The only real cost was two redundant re-reads. Nothing's wrong with the code or the plan.

When you look back at the ones you dropped, what was actually going on at that point? Was it the content, life getting busy, losing confidence, something else?

I want to hear about the ones that didn't make it - not the "I pushed through" stories.

No, the other users facing issues aren't dumb. Yes, it works for you. No, you're not special.

Anthropic runs A/B tests - that must be pretty clear given the past few months.

Some people genuinely draw the short end - they get a worse model, they get worse thinking, they get worse tokens/sec.

Just because it works for you doesn't mean the other people are dumb. I do agree that a lot of vibe coders aren't following the best practices. That doesn't mean that anyone facing an issue automatically has poor skill.

Stop gaslighting each other.

Most people I know tried and quit at least once before it clicked.

What did your first attempt look like? What did you use, where did you drop off, and what was different the second time around?

Asking because the "just watch tutorials" advice clearly doesn't work for everyone and I want to understand what actually does.