Earlier quoted context omitted.
I think folks might be crossing wires a bit. To make it so you can see full file paths, we repurposed verbose mode to enable the old explicit file output, while hiding more details behind ctrl+o. In effect, we've evolved verbose mode to be multi-state, so that it lets you toggle back to the old behavior while giving you a way to see even more verbose output, while still defaulting everyone else to the condensed view.…
How do you respond to the comment that; given the log trace: “Did something 2 times” That may as well not be shown at all in default mode? What useful information is imparted by “Read 4 files”? You have two issues here: 1) making verbose mode better. Sure. 2) logging useless information in default. If you're not imparting any useful information, claude may as well just show a spinner.
Claude Code is being dumbed down?
421–430 of 732 posts
Re: Claude Code is being dumbed down?
#422Earlier quoted context omitted.
But I used to be a skeptic but now in the last month
Yes, as all of modern politics illustrates, once one has staked out a position on an issue it is far more important to stick to one's guns regardless of observations rather than update based on evidence.
Re: Claude Code is being dumbed down?
#423Earlier quoted context omitted.
I understand not exposing a full stack trace, but I don't see any excuse to not even expose a googleable error code. If me having an error code makes your product insecure, then you have a much bigger problem.
I show the stack trace on AGPL projects. Why hide what they can already see for themselves?
Re: Claude Code is being dumbed down?
#424Earlier quoted context omitted.
In what terminals is rendering slow? I really think GPU acceleration for terminals (as seen in Ghostty) is silly. It's a terminal. Edit: I can't post anymore today apparently because of dang. If you post a comment about a bad terminal at least tell us about the rendering issues.
VSCode (xterm.js) is one of the worst, but there's a large long tail of slow terminals out there.
Re: Claude Code is being dumbed down?
#425Hey, 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…
> this resulted in an experience that most users preferred I just find that very hard to believe. Does anyone actually do anything with the output now? Or are they just crossing their fingers and hoping for the best?
Re: Claude Code is being dumbed down?
#426Hey, 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…
I can’t count how many times I benefitted from seeing the files Claude was reading, to understand how I could interrupt and give it a little more context… saving thousands of tokens and sparing the context window. I must be in the minority of users who preferred seeing the actual files. I love claude code, but some of the recent updates seem like they’re making it harder for me to see what’s happening.. I agree with…
shhh don't say that, they will never fix it if means you use less tokens.
Re: Claude Code is being dumbed down?
#427Earlier quoted context omitted.
This is an insanely good response. History, backstory, we screwed up, what we're doing to fix it. Keep up the great work!
it reads like AI generated or at least AI assisted... those -- don't fool me!
Re: Claude Code is being dumbed down?
#428Claude's brand is sliding dangerously close to "the Microsoft of AI." DEVELOPERS, DEVELOPERS, DEVELOPERS, DEVELOPERS I write mainly out of the hope that some Anthropic employees read this: you need an internal crusade to fight these impulses. Take the high road in the short-term and you may avoid being disrupted in the long-term. It's a culture issue. Probably your strongest tool is specifically educating people abou…
Huh? Why wouldn’t developers (who probably have stock options in Claude) try to prevent becoming 'the Microsoft of AI'? That's probably what they are actively trying to do.
Some greatest hits:
- CoreAudio, Mac OS memory management, kernel in general, and many other decisions
- Google's internal dev tooling, Go, and Chrome (at least, in its day)
- C#, .NET, and Typescript (even Microsoft does good work)
One of the hallmarks of heroic engineering work is that everyone takes it for granted afterward. Open source browsers that work, audio that just works, successors to C/C++ with actual support and adoption, operating systems that respond gracefully under load, etc. ... none of these things were guaranteed, or directly aligned with short-term financial incentives. Now, we just assume they're a requirement.
Part of the "sensibility" I'm talking about is seeking to build things that are so boring and reliable that nobody notices them anymore.
Re: Claude Code is being dumbed down?
#429Earlier quoted context omitted.
I can’t count how many times I benefitted from seeing the files Claude was reading, to understand how I could interrupt and give it a little more context… saving thousands of tokens and sparing the context window. I must be in the minority of users who preferred seeing the actual files. I love claude code, but some of the recent updates seem like they’re making it harder for me to see what’s happening.. I agree with…
I think folks might be crossing wires a bit. To make it so you can see full file paths, we repurposed verbose mode to enable the old explicit file output, while hiding more details behind ctrl+o. In effect, we've evolved verbose mode to be multi-state, so that it lets you toggle back to the old behavior while giving you a way to see even more verbose output, while still defaulting everyone else to the condensed view.…
I actually miss being able to see all of the thinking, for example, because I could tell more quickly when the model was making a wrong assumption and intervene.
Re: Claude Code is being dumbed down?
#430Hey, 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…
Can we please move the "Extended Thinking" icon back to the left side of claude desktop, near the research and web search icons? What used to be one click is now three.