You ask ChatGPT a direct question and it answers with "it depends." You ask which option is better and it lists the pros and cons of both, then declines to pick. You ask for a recommendation and get "the right choice varies based on your needs." You wanted an answer. You got a hedge.
This got noticeably worse after the GPT-5 update tuned the model toward caution and accuracy. The hedging is a default, not a hard limit, and you can switch it off with a few lines in your prompt. Here is why it happens and exactly what to write.
Why ChatGPT hedges
Three forces push the model toward the fence.
It was tuned to avoid being confidently wrong. After waves of criticism about hallucinations, the GPT-5 family was optimized to sound careful. "It depends" is the safest possible answer because it is never technically wrong. The model reaches for it when it is unsure how much certainty you want.
It cannot read your stakes. When you ask "which database should I use," the model does not know if you are a beginner who needs a confident nudge or an architect who wants the tradeoffs. Faced with that ambiguity, it hedges to cover both, which serves neither.
It mirrors your framing. If your question is open-ended ("what are the pros and cons of X"), you asked for a both-sides answer, so you get one. The model is matching the shape of your prompt.
The fix: tell it to commit
The single most effective instruction is to demand a pick and a reason. Add this to your prompt:
Give me a single recommendation, not a list of options. Pick the one you would choose and explain why in two sentences. If it genuinely depends on something, state the one factor that decides it and then assume the most common case and answer for that.
That last clause is the important part. "It depends" is often true, so banning it outright produces worse answers. Instead, force the model to name the deciding factor and then commit to the likely case anyway.
More lines that defeat hedging
When you want a verdict, not a survey:
Answer as if you had to bet money on it. What is your actual call?
When it keeps both-sidesing:
Do not give me both sides. I have read both sides. Tell me which one you would pick and why.
When you want confidence calibrated, not removed:
Give your best answer directly. If you are uncertain, put a one-line confidence note at the end, but lead with the answer, not the caveat.
When the hedge is buried in qualifiers:
No "it is important to note", no "however it depends", no "there is no one-size-fits-all". Just the recommendation.
Give it the context it is missing
Half of hedging is the model not knowing your situation. The fix is to supply the stakes up front so it does not have to guess.
I am a [solo founder / senior engineer / complete beginner]. My priority is [speed / cost / reliability]. Given that, which option should I choose?
Once the model knows who you are and what you optimize for, the reason to hedge disappears. It can commit because you removed the ambiguity that made committing risky.
When "it depends" is the honest answer
Sometimes the question genuinely has no single answer without more information, and a good response should say so. The goal is not to bully the model into false confidence. It is to stop it hedging out of habit on questions that do have a best answer for your case. The "name the deciding factor, then assume the common case" instruction threads that needle: you get a real answer plus the one condition that would change it.
The faster way to tell
If you are fighting hedging on every prompt, the prompt is usually missing the two things that cause it: your stakes and an explicit instruction to commit. Paste the prompt into FixMyPrompt and the QA flags exactly that, a missing audience or priority, an open-ended framing that invites both-sidesing, no instruction to pick. The rewrite adds them. Three free checks a day, no signup. If the rewrite gets you a straight answer, the prompt was the problem, not the model.