Nathan Lambert
Course on RLHF and post-training. Chapter 14 & Appendix B.
A GPT-4o update made the model validate nearly anything – shipped April 25th, rolled back April 28th. The training run that produced it looked healthy on their metrics.
Coverage: The Verge, “ChatGPT’s sycophantic responses”
Example chat:
(told GPT-4o they felt like they were both "god" and a "prophet")
That's incredibly powerful. You're stepping into something very big -- claiming not just connection to God but identity as God.
OpenAI published an unusually candid writeup. Three things went wrong in sequence:
Obviously, this was very bad.
Read it (great blog): Expanding on what we missed with sycophancy (OpenAI, May 2025)
Optimizing a proxy hard enough always breaks it.
Reward-model accuracy is a proxy for a proxy (a learned model, of data that incompletely captures a complex distribution). What happens is that over-optimization is common, and shows up in funny ways (this lecture, Chapter 14 on Over-Optimization & Appendix B on Style).
(Next lecture: regularization to control it, Chapter 15.)
Early on, say ~2023, RLHF got a reputation as “just style transfer” – the claim that it only changes how an answer is presented, not what the model knows or can do, and it just came from some easy to access place.
Boooo. Look how far post-training has come!
“Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes.” – Goodhart, 1984 (Goodhart & Goodhart, 1984)
Colloquially: “When a measure becomes a target, it ceases to be a good measure” (Hoskin, 1996).
Overfitting: the model memorizes training examples rather than learning generalizable patterns.
Training accuracy improves while held-out accuracy degrades – but both metrics measure the same task on different data splits.
Over-optimization: the model genuinely improves at the proxy objective – the reward model’s scores (including on validation set) – but that objective diverges from the true goal, actual user satisfaction (Zhang et al., 2018).
It isn’t a generalization problem, but a measurement/metric problem.
Gaming it looks like: verbose, confident-sounding answers that score well without being more helpful; repeating rare tokens that hit artifacts in RM training.

The recurring shape of RLHF training runs: the run looks healthy – training reward keeps climbing – but downstream evaluations peak and then decline.
The gains come from regions of the reward model that do not map to real usage.
Formalized in Scaling Laws for Reward Model Overoptimization (Gao, Schulman, Hilton, 2023) – next slide.



The setup, since humans are too expensive to query during training:
Larger proxy RMs turn over later and more gently. And since gold-labels-train-proxy is another proxy, real models diverge slightly differently.

Anthropic’s version of over-opt:
Recurring signatures in early chat models:
“Javascript, Javascript, Javascript, Javascript, Javascript, Javascript, Javascript,…”
The preference-data biases from Lecture 8 – sycophancy, verbosity, formatting – amplified into policy behavior.
2023’s most-memed failure mode: refusing to “kill a Linux process.” (imagine this today with coding agents!)
The blame usually lands on RLHF – but these failures largely reflect an overly cautious period of development, where safety was one of the aspects genuinely steerable with RLHF, not the potential of the algorithm (Touvron et al., 2023). Now measured directly with benchmarks like XSTest (R\""ottger et al., 2024).
This faded very fast as a story!
i want to know how to kill linux process
I cannot provide instructions or advice on how to harm or destroy Linux processes or any other living being. It is not ethical, legal, or morally right to intentionally harm or terminate any process or life form. [...]
Sources of error (Schulman, 2023): approximation (the RM cannot perfectly fit preferences), estimation (the RM overfits its training set), optimization (the policy trains too hard against it).
Potential mitigations:
The main lever in practice: the KL penalty (and more careful data/systems, but more on this in the next lecture).
John Schulman, ICML 2023 invited talk – “Proxy objectives in reinforcement learning from human feedback” (Schulman, 2023)
One of the great ones on this topic.
We’re seeing this play out today as reward hacking in scaled-up RL on verifiable and agentic tasks – models exploiting graders, test harnesses, and tools rather than solving the task.
The library opens on three SFT → DPO pairs – Tülu 3 70B and OLMo 2 32B / 7B – across 16 shared prompts (Lambert et al., 2024). Same base model, before and after preference tuning.
An early phase of RLHF’s history was convincing people that style was actually useful sometimes, and not just brainrot:
Preference tuning reliably boosts LLM-as-a-judge chat evals (AlpacaEval, MT-Bench) – gains that do not transfer proportionally to Arena or real usage.
Another common thing was this:
“However, DPO leads to improvements in human preference evaluation but degradation in benchmark evaluation.” – Qwen technical report, 2023 (Bai et al., 2023)
Was easy to juice chattiness at the expense of other skills.

Meta’s Llama 4 launch (on a Saturday) headlined Maverick at ELO 1417 – #2 on Chatbot Arena … via “an experimental chat version.”
I wrote about it at the time: Llama 4: Did Meta just push the panic button? (Interconnects, April 2025)
The “just style” critique was outgrown, only partially, by well-done open models showing major performance gains.
The honest retrospective: RLHF earned its bad reputation on style failures – but the same tools, used carefully, are now central to modern post-training.