Original Reddit post

So after a session, Opus 5 wil come back to you with a list of things it thinks are wrong/subotimal in the codebase. It will say, oh a found some bugs here and this function is behaving bad. It always does this like 70% of the time, which leads to session being long. Have you ever gone and checked if these recommendations hold up? I think this sort of doubt is a result of heavy RL training, like the “aha” moment mentioned in the DeepSeek V3 paper. So is this Opus self-doubt something useful and to be looked at, or should we just ignore it. Before somebody comes back to me and tells me to go check, no I have no clue what’s going on in my codebase, that’s why I am asking. submitted by /u/BankruptingBanks

Originally posted by u/BankruptingBanks on r/ClaudeCode