Comment by rjh29

A few things imo, 1) not prompting precisely enough (narrowing scope) means your agent will scan your entire code-base and sometimes get stuck looking at things repeatedly. 2) not checking the output is usually fine but sometimes it produces junk because it doesn't understand, and you cannot prompt your way out of it without reading the code and figuring out the problem. If you leave it on auto it will burn tokens.

Plenty of low level things can trip agents up, too. I just had one inexplicably refuse to read an error about a function needing a bool return value - trying about 10 variations of the same thing before I interrupted it. Skills probably cause issues too, it loves to for example read the source code of libraries I'm using if I give it permission. That's a rabbit hole.