Claude Code Loses the Thread on Real Codebases
Developers are experiencing frustration with Claude Code's performance, citing issues like inaccurate code generation, failure to follow through on tasks, hallucinations, and disruptive interruptions. These problems hinder productivity and require significant manual oversight, undermining the promise of autonomous coding assistance. The rapid release cycle and community reactions further complicate the user experience.
SOURCES (60)
“you know what i hate? i hate that each update, to codex or claude code, it seems like they're always trying to "hide stuff" , reminds me of the 80s and 90s when tech assumes normal people are too stupid to see 'raw' stuff like…”
I am working on an app where I have integrated Claude. The current setup is that I send Claude a list of symptom names along with the user’s input, and Claude returns…
[Claude] ★ 1/5 (v1.260716.0) — Is often giving me wrong information. Claude is not very trustworthy!
[Claude] ★ 1/5 (v1.260716.0) — claude is getting worse with each update. it used to be fun to use. now it responds as if this tool is in charge and as if…
“I spent a lot of time improving my Claude Code prompts when the bigger problem was that every cloud session started cold. Each session runs on a real cloud VM included with my Claude subscription. It can clone private repos, install dependencies, run tests, access the internet, and keep working after my laptop is closed. But I was treating it like a temporary chat: attach a repo, explain the project, describe our conventions, give it the task, then repeat everything next time. The unlock was pre”
“Curious do you have any type of eval or review to see how accurate your synthesis is?”
“Shame really, his first task and he's already bust the code. Claude on the other hand absolutely aces both but for final review chatgpt always wins hands down. I was hoping 5.6 would be a better coder, alas, maybe 5.7? submitted by /u/terraslate [link] [comments]”
“this is absolutely true, there's countless time I was angry at opus 4.8 because how bad it was at structuring code”
“Claude Code Opus 5 and Fable 5 both fail at basic things when creating UI. Of course it looks generic AF. But it also has blatant problems like each button styled a bit differently, completely half-assing most URL work and stuff clearly clipped through the container or the viewport. To be fair AI works damn well for backend, systems, cryptography, backend-in-the-fromtend work. And I am using the Chrome MCP to let it auto-debug in the browser etc and (only a couple) other skills. Are your results”
“You need to create custom AI Skill Pages and use them more properly for what you need. Then use the proper model.”
“Opus 4.8 . Used max but it blasts way too much unnecessarily, so I tend towards the high variant, and max when I need more thorough planning. Opencode.”
“Almost everyone still uses Claude as a code generator: it writes code, you copy it out, you run it, it breaks, you paste the error back. That loop is dead and most people have not noticed. Claude can now write the code, run it itself, see the actual output, catch its own errors, and iterate until it works, then hand you the verified result. You stop being the one who runs and debugs it. Don't just write code for this. Actually run it, check the output, and fix it yourself before you show me”
“Which would you prefer to use for development, and why? Claude Code extension in VS code or Claude Code desktop app? submitted by /u/raj-kateshiya [link] [comments]”
“Ditch ugly harness which penalize custom models, use opencode / smallcode ( Cline was working but is worse each update, and now after 3 retries suggests you to use Claude )”
“I work in this area and this is the correct answer. The models matter but the harnesses sometimes matter more . You can see this directly if you compare something like Cursor + Opus with Claude Code + Opus. It's not only workflow niceities like /loop / /goal or /btw or skills or what not, it's also the way in which the system prompt and agent instructions (e.g CLAUDE.md) gets integrated with your base prompt and how that is reported to the model. It's the way the context window gets”
“Claude’s models (Sonnet and Opus) are well regarded to be the best at generating code. OpenAI’s GPT models are good for reasoning and question/answer without being too expensive. At work, we don’t want to have a mess of AI subscriptions, and we don’t want to get yanked around as the AI wars drag on and they leapfrog each other. So we thought GitHub Copilot would be a good way to access the various models while avoiding vendor lock-in. A layer of abstraction, if you will. Even with Copilot’s bill”
“As IT engineers or sys admins what are you building in Claude code? Do we collectively know how safe it is to build and deploy into core tools?”
“Most people use Claude the same way every time. The new update (Opus 4.8) lets you tell it how much effort to put in. On Max effort it reasons through multiple approaches and flags where it's uncertain instead of just agreeing with you. This is the prompt I run on Max effort before any decision that actually matters: Maximum effort on this. Don't rush it. I'm deciding: [the decision] I'm leaning toward: [your option] because [reasons] Argue”