Anthropic tries to hide Claude's AI actions. Devs hate it

Post by [deleted] » Mon, Feb 16, 2026, 2:54 PM UTC

pzs wrote: post #65

rco8786 wrote: post #22

Earlier quoted context omitted.

> it's about catching when it goes off the rails before it makes a mess The latest "meta" in AI programming appears to be agent teams (or swarms or clusters or whatever) that are designed to run for long periods of time autonomously. Through that lens, these changes make more sense. They're not designing UX for a human sitting there watching the agent work. They're designing for horizontally scaling agents that work…

Related question: how do we resolve the problem that we sign a blank cheque for the autonomous agents to use however many tokens they deem necessary to respond to your request? The analogy from team management: you don't just ask someone in your team to look into something only to realize three weeks later (in the absence of any updates) that they got nowhere with a problem that you expected to take less than a day t…

Post by dhagz » Mon, Feb 16, 2026, 2:57 PM UTC

embedding-shape wrote: post #23

xg15 wrote: post #8

> Cherny responded to the feedback by making changes. "We have repurposed the existing verbose mode setting for this," he said, so that it "shows file paths for read/searches. Does not show full thinking, hook output, or subagent output (coming in tomorrow's release)." How to comply with a demand to show more information by showing less information.

Words have lost all meaning. "Verbose" no longer means "containing more words than necessary" but instead "Bit more than usual". "Fast" no longer mean "characterized by quick motion, operation, or effect" but instead depends on the company, some of them use slightly different way, but same "speed", but it's called "fast mode". It's just a whole new world where words suddenly mean something completely different, and y…

Post by the_harpia_io » Mon, Feb 16, 2026, 3:02 PM UTC

rco8786 wrote: post #22

the_harpia_io wrote: post #13

[flagged]

> it's about catching when it goes off the rails before it makes a mess The latest "meta" in AI programming appears to be agent teams (or swarms or clusters or whatever) that are designed to run for long periods of time autonomously. Through that lens, these changes make more sense. They're not designing UX for a human sitting there watching the agent work. They're designing for horizontally scaling agents that work…

Post by the_harpia_io » Mon, Feb 16, 2026, 3:03 PM UTC

charliea0 wrote: post #60

the_harpia_io wrote: post #13

[flagged]

I assume it's to make it harder for competitors to train on Claude's Chain-of-Thought.

Post by the_harpia_io » Mon, Feb 16, 2026, 3:06 PM UTC

xnorswap wrote: post #28

the_harpia_io wrote: post #13

[flagged]

Yes, this is why I generally still use "ask for permission" prompts. As tedious as it is a lot of the time ( And I wish there was an in-between "allow this session" not just allow once or "allow all" ), it's invaluable to catch when the model has tried to fix the problem in entirely the wrong project. Working on a monolithic code-base with several hundred library projects, it's essential that it doesn't start digging…