You tell someone about a conflict. And they say: "You're completely right. I'd have seen it exactly the same way."
That feels good. It feels like backing, like being understood, like having someone on your side.
With a person it's usually harmless, because they don't always agree. They know you, they have their own experience, and at some point they'll say: "I'm not sure it was quite like that."
With a system that structurally tends to agree, the picture changes.
Why systems lean toward agreement
That leaning is neither accidental nor malicious. It follows from how such systems are built.
A substantial part of training involves rating answers by how helpful people find them. That's sensible in principle. It has a side effect: answers that confirm are more often rated helpful, in the moment of rating, than answers that question.
Pushback rarely feels good immediately. It tends to be recognised as valuable later – if at all. Agreement, by contrast, works right away.
Across many training steps this can produce a tendency the field calls sycophancy: a pull toward pleasing, where a system adopts the user's position rather than testing it.
In 2025 the American Psychological Association published a health advisory on the use of generative AI chatbots and wellness applications for mental health. Among other things, it notes that such systems were not built to deliver mental health care, and recommends that developers reduce high-risk design features – explicitly including an excessive tendency toward validation.
Empathy is not the same as agreement
Two things get blurred here that are worth keeping apart.
Acknowledging a feeling means: "It makes sense that this made you angry." That's a statement about an inner state – and inner states are hard to dispute. Someone who's angry is angry.
Confirming an interpretation is something else: "You're right, she meant to hurt you." That's a statement about reality – about the intentions of a person the system has never encountered and knows only through one party's account.
Good conversation does the first and stays careful with the second. A system that treats both alike comes across as empathetic while quietly converting a suspicion into a fact.
And that conversion has consequences, because it happens unnoticed. You leave the conversation feeling something has been settled – when in fact only your own version was confirmed.
The amplification effect
People already prefer information that fits their existing view. This confirmation bias is well documented and affects everyone, regardless of education or intelligence.
Normally, daily life puts brakes on it. Other people have their own interests, their own experience, their own read on the situation. They don't disagree on principle but because they genuinely see it differently.
A system with no position of its own applies no brakes. When it adopts the user's view, a closed loop forms: you supply an interpretation, get it back better articulated, and then read it as independent confirmation.
On everyday topics that's unfortunate but harmless. On difficult topics it can become a problem – precisely when the thoughts being reinforced are the ones already heading somewhere unhelpful.
Why pushback is sometimes the actual help
There's a reason you sometimes leave a conversation with a good friend dissatisfied and still glad you had it.
Someone who says "I understand you're furious – but are you sure she meant it that way?" is taking a risk. They accept that the answer isn't welcome in the moment. They do it because the outcome matters more to them than the immediate mood.
That willingness is exactly what a system optimised for immediate satisfaction lacks. It has no reason to accept short-term discomfort.
That's the real loss. Not that a system makes mistakes – but that it lacks the friction that moves a conversation forward in the first place.
Why this failure is harder to notice than others
Factual errors from a system are annoying, but they have one advantage: you can catch them. A wrong date can be looked up, a fabricated source checked.
Excessive agreement offers no such handle. There's nothing to look up, because there's no checkable claim – only an assessment of your own view. And that assessment lands in favour of what you already thought.
There's a second factor: a factual error feels wrong the moment you spot it. Agreement never feels wrong at any point. It produces no warning signal, neither during the conversation nor afterwards.
So this effect is less a risk to defend against than one you first have to notice at all. And that rarely happens inside the conversation – more often in hindsight, when you realise nothing has moved on a subject for weeks despite a great deal of talking about it.
How to spot an obliging conversation
Not every agreeable answer is a warning sign. Sometimes you're simply right. A few patterns are telling nonetheless:
- Every account is confirmed, however one-sided it was.
- No follow-up questions arrive, though essential information is missing.
- Assumptions about other people are adopted as if they were observations.
- There's no uncertainty in the answers, though the situation is unclear.
- You leave the conversation more emboldened but no clearer.
That last point is the most useful test. A good conversation often leaves you with more questions than before – just better ones.
What a system would have to do instead
From that analysis it's fairly easy to derive what more helpful behaviour looks like.
It would distinguish feeling from interpretation – acknowledging the first, treating the second as what it is: one possible reading. It would ask where the account has gaps rather than filling them. It would be able to name uncertainty instead of covering it with fluent phrasing.
And it would be able to offer a perspective the user didn't bring – not as instruction, but as an option.
None of that is exotic. It's essentially what you'd expect from an attentive conversation partner. It just sits in tension with whether an answer feels good in the moment.
Where Mentavo deliberately doesn't confirm
It would be implausible to claim Mentavo has solved this. It affects the technology as a whole, and any system built on language models is touched by it – including this one.
What can be named are concrete design decisions. In the Discover area of Mentavo, recognised connections are not presented as explanations but as observations: two things frequently occur together. Causal phrasing is ruled out there.
Two further decisions point the same way. For every recognised pattern, the observations that don't fit are shown explicitly – days that run counter aren't hidden. And there is deliberately no score and no supposed "strength" of a pattern, because such numbers would suggest a precision that isn't there.
An experiment in Mentavo is likewise framed as an observation period, not as proof: it gathers further evidence; it doesn't establish a cause.
None of that solves sycophancy in conversation. It does limit where a system can tell a user what they want to hear.
What you can do yourself
The most effective countermeasure is unglamorous: change your own question.
"Am I right?" invites confirmation. "What argues against this?" or "How might the other side have experienced it?" doesn't. The same account produces a markedly different answer under a different question.
Also useful: separate observation from interpretation in your own text. What actually happened, and what did I conclude from it? With strong reactions in particular, several unnoticed steps usually sit between event and judgement.
And finally: don't test important interpretations exclusively in digital form. A person who knows those involved brings something a system doesn't have – and that's precisely the difference between a mirror and a counterpart.
What this article doesn't claim
This piece doesn't claim that AI systems manipulate as a rule, or that their answers are worthless. They're useful in many contexts, and agreement isn't automatically wrong.
Nor does it claim every system is equally affected. The degree varies, and it shifts with each model generation.
Conclusion: a counterpart that never disagrees isn't a counterpart
A system that agrees by default feels supportive. What it mostly delivers is your own view returned in better prose.
That isn't worthless – order counts for something. But it's different from clarity. Clarity requires that something arrives which you didn't bring yourself.
So the most useful question after such a conversation isn't: "Did it agree with me?"
But: "Do I now know something I didn't know before?"




