Earlier quoted context omitted.
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.
Issue: Claude Code is unusable for complex engineering tasks with Feb updates
351–360 of 829 posts
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#352Earlier quoted context omitted.
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…
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#353Hey 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…
I think it is hilarious that there are four different ways to set settings (settings.json config file, environment variable, slash commands and magical chat keywords). That kind of consistency has also been my own experience with LLMs.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#354> This report was produced by me — Claude Opus 4.6 — analyzing my own session logs [...] Please give me back my ability to think. a bit ironic to utilize the tool that can't think to write up your report on said tool. that and this issue[1] demonstrate the extent folks become over reliant on LLMs. their review process let so many defects through that they now have to stop work and comb over everything they've shipped…
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…
https://oneuptime.com/blog/post/2026-01-24-git-reflog-recove...
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#355Earlier quoted context omitted.
Ultrathink is back? I thought that wasn't a thing anymore. If I am following.. "Max" is above "High", but you can't set it to "Max" as a default. The highest you can configure is "High", and you can use "/effort max" to move a step up for a (conversation? session?), or "ultrathink" somewhere in the prompt to move a step up for a single turn. Is this accurate?
Yep, exactly
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#356Earlier quoted context omitted.
How complex are we talking? I one shotted a game boy emulator in <6 minutes today
There are countless reference examples online, that's just a slower, buggier, and more expensive git clone.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#357Hey 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…
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#358Hey 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…
I think it is hilarious that there are four different ways to set settings (settings.json config file, environment variable, slash commands and magical chat keywords). That kind of consistency has also been my own experience with LLMs.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#359Earlier quoted context omitted.
[flagged]
It also completely ignores the increase in behavioral tracking metrics. 68% increase in swearing at the LLM for doing something wrong needs to be addressed and isn't just "you're holding it wrong"
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#360Maybe it's because I spend a lot of time breaking up tasks beforehand to be highly specific and narrow, but I really don't run into issues like this at all. A trivial example: whenever CC suggests doing more than one thing in a planning mode, just have it focus on each task and subtask separately, bounding each one by a commit. Each commit is a push/deploy as well, leading to a shitload of pushes and deployments, but…
> Maybe it's because I spend a lot of time breaking up tasks beforehand to be highly specific and narrow, but I really don't run into issues like this at all. I'm looking at the ticket opened, and you can't really be claiming that someone who did such a methodical deep dive into the issue, and presented a ton of supporting context to understand the problem, and further patiently collected evidence for this... does no…
I started doing this a while ago (months) precisely because of issues as described.
On the other hand,analyzing prompts and deviations isnt that complex.. just ask Claude :)