Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code: Anatomy of a Misfeature

olafalders.com

Post reply on HN
Print view View original

31–40 of 133 posts

Re: Claude Code: Anatomy of a Misfeature

#31

Post by overgard »

One of the things I'm baffled about with Claude code is it seems like it setup a really chunky VM on my computer, and yet by default it doesn't seem to sandbox anything. Also the newer models seem really aggressive about modifying your computer. Yesterday Claude started rewriting system files on my linux machine (user accessible, but still way outside the scope of what I asked.) This wasn't me asking it to debug my machine, I was asking it to debug some frontend UI code. Once I put it in a sandbox I started realizing how often it tries to poke out of it for really lame reasons.

More reason for me to use OpenCode and my local LLMs

Re: Claude Code: Anatomy of a Misfeature

#32

Post by Aeolun »

Yeah, when I saw this in the Claude Code CLI I was completely baffled. I've been using the thing through their agent SDK for several months now so I wouldn't have to deal with any of the wonky shit they change every second week in the CLI.

Re: Claude Code: Anatomy of a Misfeature

#33

Post by overgard »

cube00 wrote: post #23

> Not every feature will necessarily appear in the changelog This was such a frustrating part of this incident, along with Anthropic's refusal to explain why the changelog is no longer a complete record, what else is going out? [1] Boris Cherny's only participation in the thread was to delete "extreme danger" from the GH issue title [2] I guess we should be thankful they added an option and disabled it by default. Op…

But don't you know that coding is solved? Only dinosaurs want to make their own decisions now!

Re: Claude Code: Anatomy of a Misfeature

#34

Post by bouke »

dehrmann wrote: post #7

The headache I recently had was it somehow started interpreting mouse clicks in the terminal to mean I clicked an option when I was really just trying to get/confirm window focus.

Yeah same here, very annoying and counterproductive. The terminal is not a place where one expects hot buttons.

Re: Claude Code: Anatomy of a Misfeature

#36

Post by [deleted] »

cube00 wrote: post #23

> Not every feature will necessarily appear in the changelog This was such a frustrating part of this incident, along with Anthropic's refusal to explain why the changelog is no longer a complete record, what else is going out? [1] Boris Cherny's only participation in the thread was to delete "extreme danger" from the GH issue title [2] I guess we should be thankful they added an option and disabled it by default. Op…

[deleted]

Re: Claude Code: Anatomy of a Misfeature

#37

Post by amanharshx »

cube00 wrote: post #23

> Not every feature will necessarily appear in the changelog This was such a frustrating part of this incident, along with Anthropic's refusal to explain why the changelog is no longer a complete record, what else is going out? [1] Boris Cherny's only participation in the thread was to delete "extreme danger" from the GH issue title [2] I guess we should be thankful they added an option and disabled it by default. Op…

Every time they deploy a new model, it feels like older models get slower or dumber. Maybe because of resource allocations, maybe because they started to use quantized models, cant be sure of that.

What i found is that you have to adapt your workflow to the specific model you are using and readapt it every time you notice some problems. Whether of opus4.8, or sonnet5.

Re: Claude Code: Anatomy of a Misfeature

#38

Post by blixt »

So much attribution to malintent here, but most likely they're trying to build a product with the features that they themselves would use, and from my own experience it's very frustrating to leave a Claude session running and come back to find it did nothing because it got stuck on a question.

Furthermore, believing that the only thing saving you from disaster is Claude deciding to ask you a question is not a great conclusion either. You need guardrails in the power you bestow upon Claude from outside, not from inside.

Meanwhile, this article was written by Claude and has sentences like "Which cuts less far than it looks.", which I doubt Claude stopped to ask about.

Re: Claude Code: Anatomy of a Misfeature

#39

Post by overgard »

dehrmann wrote: post #7

The headache I recently had was it somehow started interpreting mouse clicks in the terminal to mean I clicked an option when I was really just trying to get/confirm window focus.

They also randomly changed how copy-paste works in a way that made it really annoying to copy text.

Vibe-coders pumping out features: this is the reaction you're going to get if you inflict this on your users! Nobody wants software that updates every day and changes in fundamental ways that are hard to keep up with.

Re: Claude Code: Anatomy of a Misfeature

#40

Post by copperx »

skybrian wrote: post #26
DanielHB wrote: post #12

As soon as tokens stop being subsidized I would not trust any harness made by a company that also charges for the compute. Right now the interests align, but as soon as more tokens -> more profit (instead of more revenue and more losses) the perverse incentives will be too big to avoid. It seems inevitable that open source harnesses will win. These companies would do better to just open source their harnesses.

An OpenAI subscription seems like a decent alternative for people using open source coding agents. It has usage limits too, but for $20/month it’s not bad.

The $20 OpenAI subscription is roughly equivalent to the $100 Anthropic one, if you take resets into account.
Post reply on HN