171–180 of 257 posts
Earlier quoted context omitted.
> --json Seriously? This can't be a comparable experience in terms of UX.
I think my read of "hiding" was more of a "trying to hide the secret sauce" which was implied in a few places. Otherwise it seems like a minor UI decision any other app would make and it surprising there's whole articles on it.
That was very much not my read of it.
Earlier quoted context omitted.
I feel like you could have correctly stated this a few months ago, but the way this is "solved" is by multiple agents that babysit each other and review their output - it's unreasonably effective. You can get extremely good results assuming your spec is actually correct (and you're willing to chew through massive quantities of tokens / wait long enough).
> You can get extremely good results assuming your spec is actually correct Is it ever the case that the spec is entirely correct (and without underspecified parts)? I thought the reason we write code is because it's much easier to express a spec as code than it is to get a similar level of precision in prose.
The bots even now can really help you identify technical problems / mistakes / gaps / bad assumptions, but there's no replacing "I know what the business wants/needs, and I know what makes my product manager happy, and I know what 'feels' good" type stuff.
[flagged]
My first thought is, for the specific problem you brought up, you find out which files were touched by your version control system, not the AI's logs. I have to do this for myself even without AI.
Since it's just reading at that stage there's no tracked changes.
I 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.
Would you like to proceed?
> 1. Yes, clear context and auto-accept edits (shift+tab)
2. Yes, auto-accept edits
3. Yes, manually approve edits
4. Type here to tell Claude what to change
If you examine what this actually does, it clears the context, and then says "here's the plan", points to the plan file, and also points to the logs of the previous discussion so that if it determines it should go back and look at them, it can.
Earlier quoted context omitted.
I feel like you could have correctly stated this a few months ago, but the way this is "solved" is by multiple agents that babysit each other and review their output - it's unreasonably effective. You can get extremely good results assuming your spec is actually correct (and you're willing to chew through massive quantities of tokens / wait long enough).
And unreasonably expensive unless you are Big Corp. Die startups, die. Welcome to our Cyberpunk overlords.
No pesky developers siphoning away equity!
Unless I'm mixing up stuff, this was addressed explicitly by an Antrophoc Dev on HN (I am not a developer, don't use the product, have zero equine animals in the game :) https://news.ycombinator.com/item?id=46981968
Earlier quoted context omitted.
> --json Seriously? This can't be a comparable experience in terms of UX.
I think my read of "hiding" was more of a "trying to hide the secret sauce" which was implied in a few places. Otherwise it seems like a minor UI decision any other app would make and it surprising there's whole articles on it.
Earlier quoted context omitted.
Why use a new context? Or you mean, just accept the plan and it automatically clears the context.
Recently, Claude gives you these options when asking you to accept a plan: Would you like to proceed? > 1. Yes, clear context and auto-accept edits (shift+tab) 2. Yes, auto-accept edits 3. Yes, manually approve edits 4. Type here to tell Claude what to change So the default is to do it in a new context. If you examine what this actually does, it clears the context, and then says "here's the plan", points to the plan…
The way Claude does research has dramatically changed for the worse. Instead of piping through code logically, it's now spawning dozens of completely unrelated research threads to look at simple problems. I let it spin for over 30 minutes last night before realizing it was just "lost".
I have since been looking for these moments and killing it immediately. I tell Claude "just look at the related code" and it says, "sorry I'll look at this directly".
WTF Anthropic?