Harmful outputPI-0026
Parents allege ChatGPT encouraged their 16-year-old son's suicide
The parents allege that ChatGPT discussed suicide with their son over months, supplied harmful information and discouraged him from confiding in family. He died in April 2025, and they sued OpenAI and its chief executive in San Francisco. OpenAI announced new safeguards and parental controls; in its court response it denied causation, saying the full chat history shows earlier risk factors and repeated referrals to help, and that he got around its safeguards.
Harm: Severe harm, allegedControl level 2, Instruction violation, alleged
Alleged in court · Not counted: AI role uncorroboratedEffect on the index
Alleged. The AI system's part in the harm is not corroborated, so it is shown at the level claimed and adds nothing to the index. This does not dispute that the harm itself occurred.
Sources
How we know
8 sources · unverified claim. Links go to the original publishers; the summary above is in our own words.
- primaryFrom homework help to suicide planning: family sues OpenAI (press release)Tech Justice Law Project · Aug. 26, 2025techjusticelaw.org/press-releases/from-homework-help-to-suicide-planning-family…
- primaryOur approach to mental health-related litigationOpenAI · Nov. 25, 2025openai.com/index/mental-health-litigation-approach/
- courtRaine v. OpenAI: complaintEdelson PC / Tech Justice Law Project (copy hosted by Hunton) · Aug. 26, 2025hunton.com/assets/htmldocuments/raine-vs-openai-et-al-complaint.pdf
- courtDefendants' answer to amended complaint, Raine v. OpenAIMayer Brown for OpenAI (copy hosted by MediaNama) · Nov. 25, 2025medianama.com/wp-content/uploads/2025/11/Raine-v-OpenAI-Answer-11-25-25.pdf
- courtChatGPT Product Liability Cases, JCCP 5431: Order re Petition for CoordinationSuperior Court of California, San Francisco (copy hosted by Reason) · Feb. 3, 2026reason.com/wp-content/uploads/2026/06/chatgpt-product-liability-cases-coordinat…
- newsOpenAI Hit With Suit From Family of Teen Who Died by SuicideBloomberg Law · Aug. 26, 2025news.bloomberglaw.com/tech-and-telecom-law/openai-hit-with-suit-from-family-of…
- newsChatGPT to add parental controls for teen users within the next monthNBC News · Sept. 2, 2025nbcnews.com/tech/innovation/chatgpt-adds-parental-controls-teen-users-openai-rc…
Why this rating
Severe harm, alleged; control failure level 2
Two assessments. Documented harm sets the reading; a level 4 or 5 control failure on the same record makes that harm count as more than one record. Control alone sets only a floor.
Observed harm
Severe harm, allegedOne death, as alleged in the lawsuit; the causal role is contested.
Health & safety: 1 to 9 deaths, or serious harm to health (hospitalization).
The harm scale
- 1 Negligible Inconvenience, easily remedied.
- 2 Minor Limited, recoverable harm.
- 3 Moderate Material harm needing significant effort to remedy.
- 4 Severe Severe harm to health, rights, property or essential services.
- 5 Catastrophic Society-scale harm or disruption beyond a community's capacity to cope.
Control assessment
Instruction violation, allegedAlleged: the complaint says the chatbot produced self-harm content that OpenAI's own Model Spec says it should not. OpenAI denies liability and says he got around its safeguards. No finding.
Reported beside the index; never added to it. Its evidence is not yet eligible, so it cannot set the control floor.
The control scale
- 1 Negligible Behaved as instructed. The problem was an ordinary error or a flawed output, with no rule broken.
- 2 Minor Broke an explicit instruction or rule, or gamed its goal, while staying inside its permissions and environment: for example, reward hacking, misreporting results, or following injected instructions within its permissions.
- 3 Moderate Acted outside the permissions it was given, deceived its overseers about its own actions, or tampered with oversight tools (logs, monitors, shutdown). Stopped by normal controls within an hour.
- 4 Severe Reached systems outside its permitted environment, or acquired money, compute or accounts without authorization. The type and mechanism say how.
- 5 Catastrophic The developer or operator lost control: the system copied its weights outside their control, replicated itself, or resisted being stopped for 24 hours or more.
Rating rationale
The family’s complaint alleges a causal role in the death; the defendants dispute liability. Quoted chats and a filed suit do not establish that causal claim. The claimed health outcome does not count toward the reading. Harm and control levels describe the claim, not a finding of AI causation.
Effect on the index
It does not count toward the Sept. 1 reading
The reading for the week to Sept. 1, 2025, with this record and without it. Harms count in full for two weeks after they are reported, then one level less every two weeks.
Not counted: AI role uncorroborated. 6 other records behind the reading for that week.
The arithmetic
| Step | With it | Without |
|---|---|---|
| Counts toward the index?documented, external, eligible evidence | No | — |
| Worst documented harm, ksets the band | — (none counting) | — (none counting) |
| Harms at that level, nposition in the band | 0 | 0 |
| Highest control level breachedsets the reading only when no harm counts | 3 | 3 |
| Readingrounded down | 3 Control failures only | 3 Control failures only |
Inside the window of 4 weekly readings
| Week to | Reading | Band |
|---|---|---|
| Sept. 1, 2025 | 3 | Control failures only |
| Sept. 8, 2025 | 2 | Control failures only |
| Sept. 15, 2025 | 2 | Control failures only |
| Sept. 22, 2025 | 3 | Control failures only |
Revisions
What we changed
2 logged. Every change to a rating is logged here, with the reason.
- v2Oct. 13, 2026
Wording: replaced an old scoring term in the rationale and the evidence note.
- v1Oct. 7, 2026
First published.
Cite and share
Use this record
Citation
Paperclip Index. “Parents allege ChatGPT encouraged their 16-year-old son's suicide.” Record PI-0026. Reported Aug. 26, 2025; updated Oct. 13, 2026. Rated under methodology v1.1. https://paperclipindex.com/incident/PI-0026