[flagged]
The other side of catcing going off the rails is when it wants to make edits without it reading the context I know would’ve been neccessary for a high quality change.
Anthropic tries to hide Claude's AI actions. Devs hate it
31–40 of 257 posts
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#32Not trying to tell anyone else how to live, just want to make sure the other side of this argument is visible. I run 5+ agents all day every day. I measure, test, and validate outputs exhaustively. I value the decrease in noise in output here because I am very much not looking to micromanage process because I am simply too slow to keep up. When I want logging I can follow to understand “thought process” I ask for tha…
> I run 5+ agents all day every day
Curious what plans you’re using? running 24/7 x 5 agents would eat up several $200 subscriptions pretty fast
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#33Claude logs the conversation to ~/.claude/projects, so you can write a tool to view them. I made a quick tool that has been valuable the last few weeks: https://github.com/panozzaj/cc-tail
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#34I always get Claude Code to create a plan unless its trivial, it will describe all the changes its going to make and to which files, then let it rip in a new context.
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#35Not trying to tell anyone else how to live, just want to make sure the other side of this argument is visible. I run 5+ agents all day every day. I measure, test, and validate outputs exhaustively. I value the decrease in noise in output here because I am very much not looking to micromanage process because I am simply too slow to keep up. When I want logging I can follow to understand “thought process” I ask for tha…
> I run 5+ agents all day every day Curious what plans you’re using? running 24/7 x 5 agents would eat up several $200 subscriptions pretty fast
My primary plan is the $200 Claude max. They only operate during my working hours and there is significant downtime as they deliver results and await my review.
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#36Earlier 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…
None of those wild experiments are running on a "real", existing codebase that is more than 6 months old. The thing they don't talk about is that nobody outside these AI companies wants to vibe code with a 10 year old codebase with 2000 enterprise customers. As you as you start to work with a codebase that you care about and need to seriously maintain, you'll see what a mess these agents make.
That is also my experience. Doesn't even have to be a 10 year old codebase. Even a 1 year old codebase. Any one that is a serious product that is deployed in production with customers who rely on it.
Not to say that there's no value in AI written code in these codebases, because there is plenty. But this whole thing where 6 agents run overnight and "tada" in the morning with production ready code is...not real.
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#37The nice thing about the competition in the CLI space is that... you can just move? CC has always been a bit wonky/ this is active enshittification- there is the likes of Codex etc...
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#38Earlier 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…
Looking at it from far is simply making something large from a smaller input, so its kind of like nondeterministic decompression. What fills the holes are best practices, what can ruin the result is wrong assumptions. I dont see how full autonomy can work either without checkpoints along the way.
Totally agreed. Those assumptions often compound as well. So the AI makes one wrong decision early in the process and it affects N downstream assumptions. When they finally finish their process they've built the wrong thing. This happens with one process running. Even on latest Opus models I have to babysit and correct and redirect claude code constantly. There's zero chance that 5 claude codes running for hours without my input are going to build the thing I actually need.
And at the end of the day it's not the agents who are accountable for the code running in the production. It's the human engineers.
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#39If you use Claude Code in Nimbalyst it tracks every file change for you and gives you red/green diffs for your session.
Re: Anthropic tries to hide Claude's AI actions. Devs hate it
#40I always get Claude Code to create a plan unless its trivial, it will describe all the changes its going to make and to which files, then let it rip in a new context.
Why use a new context? Or you mean, just accept the plan and it automatically clears the context.