[dead]
Issue: Claude Code is unusable for complex engineering tasks with Feb updates
211–220 of 829 posts
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#212Same experience. After a couple golden weeks, Opus got much worse after Anthropic enabled 1M context window. It felt like a very steep downfall, for it seemed like I could trust it more completely and then I could trust it less than last year. Adopting LLMs for dev workflows has been fantastic overall, but we do have to keep adapting our interactions and expectations every day, and assume we'll keep on doing it for a…
Yeah I think the 1M context is the issue. Because I use Opus 4.6 through Cursor at the previous 200k limit and it has been totally fine. But if I switch to the 1M version it degrades noticeably.
> Yeah I think the 1M context is the issue. Because I use Opus 4.6 through Cursor at the previous 200k limit and it has been totally fine. But if I switch to the 1M version it degrades noticeably.
I thought it was already well-known that context above 200k - 300k results in degradation.
One of my more recent comments this past week was exactly that - that there was no point in claiming that a 1m context would improve things because all the evidence we have seen is that after 300k context, the results degrade.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#213Earlier quoted context omitted.
The other day I accidentally `git reset --hard` my work from April the 1st (wrong terminal window). Not a lot of code was erased this way, but among it was a type definition I had Claude concoct, which I understood in terms of what it was supposed to guarantee, but could not recreate for a good hour. Really easy to fall into this trap, especially now that results from search engines are so disappointing comparatively…
> but could not recreate for a good hour. For certain work, we'll have to let go of this desire. If you limit yourself to whatever you can recreate, then you are effectively limiting the work you can produce to what you know.
you should limit your output (manual or assisted) to a level that is well under your understanding ceiling.
Kernighan’s Law states that debugging is twice as hard as writing. how do you ever intend on debugging something you can’t even write?
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#214Hey all, Boris from the Claude Code team here. I just responded on the issue, and cross-posting here for input. --- Hi, thanks for the detailed analysis. Before I keep going, I wanted to say I appreciate the depth of thinking & care that went into this. There's a lot here, I will try to break it down a bit. These are the two core things happening: > `redact-thinking-2026-02-12` This beta header hides thinking from th…
How do you guys manage regressions as a whole with every new model update? A massive test set of e2e problem solving seeing how the models compare?
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#215Not claude code specific, but I've been noticing this on Opus 4.6 models through Copilot and others as well. Whenever the phrase "simplest fix" appears, it's time to pull the emergency break. This has gotten much, much worse over the past few weeks. It will produce completely useless code, knowingly (because up to that phrase the reasoning was correct) breaking things. Today another thing started happening which are…
> Whenever the phrase "simplest fix" appears, it's time to pull the emergency break. Second! In CLAUDE.md, I have a full section NOT to ever do this, and how to ACTUALLY fix something. This has helped enormously.
I switched from Cursor to Claude because the limits are so much higher but I see Anthropic playing a lot more games to limit token use
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#216Its so silly everyone being dependent on a black box like this
> Its so silly everyone being dependent on a black box like this
It's the logical result of "You will own nothing and you will be happy"... You are getting to the point where you won't even own thoughts (because they'll come from the LLM), but you'll be happy that you only have to wait 5 hours to have thoughts gain.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#217Hey all, Boris from the Claude Code team here. I just responded on the issue, and cross-posting here for input. --- Hi, thanks for the detailed analysis. Before I keep going, I wanted to say I appreciate the depth of thinking & care that went into this. There's a lot here, I will try to break it down a bit. These are the two core things happening: > `redact-thinking-2026-02-12` This beta header hides thinking from th…
There's been more going on than just the default to medium level thinking - I'll echo what others are saying, even on high effort there's been a very significant increase in "rush to completion" behavior.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#218My bet: LLMs will never be creative and will never be reliable. It is a matter of paradigm. Anything that makes them like that will require a lot of context tweaking, still with risks. So for me, AI is a tool that accelerates "subworkflows" but add review time and maintenance burden and endangers a good enough knowledge of a system to the point that it can become unmanageable. Also, code is a liability. That is what…
We don't even know what 'creativity' is, and most humans I know are unable to be creative even when compelled to be. AI is 'creative enough' - whether we call it 'synthetic creativity' or whatever, it definitely can explore enough combinations and permutations that it's suitably novel. Maybe it won't produce 'deeply original works' - but it'll be good enough 99.99% of the time. The reliability issue is real. It may n…
Maybe I do not have a good definition for it.
But what I see again and again in LLMs is a lot of combinations of possible solutions that are somewhere around internet (bc it put that data in). Nothing disruptive, nothing thought out like an experimented human in a specific topic. Besides all the mistakes/hallucinations.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#219Hey all, Boris from the Claude Code team here. I just responded on the issue, and cross-posting here for input. --- Hi, thanks for the detailed analysis. Before I keep going, I wanted to say I appreciate the depth of thinking & care that went into this. There's a lot here, I will try to break it down a bit. These are the two core things happening: > `redact-thinking-2026-02-12` This beta header hides thinking from th…
There's been more going on than just the default to medium level thinking - I'll echo what others are saying, even on high effort there's been a very significant increase in "rush to completion" behavior.
Thanks for the feedback. To make it actionable, would you mind running /bug the next time you see it and posting the feedback id here? That way we can debug and see if there's an issue, or if it's within variance.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#220Hey all, Boris from the Claude Code team here. I just responded on the issue, and cross-posting here for input. --- Hi, thanks for the detailed analysis. Before I keep going, I wanted to say I appreciate the depth of thinking & care that went into this. There's a lot here, I will try to break it down a bit. These are the two core things happening: > `redact-thinking-2026-02-12` This beta header hides thinking from th…
How do you guys manage regressions as a whole with every new model update? A massive test set of e2e problem solving seeing how the models compare?
A mix of evals and vibes.