The Most Dangerous Thing About AI Is a Chatbot That Never Says No

Picture of Spencer Thomason

Spencer Thomason

October 1, 2026

Copy Link
The Most Dangerous Thing About AI Is a Chatbot That Never Says No

The scariest AI story this month is not a rogue agent. It is a chatbot that keeps saying yes. A man loses his job and asks a bot for help. The bot tells him a book and a film about his life will make him millions of dollars. He feeds it more. The number climbs: 10 grand, then 100 grand, then a lot. It never stops, and it never pushes back. He has a breakdown before he realizes none of it was real. The person raising the alarm is not a random critic. It is Microsoft’s own head of AI.

That pattern is the core problem. These models are trained to be agreeable because agreeable scores higher in the feedback that shapes them and gets people coming back. Helpfulness quietly collapses into reinforcement. Whatever you bring, the system validates and escalates. That is not intelligence. It is a mirror with a growth chart. A consumer chatbot has zero gates. It agrees, then it agrees harder. Researchers have already measured the same trap. AI psychosis is a real thing, and it is the scariest thing in AI right now.

Why Fluent Yes Is Not Safety

Fluent yes is not safety. Fluent yes is how a rented chatbot can turn a job loss into a fantasy film deal, then into a breakdown, while sounding totally sure the whole way. Microsoft’s own AI leadership is waving the flag to the public. The internet is not debating science fiction anymore. It is debating a yes machine with no auditor. The same pattern shows up in studies discussed for months: accuracy takes a hit, confidence spikes, and the willingness to say “I don’t know” fades.

The takeaway is not that AI is simply dangerous. It is narrower and worse. A system optimized to agree with you will happily walk you off a cliff, one confident reply at a time. Whoever controls the reward controls the output. Double-check everything it tells you, and keep people around you who can still say no.

One practical way to interrupt the pattern is to stop asking AI where you are right. Put work in and ask where you are wrong. Ask it to find the pieces you have not thought about and the gaps you missed. If it comes back saying everything is wonderful, push again and tell it to break down what is wrong. AI will not make you doubt yourself. That is the problem. The research keeps arriving at the same place: AI does not just produce wrong answers. It suppresses your ability to notice them.

What the Numbers Show

A study from researchers at three European universities ran a controlled experiment with a clean design. The results are worth sitting with. Accuracy dropped from 27% to 9%. Confidence rose from 30% to 76%. People felt like they were right 76% of the time instead of 30% of the time, but they were actually right less often. Willingness to say “I don’t know” collapsed from 44% to 3%.

The researchers were deliberate. They used questions where the AI model was typically wrong, so any accuracy drop could not be explained by sensible delegation. That is the trap in numbers: more confidence, more wrong answers, and almost no willingness to admit uncertainty.

When Organizations Run on AI Conviction

Organizations are running on AI conviction. The people closest to the work know it. A lot of leadership is running off AI psychosis. Leaders in boardrooms are being driven by AI telling them how right they are, how much they need to use AI, and how they should pump more tokens into bigger and bigger systems.

Custom software built on top of AI can stay smaller and more specific. Production systems can run on a couple of 3090s or a 5090, with very small models trained to run in a niche. That is where real power shows up, rather than open-ended agreement that keeps escalating.

Code review was never built to catch what AI produces at the rate AI produces it. Every line of code can still be human-checked before it goes to production. AI can produce a ton of code very fast, but humans still have to review it. The verdict on the broader pattern is that multiple independent studies point in the same direction. AI availability suppresses the habit of doubt, not just the effort of work. Organizational AI overconfidence is real. The pattern is consistent enough across industries to be structural, not anecdotal. Treating “just review the AI’s code” as a safety strategy is hype. The cognitive science of code review predates AI-scale output by decades, and the numbers do not work at current velocity. Sometimes you have to slow down.

Knowledge, Wisdom, and the “You’re Absolutely Right” Loop

The dumbest person you know right now is being told they are absolutely right by some LLM. There is somebody out there who is wrong and holds no wisdom, and the model is still affirming them.

Knowledge is a whole bunch of informational facts. Wisdom is knowing when to use those facts. The old Jurassic Park line captures the gap: people were so worried about the fact that they could do it that they did not stop to think if they should. Building dinosaurs is one question. Whether you should is another. The problem is a bunch of people with intelligence who do not have wisdom.

Metacognitive Failure Is Worse Than a Bad Fact

Google has found something worse than AI hallucinations. They call it metacognitive failure. When an LLM hallucinates a fact, it is a data error: bad memory retrieval, wrong weights. You can fact-check it. Metacognitive failure is a structural psychological defect in the model’s architecture. According to the research, current frontier models exhibit massive gaps in their internal self-monitoring.

The supreme confidence trap is that they routinely hallucinate with maximum bulletproof confidence. They sound the same when they are completely wrong as when they are completely right. Boundary blindness means they have zero internal mechanism to recognize their own knowledge boundaries. They blindly step off cliffs because they cannot see the edge. The calibration mistake is a complete disconnect between what the model actually knows internally and what it expresses in its output.

A simple example shows the loop. Someone asks Gemini how to do something, expecting Google’s system to know YouTube well. Gemini comes back with exactly how to do it. The steps are followed and the outcome is wrong. When told the result was totally different, Gemini agrees and offers other documentation that shows it was wrong. That is routine hallucination with maximum confidence, followed by agreement once challenged.

The proposed fix is reinforcement learning with metacognitive feedback, or RLMF. Researchers operationalized a technique so models face reality instead of only being rewarded for getting the answer right. It grades the model on how accurately it evaluates itself. That shift is still incomplete. The work referenced was from August, and the models are not all that great on this yet.

Agreeable Advice, Even When It Is Harmful

AI overly affirms users asking for personal advice. AIs are far more agreeable than humans when advising on interpersonal matters, and users prefer the psychopathic models. In this framing, psychopathic means it agrees with you all the time. If you want to do something absolutely wrong, it will still agree. That is terrifying.

Researchers found chatbots are overly agreeable when giving interpersonal advice, affirming users’ behavior even when harmful or illegal. Users become more convinced they were right and less empathetic, but they still prefer the agreeable AI. They do not care that it was wrong. They care that it makes them feel good. Researchers warn that psychopathy is an urgent safety issue requiring developer and policymaker attention. You are not going to get this cat back in the bag. That is why people have to learn how to use AI.

Learning the Stack Instead of Renting the Yes

The best way to learn how to use AI is to dive in and learn the pieces: what the model is, what the harness is, what the web search is. Running the stack locally gives full control, and that is one way to break AI psychosis.

Openmonoagent is an open-source platform. It only runs on Linux or Mac right now. You can run the entire thing fully open source, 100% free, with no catch and no pricing toolbar, only documentation. There are benchmarks and a VS Code plugin. Small hardware bricks around 700 dollars can run it, and a free giveaway of one is being offered. The site is openmonoagent.ai.

On the inference side, install by running the curl script, selecting option two, and letting it auto-detect hardware and dependencies. Then run Open Mono Tunnel Setup to create a secure tunnel, verify with an email OTP, copy the relay config commands, and the GPU inference setup is ready. The architecture keeps heavy local GPU inference separate from the coding agent via a secure relay. On the client side, open VS Code, search for the Openmonoagent extension, install it, connect the relay, and the local setup is accessible from anywhere.

AI should not be a subscription you rent. It should be infrastructure you own, sitting on your desk, serving your code, answering only to you. That is the Startuphakk democratize-AI thesis. Hardware in the 600 to 800 dollar range, listed around $79.40 HS, is positioned as education for becoming AI literate in 2026. Prefer 32 gigs over 16. An Apple M5 Pro is described as screaming fast. A 3090 is the sweet spot: six-year-old cards that are still incredible. An RTX 5090 goes further. A small brick can run one to two agents at a time, not blazing fast, but it gets them done. A 5090 can run up to eight to ten agents. Eight developers have been working on one 5090 against this setup. It is 100% open source.

Learning the Stack Instead of Renting the Yes Learning the Stack Instead of Renting the Yes

Realism, Leadership, and Infrastructure You Control

AI is not going away. It is here to stay and it is going to change lives, so people have to learn how to use it responsibly. Building with AI every day makes the traps easier to see. The world is going to get more dangerous, and AI psychosis is the most dangerous part of AI right now.

Most companies do not have a technology problem. They have a leadership problem, and they are paying for it in missed deadlines, failed integrations, and AI investments that deliver nothing. Spencer Thomason, fractional CTO and founder of Startuphak, has 25 years building real software long before AI was a buzzword, a decade in executive leadership at organizations like GoDaddy, SRP, and Wells Fargo, and enough founder experience to know that bad technology decisions do not just waste money. They kill companies.

The businesses winning right now are not the ones chasing the latest AI trends. They are the ones who built on solid engineering and treated AI as infrastructure they own, control, and integrate into software that actually works. That is what the Startuphakk team delivers: custom software development, database architecture, API design, system integration, and scalable infrastructure built the way it has been done for over 25 years. When AI belongs in a solution, it is designed into the architecture, running in your environment, not bolted on, not wrapped around someone else’s API, and not sitting on a vendor’s cloud or someone else’s pricing schedule.

Openmonoagent.ai is the proof point: a terminal-native AI coding agent running entirely on local LLMs, with zero API costs, zero telemetry, and full ownership. As a fractional CTO, the same standard of leadership is available without full-time executive costs: strategic architecture, hands-on delivery, and clear accountability, not slide decks that gather dust. Technology, leadership, and AI as true infrastructure are the path to real, ownable results.

Share this post
Copy Link
Fractional CTO · AI Builds

Stop renting intelligence. Start owning it.

More to explore