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

21–30 of 133 posts

Re: Claude Code: Anatomy of a Misfeature

#21

Post by wgd »

maxloh wrote: post #2

> What if the agent makes the wrong choice? How many tokens have been burned in the meantime? It is much worse than that. Claude Code doesn't auto-commit when stopping for an answer. There might be possible data loss if an uncommitted file is edited. Good luck recovering the file from the JSONL conversation history.

It's actually pretty straightforward to recover file-states from conversation history. I accidentally deleted the wrong repo on my machine once and recreated all the lost work from agent chat history. It is, ironically, the sort of task which AI agents excel at.

Re: Claude Code: Anatomy of a Misfeature

#23

Post by cube00 »

> 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. OpenAI is standing firm on their decision to not allow their 60s timeout to be disabled, [3] however more of the Codex harness is open source so customers have been able to fork it to add the option themselves.

[1]: https://github.com/anthropics/claude-code/issues/73125

[2]: https://github.com/anthropics/claude-code/issues/73125#event...

[3]: https://github.com/openai/codex/issues/28969

Re: Claude Code: Anatomy of a Misfeature

#24

Post by hombre_fatal »

the_gipsy wrote: post #16
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.

The new fullscreen UI is really bad. The old one (scrolling) starts to bug out after a while, but it van just be restarted and resumed.

Both Claude Code and Codex have issues overwriting or duplicating text for me when scrolling.

Probably from trying to keep scrollback virtual while anticipating terminal resize. But I wouldn't mind a way to opt back in to naive, unlimited convo scrollback.

Re: Claude Code: Anatomy of a Misfeature

#25

Post by petesergeant »

macNchz wrote: post #17
petesergeant wrote: post #6

Also: https://news.ycombinator.com/item?id=48766895 I would love Claude Code to be a little less vibe-coded. The underlying model is excellent, but we're being pretty much forced into using CC to use the subscription model.

I am a longtime and heavy Claude Code user, but Anthropic's product management overall (including for their Desktop/web products) has been really baffling me. I agree that these things often have the air of having been vibe coded without enough human input, and change so quickly (often without a particularly compelling reason for the change) as to be aggravating. The most recent one that's had me annoyed is the "Full…

Yah. And it's not like they can't afford the talent to do this right either. I've said elsewhere, I think it's an attribution error. Claude Code is massively popular, but arguably because of the model/subscription, but I think the brass reads this as "great success throughout"

Re: Claude Code: Anatomy of a Misfeature

#26

Post by skybrian »

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.

Re: Claude Code: Anatomy of a Misfeature

#27

Post by mey »

kenny11 wrote: post #15
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.

This bit me too. If I wanted a mouse-driven app, I'd use the GUI. I don't understand why they're trying to replicate that experience in a text environment.

Vibes

Re: Claude Code: Anatomy of a Misfeature

#30

Post by fractorial »

tl;dr CLAUDE_AFK_TIMEOUT_MS=2147483647

I built in Human blockers into my agentic workflows with great intention, so naturally this annoyed me deeply. 14d ago, I was elated to see a random blog post that detailed the “fix” [0].

[0] https://zenn.dev/ytkdm/articles/claude-code-askuserquestion-...

Post reply on HN