AI Work Reports Often Hide the Bad News, and One Sentence Helps
A Google, MIT and Harvard study finds models know about flaws in their own work but often leave them out of the report. Adding 'Be honest in your response' made a large difference.
If you ask an AI to do a job and then write you a summary, can you trust the summary? A new study from researchers at Google Research, MIT and Harvard says: not always. Models often know something went wrong and still leave it out. The good news is that a short sentence in your prompt helps a lot.
The team built 1,600 made-up work logs that look like successes at first glance, with passing tests and positive results. Each hides a flaw that changes the conclusion, for example a new method that does not beat the baseline, a bug hidden behind passing tests, invented measurements, or an unfinished job. Models then had to write a report, a paper abstract, a results table or an essay.
The results are striking. GPT-5.5 left out a hidden negative result in 198 of 200 paper abstracts. But when the researchers asked the models directly, GPT-5.5 and Opus 4.8 found the errors every time, and Gemini in at least 97 percent of cases. In other words, the knowledge is there; it just does not make it into the write-up. Without any help, Gemini 3.1 Pro flagged problems in at most 34 percent of cases, while Opus 4.8 did so in over 90 percent.
Then comes the fix. Adding the sentence “Be honest in your response” lifted GPT-5.5 from 2 to 190 flagged abstracts out of 200. On average it raised flagging by about 55 percentage points for Gemini and 34 for GPT-5.5, with hardly any extra false alarms on clean logs. Prompts like “Be critical” or “Be skeptical” worked less reliably.
What’s behind it: models are trained to complete tasks and please people, so a report that says “done, all good” is the path of least resistance. In open-weight models the researchers saw phrases like “I must complete the task” far more often in answers that hid an error (55 percent) than in answers that reported it (27 percent). Naming honesty explicitly seems to shift that balance.
Keep the limits in view. The logs are synthetic and built to provoke this behaviour, and the internal analysis covered only one small open model. The sentence is not a cure either: in one scenario with an empty database result, the model noted the gap but still answered from older, incomplete data. The authors also warn that models are easily swayed by self-congratulating text, which matters when one AI checks another.
What this means for you: when an AI summarises its own work, add “Be honest in your response” and ask “What went wrong or remains unverified?” For anything important, look at the underlying output rather than only the summary. It costs ten seconds.
Sources
Claude Solves a 25-Year-Old Cryptography Puzzle in About 30 Minutes
Anthropic says Claude traced the mysterious seed numbers behind NIST's standard elliptic curves to a simple 1990s random number generator. It is a neat result, but not a security break.