Literally the opposite though, as being able to see what it reads allows you to tell it to ignore certain files when you see it read the wrong one, and adjust the claude.md file to ensure that it does not read incorrect files given a specific input.

True vibe coders don't care about this.

Jokes about vibe-coded CLI aside, I think that's the issue for me, the defaults are being tailored to vibe coders. (and the general weirdness of trying to fix it with verbose mode)

I like that people who were afraid of CLIs perhaps are now warming up to them through tools like Claude Code but I don't think it means the interfaces should be simplified and dumbed down for them as the primary audience.

Sure you can press CTRL+O, but that's not realtime and you have to toggle between that and your current real time activity. Plus it's often laggy as hell.

Yeah, these all sound like complete non issues if you're actually... keeping your codebase clean and talking through design with Claude instead of just having it go wild.

I'm using it for converting all of the userspace bcachefs code to Rust right now, and it's going incredibly smoothly. The trick is just to think of it like a junior engineer - a smart, fast junior engineer, but lacking in experience and big picture thinking.

But if you were vibe coding and YOLOing before Claude, all those bad habits are catching up with you suuuuuuuuuuuper hard right now :)

I hate to say it, but "vibe-coders" are just "coders" now.

It's a huge shift, but we need to start thinking of AI-tools as developer tools, just like a formatter, linter, or IDE would be.

The right move is diversity. Just like diversity of editors/IDEs. We need good open source claude code alternatives.