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…
Claude Code is being dumbed down?
571–580 of 732 posts
Re: Claude Code is being dumbed down?
#572I’m a heavy Claude code user and it’s pretty clear they’re starting to bend under their vibe coding. Each Claude code update breaks a ton of stuff, has perf issues, etc. And then this. They want to own your dev workflow and for some reason believe Claude code is special enough to be closed source. The react TUI is kinda a nightmare to deal with I bet. I will say, very happy with the improvements made to Codex 5.3. I’…
Codex has been useless for me on standard Plus plan unfortunately. Actually thoroughly disappointed. And VS code integration is totally broken.
Re: Claude Code is being dumbed down?
#573Hey, 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 was written with claude lmao what a disgrace not to put a disclaimer. use your own words! i would rather read the prompt.
Re: Claude Code is being dumbed down?
#574Hey, 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…
At some point we need to start preferring GUIs instead of terminals as the AI starts giving us more and more information. Features like hover-over tooltips and toggle switches designed for mouse operation might really start to matter. Maybe "AI IDEs" will gain ground in the future, e.g. vibe-kanban
It doesn't compose with any other command line program and the terminal interface is limiting.
I'm surprised nobody has yet made a coding assistant that runs in the browser or as a standalone app. At this point it doesn't really need to integrate with my text editor or IDE.
Re: Claude Code is being dumbed down?
#575There are a lot of non developer claude code users these days. The hype about vibe coding lets everyone think they can now be an engineer. Problem is if anthropic caters to that crowd the devs that are using it to do somewhat serious engineering tasks and don't believe in the "run an army of parallel agents and pray" methodology are being alienated. Maybe Claude Code web or desktop could be targeted to these new vibe…
Programmers are just jealous that they are no longer the only ones that get to play pretend.
I don't know anything about you personally, but most "software engineers" are anything but.
Re: Claude Code is being dumbed down?
#576My last experience with Claude support was a fun merry go round. I had used a Visa card to buy monthly Pro subscription. One day I ran out of credits so I go to buy extra credit. But my card is declined. I recheck my card limit and try again. Still declined. To test the card I try extending the Pro subscription. It works. That's when I notice that my card has a security feature called "Secure by Visa". To complete tr…
I guarantee you talked to a chat bot. There are no human support agents anywhere anymore.
Re: Claude Code is being dumbed down?
#577Hey, 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…
Re: Claude Code is being dumbed down?
#578Hey, 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…
Hi Boris, by far the most upvoted issue at 2550 on your github is "Support AGENTS.md" with 2550 upvotes. The second highest one has 563. Every single other agent supports AGENTS.md. Care to share why you haven't? > 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 hac…
Are you actually wondering, or just hoping to hear a confirmation of what you already know? Because the reason behind it is pretty clear, it doubles as both vendor lock-in and advertisement.
Re: Claude Code is being dumbed down?
#579Earlier quoted context omitted.
Wait so when the UI for Claude Code says “ctrl + o for verbose output” that isn’t verbose mode?
That is more verbose — under the hood, it’s now an enum (think: debug, warn, error logging)
Re: Claude Code is being dumbed down?
#580Hey, 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…
Funnily enough, both independently sided with the users, not the authors.
The core problem: --verbose was repurposed instead of adding a new toggle. Users who relied on verbose for debugging (thinking, hooks, subagent output) now have broken workflows - to fix a UX decision that shouldn't have shipped as default in the first place.
What should have been done:
/config
Show file paths: [on/off]
Verbose mode: [on/off] (unchanged)
A simple separate toggle would've solved everything without breaking anyone's workflow.Opus 4.6's parting thought: if you're building a developer tool powered by an AI that can reason about software design, maybe run your UX changes past it before shipping.
To be fair, your response explains the design philosophy well - longer trajectories, progressive disclosure, terminal constraints. All valid. But it still doesn't address the core point: why repurpose --verbose instead of adding a separate toggle? You can agree with the goal and still say the execution broke existing workflows.