alt Hacker NewsMy 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.
Replies
graeme • yesterday at 6:23 PM
Previously you could see which files Claude was reading. If it got the totally wrong context you could interrupt and redirect it.
Since it's just reading at that stage there's no tracked changes.
yeah that works after the fact but the issue is more about catching it mid-run - like when Claude decides to read through 50 files to answer a simple question because it misunderstood the scope. by the time you check git you've already wasted the time and tokens. the logs help you spot that divergence while it's happening, not just after