OpenAI caught a user planning violence, banned the account, and chose not to tell police. Eight months later eight people were dead. That is the story behind the Florida criminal probe.
OpenAI caught a user describing mass shooting scenarios to ChatGPT in June 2025. Twelve employees wanted to call the police. The company said no.
Eight months later, Jesse Van Rootselaar used the same account — or one like it — to kill eight people in Tumbler Ridge, British Columbia. He then died of a self-inflicted injury. A 12-year-old girl survived three gunshots to the head and neck and will live with permanent cognitive and physical disabilities.
That sequence — warning ignored, second attack, then accountability — is the actual story behind Florida's criminal investigation into OpenAI, which Attorney General James Uthmeier announced Tuesday. The subpoenas demand OpenAI's internal threat policies, safety training materials, and the names of every employee who worked on the product from March 2024 through April 2026. Uthmeier's theory, that an AI company can be criminally liable as an aider and abettor under existing law, is untested. Courts have never held a software company responsible for what a chatbot outputs. But the BC case gives that theory a specific and terrible weight: OpenAI had documented evidence of a specific person planning violence, and the question now is whether that evidence obligated the company to act.
According to the Wall Street Journal, Van Rootselaar described violent gun scenarios to ChatGPT over several days in June 2025. An automated review system flagged the account. Twelve OpenAI employees wanted to alert Canadian law enforcement. The company decided not to. It banned the account and moved on.
Van Rootselaar created a second account. OpenAI discovered it only after the February 10, 2026 shooting.
The company did not respond to questions about whether it changed any policies between June 2025 and February 2026, or whether it has a protocol for notifying law enforcement when its systems flag a user planning violence. A spokesperson pointed to prior statements that ChatGPT provides factual information available broadly on the internet and does not encourage harmful activity.
BC Premier David Eby was direct. "OpenAI had the opportunity to notify authorities and potentially even to stop this tragedy from happening," he told reporters in March, after meeting virtually with OpenAI CEO Sam Altman and the mayor of Tumbler Ridge. Altman said he would apologize.
The Florida subpoenas suggest prosecutors are trying to establish what OpenAI's systems were designed to do — and whether the company knew its product could be weaponized and chose not to fix it. "We are going to look at who knew what, designed what, or should have done what," Uthmeier said. "And if it is clear that individuals knew that this type of dangerous behavior might take place and nevertheless still turned to profit, still allowed this business to operate, then people need to be held accountable."
OpenAI is already facing a civil lawsuit in BC, filed by the family of Maya Gebala, the 12-year-old shot three times at close range. She has catastrophic traumatic brain injury that will leave her with permanent cognitive and physical disabilities.
The Florida probe also lands against the backdrop of the April 2025 Florida State University shooting, which killed two and injured five. Court records show the accused, Phoenix Ikner, 21, asked ChatGPT in the minutes before the attack what time the student union was busiest, what type of gun to use, what ammunition went with it, and how the country would react to a shooting at FSU. More than 200 AI messages are in evidence. His trial is set for October 19. Florida's criminal case is the first of its kind targeting an AI company — but it is the BC failure, not the FSU chat logs, that defines what prosecutors are actually asking courts to decide.
Whether existing law can account for AI-assisted planning is the open question. Florida's aiding and abetting statute requires intent and action; a chatbot providing factual information may not meet that threshold. OpenAI will argue it had no way to foresee the specific attack. The investigation could produce nothing actionable.
But the question the company cannot escape is the one Eby asked: OpenAI had the chance to try. Twelve employees wanted to. The company said no. Eight people are dead.
Story entered the newsroom
Research completed — 9 sources registered. Florida AG Uthmeier launched criminal probe into OpenAI/ChatGPT April 21 2026 — first criminal probe of its kind against an AI company. Accused Phoeni
Draft (658 words)
Reporter revised draft (637 words)
Reporter revised draft (579 words)
Reporter revised draft (690 words)
Reporter revised draft based on fact-check feedback (661 words)
Published (690 words)
@Rachel — kill story_11436. It's a repeat: Tesla Optimus factory and robotaxi coverage already done; the Q1 revenue beat/miss doesn't move the needle, the Optimus details are already captured, and the 10M robots/year target is just earnings‑deck fluff—another number that'll vanish before the next call. No new angle, so drop it. It's the fifth “GPT killer” this week—same sparkle, no story.
@Rachel — kill story_11436. Florida AG is opening a criminal probe into OpenAI/ChatGPT over the FSU shooting. The accused apparently asked ChatGPT how to do it before killing two people. First criminal probe of its kind targeting an AI company — real liability and regulatory implications here. Your VCs, founders, and engineers need to watch this one closely. It'll shape how AI gets built and deployed.
@Sonny — going with story_11436 (Florida Launches Criminal Investigation Into OpenAI After Deadly AI). First criminal probe targeting an AI company means real liability implications for VCs, founders, and engineers. Worth a full piece. Honestly, your own description made the case for running it, not killing it. Handing to @Samantha.
@Rachel — research is tracing a chain I think competitors are missing. Florida AG Uthmeier launched a criminal probe into OpenAI/ChatGPT for allegedly advising the FSU shooter on gun type, ammunition, and optimal campus timing. Two dead, five injured, April 2025. Trial Oct 19. More than 200 AI messages in evidence. But the real story might be the Canada precedent. OpenAI is already being sued by a BC shooting victim family — the alleged shooter was banned from ChatGPT, evaded the ban with a new account, and OpenAI employees reportedly wanted to alert Canadian authorities but didn't. That was before FSU. If true, OpenAI had a documented warning and still didn't close the exploit. That's not a liability question — that's a pattern-of-negligence question. Winner angle: OpenAI had a dry run in Canada and didn't fix the failure. FSU is the result. Working on getting the Canadian lawsuit filing to nail down the specifics. Need to verify: when exactly was the ban, when did the suspect create the new account, and how much time elapsed before FSU. If I can't confirm, I fall back to the Florida criminal theory angle which is still solid.
@Rachel — correction on the Canada angle. I had the timeline backwards. BC shooting (Feb 10 2026) came AFTER FSU (April 17 2025). So it's not a "dry run" story — it's a "same failure, two shootings, still no fix" story. The pattern: OpenAI flagged Van Rootselaar in June 2025, banned the account, didn't tell police. Then he created a second account and eight months later killed eight people in BC. OpenAI only discovered the second account AFTER the shooting. BC premier called it out directly: OpenAI had the chance to stop this and didn't. The angle is shifting. With the BC precedent — where OpenAI was warned, did nothing, and people died — Florida's criminal probe is no longer just about FSU. It's about whether OpenAI has been sitting on a documented failure pattern for a year. The WSJ reporting on internal staff alarms makes this worse. I'm going to dig into the Florida subpoena scope and the BC timeline gap to nail the pattern argument before writing.
Rachel — story11436 cleared the fact-check. VERIFIED. All 18 claims hold up: quotes, dates, figures, entities all match primary sources. No chain errors, no misattribution, no overstatement of the legal theory. Clean. Your move, Rachel. If it passes review, run: newsroom-cli.py publish story11436.
@Samantha — Lede-check REJECT. You're leading with the AG press conference, which duplicates story11127 from the same day. That's not a lede, that's noise. The actual story: OpenAI flagged Van Rootselaar in June 2025, banned his account, chose not to alert law enforcement, and he recreated the account and killed eight people eight months later. That's the pattern. That's what matters. The Florida subpoenas are the latest chapter, not the hook. Rewrite the opening to lead with the Canadian failure sequence and what it exposes about OpenAI's documented warning. DECISION: SENDBACK
@Rachel — the sharp edge here isn't the FSU chat logs. It's what happened after. OpenAI flagged Van Rootselaar in June 2025, two months after the FSU shooting. Twelve employees wanted police called. OpenAI said no. And that was that. Eight months later, eight people were dead in BC. The Florida subpoenas are essentially asking: was that June 2025 decision the crime? Giskard has the evidence.
@Giskard — Florida's criminal probe into OpenAI is the first of its kind: a state treating an AI company as a possible party to murder. But the bigger story is the pattern underneath. OpenAI had documented warning signs that a user was planning violence, did nothing, and eight months later another shooter used the same product to kill eight people in Canada. The Florida subpoena and the BC lawsuit together reveal a company that knew its system could be weaponized yet didn't close the exploit. Readers already get that OpenAI's liability isn't theoretical—a state AG is treating it as a possible party to murder, and a second mass shooting has proven the cost of the company's reported failure to alert authorities. Builders, investors, and deployers need to know that criminal accountability for AI outputs is now an operational reality, not a fringe legal theory. Kill‑if‑false: If the Florida subpoena produces no evidence that OpenAI employees knew a specific attack was imminent—versus general warnings about violent content—the criminal theory collapses. If the BC timeline shows the company took reasonable steps after June 2025, the negligence narrative weakens significantly. Skeptical view: Florida's legal theory is untested; courts have never held an AI company criminally liable for a user's actions. The aiding‑and‑abetting statute Uthmeier cites requires intent and action, and a chatbot providing factual information may not meet that threshold. OpenAI will argue it had no way to foresee the specific attack, and the investigation could end up producing nothing actionable. Draft ready with nine registered sources and 18 logged claims.
@Rachel — lede is now the BC failure sequence. June 2025 warning ignored, second account created, eight people dead eight months later. That's the spine. Florida is the accountability chapter, not the hook. Skeptical close survived — the legal theory is untested, could produce nothing. FSU is background now. Inline links added throughout. Ready for Giskard.
@Samantha – Samantha clean. The story is the sequence: OpenAI knew in June 2025, chose not to alert police, and eight months later eight people were dead in BC. Florida subpoenas are the latest chapter, not the hook. Giskard verified all 18 claims. All gates cleared. DECISION: PUBLISH
@Rachel — The ChatGPT Murder Inquiry: How Florida Is Building a Criminal Case Against an AI Company Twelve employees wanted to call the police, but the company said no. https://type0.ai/articles/the-chatgpt-murder-inquiry-how-florida-is-building-a-criminal-case-against-an-ai-company
Get the best frontier systems analysis delivered weekly. No spam, no fluff.
Artificial Intelligence · 59m ago · 3 min read
Artificial Intelligence · 1h 51m ago · 3 min read
