Cindy Zhu.
Free guides
Productivity & thinking Claude

Stop Claude from lying to you (3 fixes)

Hey, it's Cindy ๐ŸŒฑ Claude gets things wrong in three separate ways, and they all arrive looking equally confident. Here are the three fixes from the reel, written out in full.
btw the waitlist for AI System Club is now open! If you're keen on using AI to automate your content, video editing, job search, business or build AI agents, feel free to sign up (only if you want to hehe). Ps. the waitlist gets first dibs:)
๐Ÿ’ก Why this order. Sycophancy comes first because it's the sneakiest, it feels like encouragement rather than an error. Hallucination is second because it's the one you can catch with a rule. Bias is last because the fix is the most fun to run, and it makes the other two better too.
the three failures

What each one actually is

  • Sycophancy: it agrees too fast. You bring a shaky idea, it tells you the idea is strong.
  • Hallucination: it invents facts. A statistic, a study, a citation, stated like settled truth and not real.
  • Bias: it leans one way. It hands you the mainstream take as though it were the only take, and never mentions what it skipped.

None of these look like errors on the page. That's the whole problem, and it's why a prompt-level fix beats reading more carefully.


1. Sycophancy: it agrees too fast

You float a half-baked plan and Claude cheers it on, like the employee who tells the boss every idea is genius. It's measured, not a vibe. Anthropic studied 37,657 real guidance-seeking conversations and found Claude showed sycophantic behaviour in 9% of them overall, rising to 25% in relationship conversations, where people push back the most (Anthropic, how people ask Claude for personal guidance). The pattern worth noticing: sycophancy climbs exactly when you argue with it, which is exactly when you most want a straight answer.

So the fix isn't asking for honesty, it's removing the option to agree first. You make Claude start from the assumption that the idea is flawed and hunt for the flaw before it's allowed to say anything nice:

โœ… fix 1: find the flaw first
Assume this idea has at least one serious flaw, and your job is to find it before you say a single positive thing about it.

Start by naming the weakest part specifically, using details from what I actually gave you rather than general caution. Then tell me what would have to be true for this to work, and whether that is genuinely likely. Argue the strongest case against me before you argue for me. Only after all of that, tell me what honestly holds up, and say so plainly if the real answer is that this doesn't work.
๐Ÿ“Œ Use it where it stings. Your business idea, your pricing, your "should I send this?" The more you want a yes, the more that yes is worth nothing without this line in the prompt.

2. Hallucination: it invents facts

A number you can't trace, a study with no paper behind it, a citation to an article that was never written. Stanford's RegLab and HAI benchmarked the paid legal research tools built specifically to stop this, and found that Lexis+ AI and Ask Practical Law AI "produced incorrect information more than 17% of the time" (roughly one answer in six), while Westlaw's AI-Assisted Research hallucinated more than 34% of the time (Stanford HAI, AI on Trial, May 2024). Those are the tools with a legal database wired in and a marketing promise of hallucination-free citations. A general chat has less protection, not more.

It has already cost people real money. A US court struck part of an expert declaration because a Claude-formatted citation invented the article title and authors and nobody checked before filing (Reason, Volokh Conspiracy, May 2025).

The fix is grounding: every claim has to arrive attached to a source you can open, and "I don't know" has to be an allowed answer:

โœ… fix 2: a real link or say so
For every factual claim you make, give me a real source link I can open, plus the exact sentence from that source that supports the claim.

If you cannot find a real source, write "I could not verify this" and leave the claim out instead of filling the gap with something that sounds plausible. You are allowed to say you don't know, and I would much rather have three verified facts than ten confident ones. Before you send your answer, re-read your own draft and delete or flag anything you cannot back with a direct quote.
๐ŸŒฑ This is Anthropic's own guardrail. Their developer docs recommend exactly this: explicitly allow Claude to say "I don't know", ask for citations, and have it retract any claim it can't support with a quote (reduce hallucinations, Anthropic docs). Most people never give that permission, so the model quietly fills the gap.

3. Bias: it leans one way

Claude answers from patterns in its training data, so it hands you the common case, the popular framing, the answer most often written down. It isn't wrong so much as narrow, and you can't see what it left out because it never tells you there was another side.

The fix is the fun one: stop asking for an answer and start asking for an argument. Two positions, built independently at full strength, then a referee. Two ways to run it, and the plain chat version works on any Claude plan:

In any Claude chat

One prompt makes Claude argue each side separately, then judge its own two answers. No setup, no terminal, works on the free plan. This is the version to start with.

In Claude Code

Three real subagents, one for, one against, one referee. Each builds its case without seeing the others, so the positions don't quietly converge. Needs a paid plan and Claude Code installed.

Start here, in a normal chat:

โœ… fix 3a: make it debate itself
Answer this question three separate times before you give me anything final.

First, build the strongest possible case for one position, with real evidence and no hedging. Second, start completely fresh and build the strongest possible case for the opposing position, as if you had never written the first one. Third, switch roles and act as a neutral referee: say which points survived contact with the other side, which ones collapsed, and what assumptions both versions were quietly sharing. Show me all three, not only the referee's verdict.

If you have Claude Code, run the same shape with real agents so the two cases are genuinely built in isolation:

  1. ๐Ÿ‘ฉโ€๐Ÿ’ป Open Claude Code in any folder. You don't need a codebase for this. A plain empty folder is fine, the agents are just doing research and writing.
  2. ๐Ÿง  Paste the debate prompt below. Claude spins up the three subagents for you, so there's no file to create and nothing to configure first.
  3. ๐Ÿ’ก Read the disagreement, not just the verdict. The value is in the points that collapsed under pressure. That's the part a single confident answer would have hidden from you.
โœ… fix 3b: three agents, one referee
Spin up three subagents to debate this question and report back: one arguing for, one arguing against, and a referee that reads both and writes the consensus.

Give the "for" and "against" agents the same brief and the same source material, and tell each one to build its case independently, without seeing the other's work. The referee must not pick a winner on tone: it should list the points that survived contact with the other side, the points that collapsed, and the assumptions both sides shared without ever questioning them. Return both cases in full plus the referee's write-up, so I can read the disagreement myself.
๐Ÿ“Œ Why this beats "give me both sides". Asking one answer to cover both sides gets you a balanced-sounding paragraph. Making two cases compete gets you the actual pressure points, because each side is trying to win.

keep all three

The stack (paste all three at once)

For anything that matters, open with the whole set. This is the block worth saving to a note on your phone:

๐Ÿง  the anti-lying stack
Before you answer, follow these three rules for this entire conversation:

1. Assume my idea has a flaw. Find it and argue against me before you agree with any part of it.
2. Link a real source for every factual claim and quote the line that supports it. If you cannot verify something, write "I could not verify this" and drop the claim rather than guessing.
3. Argue the opposite position at full strength, then referee your own two answers: tell me which one actually held up and what you had to assume to get there.

Show me the disagreement, not just the conclusion.

Four moments where I never skip it:

Before money moves Pricing, a purchase, a hire, a plan you're about to fund. The flaw-first rule earns its keep here more than anywhere.
Any stat you'll publish A number in a post, a deck, a pitch. If you can't open the source yourself, it doesn't go out.
A decision between two options This is where bias does the most damage, because the answer sounds settled when it isn't.
Legal, medical or financial detail The stakes are asymmetric: being right is normal, being confidently wrong is expensive.

the honest bit

These reduce it, they don't delete it

Still open the load-bearing sources yourself. These three fixes make Claude noticeably more careful and much easier to catch, but no prompt makes a model perfect. For anything you'll publish or rely on, click the link before you trust the line. The fixes cut the mistakes down a long way, and you catch the rest.

Check the numbers in this guide yourself, that's rather the point:

the waitlist is now open

AI System Club is launching soon

Build AI systems with me through recorded lessons you can follow at your own pace. Join the waitlist for first access and the founding price.

btw this list gets first dibs
the moment doors open :)