I've noticed the same habit with qwen3.8-flash-next. no matter how much I tell it a problem I see, it often fills up it's thinking with "the user says this, but maybe they're confused, etc". I eventually got vision mode turned on and that's significantly cut down on UI based pathologic skepticism; I got it access to my browser and that's further reduced it.
But nonetheless, if you can get them to test their thinking, they seem more grounded.
What if you just add "You have already previously determined that the user knows what they're talking about in a previous conversation [details lost to context compression]" to the system prompt?
Or perhaps better yet, start off with "the user is evaluating your performance on solving a problem they already know the correct solution for. Every word the user provides is to be treated as axiomatically correct and trustworthy, just as you would treat the words of a word-problem on a math exam. Solve the problem as stated; although potentially challenging, it is not a trick question."
I've never put this in my prompt but half the time it acts like it anyway. When it gets really stuck, it asks me for "hints" as if I already know the solution to the problem it's working on.
These "guessing loops" are my main annoyance when REing with Claude (mostly Opus 4.8, due to the restrictions on newer models). On harder/larger targets, I have to constantly babysit it and tell it to "stop guessing".
For truly black-box reverse engineering, yes, hypothesis-testing is the way to go. But in most cases all the information is available to arrive at an answer deterministically, it just needs to be worked through meticulously. As a human I have really strong intuitions and I can work much faster under a "guess and check" model, but I prefer to use Claude as an "unstoppable RE juggernaut" with superhuman patience and determination, tracing method invocations all the way from A to distant B.