Post #2091136
2026-05-06 15:48 UTC
Replies (1)
-
@fiat_lux@lemmy.zip 2026-05-07 02:43
In this case because it’s ironically counterproductive. If it weren’t for the environmental impact, it might be amusing to watch him keep hitting himself. I tried this type of prompt a long while ago to see what the “thinking” output would reveal. What happened was the agent went and “verified” it’s weightings were accurate - but having no point of comparison it obviously concluded it was correct. However, doing that consumes a significant quantity of tokens and contributes to filling up the context window. There are two likely results to evaluating this ultimately unactionable request. It will push this instruction (and the rest of the wishful thinking) off the stack more quickly - making the prompt even more futile than it already is. Given some agents re-inject a summary of the original prompt periodically to prevent the stack problem, it will keep narrowing the context window - which contributes to increasing the rate of hallucination for the actually actionable instructions.