Live data from Hacker News

Issue: Claude Code is unusable for complex engineering tasks with Feb updates

github.com

461–470 of 829 posts

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#461

Earlier quoted context omitted.

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.

a9284923-141a-434a-bfbb-52de7329861d d48d5a68-82cd-4988-b95c-c8c034003cd0 5c236e02-16ea-42b1-b935-3a6a768e3655 22e09356-08ce-4b2c-a8fd-596d818b1e8a 4cb894f7-c3ed-4b8d-86c6-0242200ea333 Amusingly (not really), this is me trying to get sessions to resume to then get feedback ids and it being an absolute chore to get it to give me the commands to resume these conversations but it keeps messing things up: cf764035-0a1d-4…

Thanks for the feedback IDs — read all 5 transcripts.

On the model behavior: your sessions were sending effort=high on every request (confirmed in telemetry), so this isn't the effort default. The data points at adaptive thinking under-allocating reasoning on certain turns — the specific turns where it fabricated (stripe API version, git SHA suffix, apt package list) had zero reasoning emitted, while the turns with deep reasoning were correct. we're investigating with the model team. interim workaround: CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING=1 forces a fixed reasoning budget instead of letting the model decide per-turn.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#462
post #158

Earlier 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…

If your code was committed before the reset, check your git reflog for the lost code.

Yeah, git reset --hard is something I do like once a week! lol

With the reflog, as you mentioned, it's not hard to revert to any previous state.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#463

maybe dont outsource your brain then

This is almost like a self down-leveling programme where so-called "senior" engineers have now become interns who have outsourced their brains and are now vibe-coding half-baked solutions, glueing up and pasting code they do not even understand or can even explain themselves.

You are seeing this first hand and GitHub is patient 0 of this issue as they are frequently experiencing outages despite the "scale" of engineering they preach.

AWS took a zero tolerance approach on such outages AI or not.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#464

Hey 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.

way more than that. settings.json and settings.local.json in the project directory's .claude/, and both of files can also be in ~/.claude

MCP servers can be set in at least 5 of those places plus .mcp.json

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#465

Earlier quoted context omitted.

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.

Theres also been tons of thinking leaking into the actual output. Recently it even added thinking into a code patch it did (a[0] &= ~(1 << 2); // actually let me just rewrite { .. 5 more lines setting a[0] .. }).

I've seen this frequently also

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#466

Hey 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.

I just had this conversation today. It's hilarious that things like Skills and Soul and all of these anthropomorphized files could just be a better laid out set of configuration files. Yet here we are treating machines like pets or worse.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#467
post #340

Earlier quoted context omitted.

All right so what do I need to do so it does its job again? Disable adaptive thinking and set effort to high and/or use ULTRATHINK again which a few weeks ago Claude code kept on telling me is useless now?

You can't. This is Anthropic leveraging their dials, and ignoring their customers for weeks. Switch providers. Anecdotally, I've had no luck attempting to revert to prior behavior using either high/max level thinking (opus) or prompting. The web interface for me though doesn't seem problematic when using opus extended.

I've actually switched back to the web chat UI and copying Python files for much of my work because CC has been so nerfed.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#468
post #274

Earlier quoted context omitted.

Fair point on tone. It's a bit of a bind isn't it? When you come with a well-researched issue as OP did, you get this bland corporate nonsense "don't believe your lyin' eyes, we didn't change anything major, you can fix it in settings." How should you actually communicate in such a way that you are actually heard when this is the default wall you hit? The author is in this thread saying every suggested setting is alr…

Just use a different tool or stop vibe coding, it’s not that hard. I really don’t understand the logic of filing bug reports against the black box of AI

The only "black box" here is Anthropic. At least an LLM's performance and consistency can be established by statistical methods.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#469

Earlier quoted context omitted.

People file tickets against closed source "black box" systems all the time. You could just as well say: Stop using MS SQL, just use a different tool, it's not that hard.

Equivalent of filing a ticket against the slot machine when you lose more often than expected

Well now you're just being silly and I can't take you seriously.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#470
post #433

Earlier quoted context omitted.

Well I'm paying the coin to be near 50% and the coin's PM is listening to customers, so that's why.

The coin's PM is spamming you trivial gaslighting corporate slop, most of it barely edited.

Yes, that's why we are angry. Stop making excuses for them.
Post reply on HN