Live data from Hacker News

Claude Code is being dumbed down?

symmetrybreak.ing

701–710 of 732 posts

Re: Claude Code is being dumbed down?

#701

This isn't just a UI preference issue, it's the observability problem that every agentic system hits eventually. When you're building agents that interact with real environments (browsers, codebases, APIs), the single hardest thing to get right isn't the model's reasoning. It's giving the operator enough visibility into what the agent is actually doing without drowning them in noise. There's a narrow band between "Re…

this isn't just an empty comment -- it's the same llm slop infesting every part of your existence.

Re: Claude Code is being dumbed down?

#702

Earlier quoted context omitted.

There are so many config options. Most I still need to truly deeply understand. But this one isn't? I'd call myself a professional. I use with tons of files across a wide range of projects and types of work. To me file paths were an important aspect of understanding context of the work and of the context CC was gaining. Now? It feels like running on a foggy street, never sure when the corner will come and I'll hit a…

You want verbose mode for this -- we evolved it to do exactly what you're asking for: verbose file reads, without seeing thinking traces, hook output, or (after tomorrow's release) full subagent output. More details here: https://news.ycombinator.com/item?id=46982177

Sorry to rain on your parade. I wanted the original verbose mode for those moments I needed a truly verbose output. And I wanted to know, at a minimal glance, what files are being read and put into context in nearly any other situation.

I exactly do not need a "verbose" mode, that lost all value to me as a replacement for something it still is no good at replacing.

You actually argue, that I do not loose anything, when in fact your product just got made worse in two significant areas. And you keep arguing, that shooting the product into one foot is solved by shooting the other foot. Sorry. Not working for me.

Will be evaluating your competition. Was on the cusp of upgrading max to the higher tier. Now? No chance of that happening.

Re: Claude Code is being dumbed down?

#703

https://github.com/anthropics/claude-code/issues/8477 https://github.com/anthropics/claude-code/issues/15263 https://github.com/anthropics/claude-code/issues/9099 https://github.com/anthropics/claude-code/issues/8371 It's very clear that Anthropic doesn't really want to expose the secret sauce to end users. I have to patch Claude every release to bring this functionality back.

I don't suppose you could share a little on that patching process?

[deleted]

Re: Claude Code is being dumbed down?

#704
post #650

Earlier quoted context omitted.

The TLS thing at least kind of makes sense. 99.9% of sites that the typical user visits will have a correctly configured and trusted certificate and communicate over TLS, so the browsers only show an indicator when that’s not the case. I think it’s a sensible evolution given how the internet has changed.

Again with the "99.9%" argument. This is always the beginning of a path towards dumbing things down. "99% of users…, 99% of sites…, in 99% of cases…" — this is always how these things begin. Also, was the padlock really such a problem? Did it really have to be removed? If not, perhaps another easily accessible way to access this data could be invented. Like, I don't know, a menu item perhaps?

In chrome on macOS, the information is still there. It’s right where it used to be, to the left of the url. But quickly glancing at safari on Mac and phone I wasn’t able to find the information at all, which, yeah, I disagree with that decision.

Both browsers show “not secure” pretty prominently for non-TLS sites, and very loudly complain about sites with untrusted certificates, so the absence of either of those things signals a trusted cert, which is now the most common case by a very wide margin for me.

Re: Claude Code is being dumbed down?

#705

Earlier quoted context omitted.

I agree with you but I think there's a "defense in depth" angle to this. Yes, your security shouldn't depend on noticing which files Claude has read, since you'll mess up. But hiding the information means your guaranteed to never notice! It's good for the user to have signals that something might be going wrong.

There's no defense "in depth" here, it's like putting your SSH key in your public webroot and watching the logs to see if anyone's taken your key. That's your only layer of "defense" and you don't stand any chance of enforcing it. Real defense is rooted in technical measures, imperfect as they may be, but this is just defense through wishful thinking.

Obviously, don't put your SSH keys in a public webroot. But let's say you're managing a web server and have a decent security mindset. But don't you think it's better to regularly check the logs for evidence of an attack vs delete all the logs so they can't be checked?

Re: Claude Code is being dumbed down?

#706

Earlier 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.…

Have you considered keeping the old behavior available as "legacy mode"? I don't want verbose mode. I don't want to spend time configuring a mutli-state verbose mode that introduces new logging in future versions so I have to go and suppress things to get just file names. I just want to see the file names. I don't consider that verbose.

Re: Claude Code is being dumbed down?

#707

Earlier quoted context omitted.

There's one really confusing thing in Codex CLI from my perspective. How do I make it run unsandboxed but still ask me for approvals? I'm fine with it running bare on my machine but I like to approve first before it runs commands. But I only see how I can configure to have both or none. What am I missing?

--help explains this, -s for sandbox and -a for approvals

Thanks! That helped. Really strange though, that the slash commands inside the CLI do not allow for such a detailed configuration. It allows for the sandbox and approvals options but there's only "default" and "just allow everything" while the CLI flags or the config.toml allows for more nuanced options.

Re: Claude Code is being dumbed down?

#708

Earlier 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.

As someone who's business is run through a terminal, not everyone uses ghostty, even though they should. Remember, that they don't have a windows version.

Not everyone has the massive GPUs required by run Ghostty.

Re: Claude Code is being dumbed down?

#709

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…

What is the best way to get you guys feedback? There's a few things I tell Claude Code to do every project that I feel like Claude should just do by default, the biggest one is instead of using Grep so much, I have ripgrep installed, it makes searching for text inside the current folder so much easier and it is insanely faster. Claude seems to work way faster when it uses ripgrep, I don't know if its because MCP has…

add that to your claude.md

Re: Claude Code is being dumbed down?

#710

Earlier quoted context omitted.

Yeah, in hindsight, we probably should have renamed it.

You can call it “output granularity” and allow Java logger style configuration, e.g. allowing certain operations to be very verbose while others being simply aggregated

If we're going there, we need to make the logging dynamically configurable with Log4J-style JNDI and LDAP. It's entirely secure as history has shown - and no matter what, it'll still be more secure than installing OpenClaw!

(Kidding aside, logging complexity is a slippery slope, and I think it's important, perhaps even at a societal level, for an organization like Anthropic to default to a posture that allows people to feel they have visibility into where their agentic workflows are getting their context from. To the extent that "___ puts you in control" becomes important as rogue agentic behavior is increasingly publicized, it's in keeping with, and arguably critical to, Claude's brand messaging.)

Post reply on HN