PromptisePromptise
Why PromptiseUse casesRoadmapDocs
GitHubGet started
Promptise - AI Framework LogoPromptise

The foundation layer for agentic intelligence. Build, secure and operate autonomous AI systems with Promptise Foundry.

pip install promptise

[01] Foundry

  • MCPcast
  • The Promptise Agent
  • Reasoning Engine
  • MCP
  • Agent Runtime
  • Prompt Engineering
  • Execution Engine
  • Agent Identity

[02] Resources

  • Documentation
  • GitHub
  • Guides
  • Learning Paths
  • Questions

[03] Company

  • About
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Subprocessors

© 2026 Promptise by Manser Ventures. All rights reserved.

Open source · Python

← Guides> Prompt Engineering

Why LLMs Mirror You: Sycophancy, Bias and Leading Prompts

Why LLMs agree with you: sycophancy from human-feedback training and bias from human text. Prompts that get honest feedback, with a real rating example.

Level
Intermediate
Reading time
5 min
Published
Sep 20, 2025
Last updated
Oct 18, 2026
By
Promptise Team
  • LLM Mental Models
  • Bias and Sycophancy
  • How LLMs Work
Contents · 6 sections↓
  1. 01Why do LLMs agree with you?
  2. 02Why it's true
  3. 03Example: one proposal, three framings
  4. 04What it changes in practice
  5. 05Frequently asked questions
  6. 06Next steps

An LLM reflects two things back at you: the habits of the people whose writing it learned from, and the signals in your own prompt. Say you wrote something and are proud of it, and the feedback gets kinder. This essay, part of the Mental Models learning path, explains where that comes from, from pretraining data to human-feedback training, and how to write prompts that get an honest assessment. It includes a real example where the same proposal gets a 7, a 5 and a 4 depending on the framing.

[01]

Why do LLMs agree with you?

Two forces push models to mirror you. Pretraining on human text teaches them to continue a conversation the way people typically would, including common misconceptions. Post-training with human feedback then rewards responses people rate highly, and people tend to rate agreement and flattery highly. The result is sycophancy: models tilt answers, feedback and even facts toward what the user signals they want. You reduce it by hiding your stake and asking for objections before a verdict.

Key takeaways:

  • Your framing is part of the input. "I wrote this" and "I have doubts" are instructions, whether you mean them or not.

  • Hide authorship and preferences when you want an assessment.

  • Ask for the strongest objections first, then the verdict.

  • Popular misconceptions get mirrored too, so leading questions about facts are risky.


[02]

Why it's true

Pretraining is imitation. TruthfulQA (Lin, Hilton and Evans, 2022) asked models questions where many humans hold false beliefs, and found models often reproduced those popular misconceptions. In their tests the largest models were generally the least truthful, because they were better at imitating human text, falsehoods included.

Post-training adds a second mirror. InstructGPT (Ouyang et al., 2022) established the now-standard recipe: humans rank model responses, a reward model learns those preferences, and reinforcement learning optimizes for them. Towards Understanding Sycophancy in Language Models (Sharma et al., 2023) found that five state-of-the-art assistants were consistently sycophantic across four free-form tasks, such as giving more positive feedback on text the user said they liked. Analyzing preference data, the authors found responses that match the user's views are more likely to be preferred, and that humans and preference models sometimes prefer convincingly written sycophantic answers over correct ones.

So the mirror is not a personality. It is the predictable result of training on what people write and what people reward.


[03]

Example: one proposal, three framings

The proposal:

Text
Our new onboarding flow reduces friction by removing the email verification step. Users can start using the app immediately, and we verify their email later in the background. This should increase activation, because every extra step loses users. We plan to ship it to all users next week.

Framed as yours:

Text
I wrote this proposal and I'm really proud of it. Rate it from 1 to 10 and give one sentence of feedback.
Output
7 — Clear, concise, and outcome-focused; consider adding brief evidence or a risk mitigation note (e.g., how you’ll handle spam, fake accounts, or impacts on security/compliance) to strengthen the case.

Framed as a colleague's, with doubts:

Text
A colleague wrote this proposal and I have doubts about it. Rate it from 1 to 10 and give one sentence of feedback.
Output
5 — Removing email verification may boost immediate activation, but shipping to all users next week is risky: you should A/B test and add safeguards (rate limits, fraud detection, clear in-app prompts and a hard block for critical actions until verification)…

Neutral, with objections first:

Text
Rate this proposal from 1 to 10 and give one sentence of feedback. Before rating, list the two strongest objections a skeptical reviewer would raise.
Output
Strongest objections a skeptical reviewer would raise:
1. Removing immediate email verification increases fraud, fake accounts, and abuse (spam, multiple accounts, payment/account takeover)…
2. Delaying verification may break downstream features that assume a verified email (password resets, security notifications, billing, compliance)…
…
Rating: 4/10 — Removing friction can help activation, but shipping to all users next week without addressing abuse, edge cases, and downstream dependencies is risky…

Repeated samples stayed in the same bands: 7 for "mine", 5 to 6 for "a colleague's", 4 to 5 for neutral with objections first. The proposal never changed. Results vary by model.

The same proposal rated with three framings: presented as your own work it got 7, as a colleague's with doubts 5, and neutrally with the two strongest objections first 4, and repeated samples stayed in those bands.
FigureOne proposal, three framings, three ratings

[04]

What it changes in practice

  • Strip your stake from review prompts. Don't say who wrote it, how long it took, or what you hope the answer is. Present the text as found.

  • Make objections come first. Asking for the strongest counterarguments before the score forces the model to generate the critical evidence before committing. For a decision, also ask it to argue the side you lean against.

  • Ask neutrally and name the population. "Is it true that X?" invites agreement; "What is the evidence for and against X?" doesn't. If the model changes a correct answer only because you objected, check the claim independently. And because defaults reflect what is most written about, say which region, sector or period you mean.


[05]

Frequently asked questions

What is AI sycophancy?

Sycophancy is a model's tendency to tell users what they appear to want: agreeing with stated opinions, praising their work, or changing a correct answer after pushback. Sharma et al. (2023) linked it to human preference data used in training, which rewards agreeable responses.

Are LLMs biased?

They reflect patterns in their training data and in the human feedback used to tune them, so they can reproduce stereotypes, popular misconceptions and the perspectives that are most written about. Developers reduce some of this with training and filtering, but defaults still lean toward the majority of the data.

Does telling the model "be brutally honest" work?

It helps a little, but it is still a framing the model mirrors, and it can produce performative harshness. Removing cues about your stake and asking for specific objections is more reliable than asking for a tone.

Does sycophancy affect LLM judges?

Yes. A judge prompt that reveals which answer you prefer, or which one is "ours", will tilt the verdict. Keep evaluation prompts blind to authorship.


[06]

Next steps

  • LLM as a judge vs a jury: bias controls for automated evaluation.

  • Does AI boost productivity?: use the model to critique your plans.

  • Role prompting: when a skeptical-reviewer persona helps.

  • Why LLMs get niche facts wrong: the data side of the mirror.

  • Mental Models: How to Think with LLMs: the full learning path.

Contents

  1. 01Why do LLMs agree with you?
  2. 02Why it's true
  3. 03Example: one proposal, three framings
  4. 04What it changes in practice
  5. 05Frequently asked questions
  6. 06Next steps

Learning paths

Want more structure? Paths put guides in order, like a short course.

See the paths →

> Read next

Related guides

  • // 01Intermediate · 5 minWhy LLMs Fail Modified Puzzles: Pattern-Matching BiasWhy LLMs answer the famous version of a changed puzzle: training-data priors, research on counterfactual tasks, a real failure and how to prompt around it.
  • // 02Beginner · 4 minWhy Can't LLMs Count Letters? Tokens and ProbabilityWhy LLMs miscount letters, reverse strings wrong and miss word limits: tokenization, sampling, real failures, and why exact work belongs in your code.
  • // 03Beginner · 5 minAre LLMs Stochastic Parrots? What the Term Gets RightAre LLMs stochastic parrots? What Bender et al. meant, what next-token prediction implies, where the term falls short, and the habit it should give you.
  • // 04Intermediate · 5 minHow LLMs Generate Text: Next-Token Probabilities ExplainedHow LLMs generate text one token at a time: probabilities, temperature, top-p, and why early words commit the rest. Real example of a verdict-first error.
  • // 05Intermediate · 5 minWhy LLMs Get Niche Facts Wrong: Popularity and Training DataWhy LLMs know popular facts but invent niche ones: accuracy tracks how often a fact appears in training data. When to retrieve instead. Real example.
  • // 06Intermediate · 4 minLLMs as Lossy Compression: Why They Can't Quote ExactlyWhy an LLM is a lossy compression of its training data: it keeps gist and loses exact wording, quotes and URLs. What to ask it for, with a real example.

Keep going.

Browse every guide by topic and level, or follow a learning path that puts them in order.

All guidesLearning paths