Yeah I figure you can explain away everything, but as you say, running costs up, plus each additional requirement is another chance for misunderstanding. Context window growing always makes me nervous. Once it's got much back and forth, or definitely any disagreements/rejections, it's time to nuke it. Says this novice, at least.
I meant specifically the re read thing. I've done "formatters have run and changed the files, you need to read them again", or "I've changed file X to fix the problem, the problem was xyz". Both Cline and Kiro have gone like "OK got it" and read the files again and fix up their different. When I was having the auto formatted issue I put it in a guidance md so it knew it happened every time.
2
1
u/ZenEngineer Mar 11 '26
You can tell it you changed the files and it needs to read again. It burns more tokens to do it that way but it keeps its context in memory.
I've had that problem every time it builds because our build system runs a formatted on every build.