| ▲ | cyanydeez an hour ago | |
On llamacpp and other engines, you can inject a think budget which truncates at specified token count. You can also specify a message at the limit. You can set this in the header, so a dynamic engineering harness could relax/tighten. Combine with a decision model and some robust messages like, "run a test to rule out items" and all that would reduce. 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. | ||