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

101–110 of 133 posts

Re: Claude Code: Anatomy of a Misfeature

#101

Post by inigyou »

oalders wrote: post #46
blixt wrote: post #38

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

>Meanwhile, this article was written by Claude The prose was written by me, with the research being done by Claude and also clearly attributed. I left Claude's research as a series of bullet points so that it would be clear that I'm not passing off an LLM's work as my own, but if anyone wants to dig deeper, they have some starting points to consider. I don't publish prose written by an LLM for the same reason I would…

The article was obviously written by an LLM, it's obviously from the overall structure as well as individual sentences. Maybe you've been exposed to so much LLM text that you write identically to one, in which case, yikes!

Re: Claude Code: Anatomy of a Misfeature

#102

Post by allenu »

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.

I really hate that change. It's counterintuitive that a shell recognizes mouse clicks to mean "select this option".

Also, the auto-copy selected text feature is awful. That's another thing that is so counterintuitive. I have never seen a UI where just selecting text means auto-copy to the paste buffer. Who is coming up with these awful UX ideas?

On top of that, the scroll "feel" of the new client (at least on macOS) isn't quite as good as their old one. It just feels off and not like a native terminal.

Re: Claude Code: Anatomy of a Misfeature

#103

Post by grim_io »

brabel wrote: post #69
randysalami wrote: post #59

Earlier quoted context omitted.

I read the article but I find this response kind of strange. Am I alone in this? Wanton accountability for a multi-billion dollar cutting edge company… leaves more to be desired from the best? Take Apple or Google or any top tech company of the past at its prime and compare. This kind of behavior then would probably reflect poorly on the institutions behind the tech and not maintain their image of technical brillianc…

> it shows weakness in a vulnerable way. It is human. It is not strategic. Are you complaining that the answer is too human and that a multi billion company should not allow a human who made a mistake to own the mistake in public, being honest about what happened in this case?? Would you prefer complete silence from them like you most certainly would from Google or Apple. That sounds incredibly sad to me, we don’t ev…

Not the person you asked.

I expect the person responsible for Claude Code to explain the reason this direction was chosen.

It is ridiculous to expect individual contributors to do so.

Where is the leadership? Can individual contributors decide to significantly alter the workflow of millions of customers? Were any customers consulted at all?

Re: Claude Code: Anatomy of a Misfeature

#104

Post by ubermon »

enraged_camel wrote: post #10

I think this is a good feature, but should be gated behind a toggle that is off by default, and designed to be enabled per session via prompt. There are situations when I want Claude to start working on something just as I'm about to head to bed or otherwise step away. It's kind of annoying to come back only to find that Claude worked for just 5 minutes and then decided to pause and ask a question. That said, I think…

we need a real agent that represent our own interest and deal with a more powerful general agents. And we can delegate answering this question to those more personal agents.

Re: Claude Code: Anatomy of a Misfeature

#105

Post by FunHearing3443 »

cube00 wrote: post #86
trq_ wrote: post #82

Earlier quoted context omitted.

I did make the decision, and shipped the PR.

There has to be a second PR approver. There's no way a company as large this can allow an individual the ability to push to production without a secondary person involved. When there's at least two people involved you can then start to look at more systematic factors that go beyond any single human mistake. When both the submitter and approver miss that there's no changelog entry for a PR does that mean a checklist i…

If there really is no PR reviewer and no separate QA what is Anthropic even doing. I have respect for someone owning their mistake but as others have mentioned it reveals what may be a systemic issue.

Re: Claude Code: Anatomy of a Misfeature

#106

Post by grim_io »

trq_ wrote: post #82
Jcampuzano2 wrote: post #79

Earlier quoted context omitted.

> It's Thariq from the Claude Code team here. This was my change! I made the AskUserQuestion tool so am generally in charge of maintaining it. In a sense yes, I think it is actually reasonable to complain that the answer is too human/individualized here because it likely wasn't this individual human who made this decision, but he's making it seem like it is so that we are less likely to blame the company as a whole.…

I did make the decision, and shipped the PR.

I don't really care, in a most positive way towards you.

I don't hold you accountable even if you twirled your mustache like a villain. You are not responsible for Claude Code. Why did the leadership set up such a weak, error-prone process?

Again, not asking you directly, because it doesn't matter to me what you say, respectfully.

Re: Claude Code: Anatomy of a Misfeature

#107

Post by redhale »

blixt wrote: post #38

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

Come on now, arguing it's a good feature is different than arguing that it should be turned on by default for everyone with no documented option to turn it off.

I like this feature as an OPTION that is DOCUMENTED. But that's not how it was rolled out. The CC team + processes clearly failed here. And this is far from the first example of this kind of slopiness.

I don't think it was malicious, but I do think it was quite obviously reckless/careless, and I feel like most of the comments here match that sentiment. Everyone and every team makes mistakes, but unfortunately I don't see the CC team really learning from those mistakes even though they keep happening.

CC is not a stable or reliable tool, it is bleeding edge, and that's a tradeoff you make when you pick it over other harnesses.

Re: Claude Code: Anatomy of a Misfeature

#108

Post by bostik »

hungryhobbit wrote: post #48
overgard wrote: post #39

Earlier quoted context omitted.

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.

THIS ONE IS HORRIBLE ! Copy/paste is one of the most basic, low-level features of a modern operating system. NO APPLICATION SHOULD EVER SCREW WITH IT, IN ANY WAY! And I say this not just as a seriously annoyed user, but also as a professional UI developer: it is a well-known anti-pattern to override the user's expectations, at any level ... and that applies tenfold to the most basic patterns that every other app foll…

> Copy/paste is one of the most basic, low-level features of a modern operating system. NO APPLICATION SHOULD EVER SCREW WITH IT, IN ANY WAY!

-Ghostty enters the chat-

Middle-click paste in Ghostty is hazardous: the damn thing can move your cursor to the position of your mouse pointer and paste there. An utterly infuriating behaviour - it is a text terminal. It has no business emulating the usability crimes GUIs first committed and then committed to.

Re: Claude Code: Anatomy of a Misfeature

#109

Post by bostik »

allenu wrote: post #102
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.

I really hate that change. It's counterintuitive that a shell recognizes mouse clicks to mean "select this option". Also, the auto-copy selected text feature is awful. That's another thing that is so counterintuitive. I have never seen a UI where just selecting text means auto-copy to the paste buffer. Who is coming up with these awful UX ideas? On top of that, the scroll "feel" of the new client (at least on macOS)…

> I have never seen a UI where just selecting text means auto-copy to the paste buffer.

Isn't this the default behaviour of every X application since the 1990's?

Re: Claude Code: Anatomy of a Misfeature

#110

Post by petesergeant »

trq_ wrote: post #82
Jcampuzano2 wrote: post #79

Earlier quoted context omitted.

> It's Thariq from the Claude Code team here. This was my change! I made the AskUserQuestion tool so am generally in charge of maintaining it. In a sense yes, I think it is actually reasonable to complain that the answer is too human/individualized here because it likely wasn't this individual human who made this decision, but he's making it seem like it is so that we are less likely to blame the company as a whole.…

I did make the decision, and shipped the PR.

Habibi, I don't think anyone is really blaming you personally. We are piling on to the fact that this piece of critical infrastructure many of us depend on day in day out is being built in such a way that a single developer can wake up one morning, ship a change they thought might be nice, and then walk it back the next day.
Post reply on HN