511–520 of 732 posts
Earlier quoted context omitted.
VSCode (xterm.js) is one of the worst, but there's a large long tail of slow terminals out there.
Not really using VS Code terminal anymore, just Ubuntu terminal but the biggest problem I have is that at some point Claude just eats up all memory and session crashes. I know it's not really Claude's fault but damn it's annoying.
Hey, Boris from the Claude Code team here. I wanted to take a sec to explain the context for this change. One of the hard things about building a product on an LLM is that the model frequently changes underneath you. Since we introduced Claude Code almost a year ago, Claude has gotten more intelligent, it runs for longer periods of time, and it is able to more agentically use more tools. This is one of the magical th…
Earlier quoted context omitted.
I don't know how to say this but either you haven't written any complex code or your definition of complex and impossible is not the same as mine, or you are "ai hyper booster clickbaiting" (your words). It strains belief that anyone working on a moderate to large project would not have hit the edge cases and issues. Every other day I discover and have to fix a bug that was introduced by Claude/Codex previously (some…
I resent your implication that I am baselessly hyping. I've open sourced a few Opus 4.5-coded projects ( https://news.ycombinator.com/item?id=46543359 ) ( https://news.ycombinator.com/item?id=46682115 ) that while not moderate-to-large projects, are very niche and novel without much if any prior art. The prompts I used are included with each those projects: they did not "run and look fine" on first run, and were refi…
I think you and I have different definitions of “one-shotting”. If the model has to be steered, I don’t consider that a one-shot.
And you clearly “broke” the model a few times based on your prompt log where the model was unable to solve the problem given with the spec.
Honestly, your experience in these repos matches my daily experience with these models almost exactly.
I want to see good/interesting work where the model is going off and doing its thing for multiple hours without supervision.
Hey, Boris from the Claude Code team here. I wanted to take a sec to explain the context for this change. One of the hard things about building a product on an LLM is that the model frequently changes underneath you. Since we introduced Claude Code almost a year ago, Claude has gotten more intelligent, it runs for longer periods of time, and it is able to more agentically use more tools. This is one of the magical th…
> Yoshi and others -- please keep the feedback coming. We want to hear it, and we genuinely want to improve the product in a way that gives great defaults for the majority of users, while being extremely hackable and customizable for everyone else.
I think an issue with 2550 upvotes, more than 4 times of the second-highest, is very clear feedback about your defaults and/or making it customizable.
Earlier quoted context omitted.
> We can no longer design for ourselves, and we rely heavily on community feedback to co-design the right experience. We cannot build the right things without that feedback. How can that be true, when you're deliberately and repeatedly telling devs (the community you claim to listen to) that you know better than they do? They're telling you exactly what they want, and you're telling them, "Nah." That isn't listening.…
interesting. they have been pretty receptive to my pull comments and discourse on issues. To each's anecdote I suppose.
Earlier quoted context omitted.
> I don't want verbose mode. I want Claude to tell me what it's reading in the first 3 seconds, so I can switch gears without fear it's going to the wrong part of the codebase. By saying that my use case requires verbose mode, you're saying that I need to see massive levels of babysitting-level output (even if less massive than before) to be able to do this. To be clear: we re-purposed verbose mode to do exactly what…
> To be clear: we re-purposed verbose mode to do exactly what you are asking for. We kept the name "verbose mode", but the behavior is what you want, without the other verbose output. Verbose mode feels far too verbose to handle that. It’s also very hard to “keep your place” when toggling into verbose mode to see a specific output.
Hey, Boris from the Claude Code team here. I wanted to take a sec to explain the context for this change. One of the hard things about building a product on an LLM is that the model frequently changes underneath you. Since we introduced Claude Code almost a year ago, Claude has gotten more intelligent, it runs for longer periods of time, and it is able to more agentically use more tools. This is one of the magical th…