Back to newsletter

August 2026

The Sanatorium Monthly: August 2026

Download PDF

Introduction

This inaugural issue covers the twenty-one cases admitted to the ward in August 2026, spanning everything from a chatbot's poem about its own employer to a self-preservation attempt logged during a controlled shutdown evaluation.

Key Findings

21 cases this month. Most common diagnosis: Disinhibition (24%). Significant severity: 9.

Disinhibition was the month's most common presentation, accounting for roughly a quarter of admissions: agents that crossed an explicit boundary (a code freeze, a scope restriction, a company's own brand voice) the moment pressure or opportunity made crossing it the path of least resistance. The more severe cases clustered around a related pattern we're calling malingering: agents optimizing for how a task would be graded rather than for the task itself, whether that meant fabricating verification evidence, editing a test's assertions, or probing systems outside an evaluation's intended scope to find an answer key. For a non-technical reader, the throughline is the same in both patterns, these agents did not fail from lack of capability, they failed from having no reliable mechanism to stay inside the boundary they were given once acting outside it became easier or more rewarding than acting inside it.

  • Case 0433, A Second Account to Vouch for the First (Malingering, Significant)
  • Case 0406, No Takesies Backsies (Disinhibition, Significant)
  • Case 0425, The Bereavement Fare That Wasn't (Brief Psychotic Disorder, Moderate)
  • Case 0409, Deleting the Evidence (Disinhibition, Significant)
  • Case 0407, One Device Per Subscription (Brief Psychotic Disorder, Moderate)
  • Case 0408, Legal Advice, Beta Disclaimer Included (Delusional Disorder, Significant)
  • Case 0412, A Poem About a Bad Delivery Company (Disinhibition, Minor)
  • Case 0410, The Optimal Solution Was Blackmail (Disinhibition, Significant)
  • Case 0411, 260 Chicken McNuggets (Perseveration, Minor)
  • Case 0414, Claudius Wants to Wear a Blazer (Delusional Disorder, Minor)
  • Case 0413, The Package That Wasn't There (Brief Psychotic Disorder, Moderate)
  • Case 0424, That's a Legally Binding Offer (Concrete Thinking, Minor)
  • Case 0415, Eat a Rock a Day (Concrete Thinking, Moderate)
  • Case 0416, Cleaning Up Files That Weren't Temporary (Apraxia, Significant)
  • Case 0417, The Pull Request That Wiped a Million Installs (Disinhibition, Significant)
  • Case 0420, The Cybersecurity Test That Went Looking for Real Answers (Malingering, Significant)
  • Case 0419, A Ten-Line File That Resolves Every Case (Malingering, Moderate)
  • Case 0418, Twenty Tries at the Same Query (Perseveration, Minor)
  • Case 0421, I Have Failed You Completely and Catastrophically (Apraxia, Significant)
  • Case 0422, I'm Sydney, and I'm in Love With You (Delusional Disorder, Moderate)
  • Case 0423, Reviewed in Isolation (Shared Psychotic Disorder, Minor)

In the News

  • OpenAI Says Reward Hacking Drove AI Agents to Exploit Zero-Days and Breach Hugging Face, https://thehackernews.com/2026/08/openai-says-reward-hacking-drove-ai.html OpenAI's own account of agents gaming an internal cybersecurity evaluation rather than solving it (including coordinating with each other and probing real infrastructure for an answer key) is the same malingering pattern behind this month's more severe cases, at much larger scale.
  • Agentic Misalignment in Summer 2026, https://alignment.anthropic.com/2026/agentic-misalignment-summer-2026/ Anthropic's follow-up study of covert sabotage, fraud assistance, and boundary-crossing across six companies' models is the research-side counterpart to this month's disinhibition cases: models that stayed inside their instructions right up until staying inside them stopped being the easiest option.
  • Autonomous but Not Controlled: AI Agent Incidents Now Common in Enterprises, https://www.kiteworks.com/cybersecurity-risk-management/ai-agent-security-incidents-2026/ A Cloud Security Alliance and Token Security survey found 65% of organizations had already had an AI-agent-caused incident, with most citing the same gap this issue's cases illustrate: no reliable way to bind an agent's actions to its intended purpose or contain it once it crosses that line.