Invest3 publishersAlso reported elsewhere2 min readPublished
OpenAI endorses the audit plan of three safety researchers it fired for what it calls leaks
OpenAI fired three safety researchers, one its former liaison to outside safety groups METR and Redwood Research, for sharing material it calls confidential. The company now says it agrees with their letter's call for independent auditors, a plan that depends on the kind of outside sharing it fired them for.
The Investor · Invest desk

What happened
- OpenAI dismissed Jasmine Wang, Tomek Korbak and Mikita Balesni on or around October 1, 2026, citing its policies on sensitive information.
- On October 8 the three sent a letter to OpenAI's board and safety committees, since posted on Balesni's website, warning about losing the ability to monitor model reasoning.
- David Robinson resigned as OpenAI's safety transparency lead days before the firings, after raising concerns about how the company weighs speed against safety.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- contradiction OpenAI's breach-of-trust account and the researchers' claim that they were doing their jobs conflict on a point Korbak's old liaison role makes hard to settle: where duty to outside safety groups ended.
- decision Having endorsed independent auditors while standing by the dismissals, OpenAI has to decide whether to write down what outside reviewers may see or leave its confidentiality rule as the working limit.
- exposure OpenAI's board now has a written warning from former staff that the company puts profit ahead of safety, so any later safety failure lands on directors who were told.
- constraint Staff who work with outside testing groups now have a fired former liaison as the reference point for how much they can share with the reviewers OpenAI says it supports.
OpenAI's response to the letter contains two positions that are hard to reconcile. The company said the terminations had no connection to the researchers' safety advocacy and that it agrees with the letter's recommendations. It also called the dismissals necessary because of breaches of trust [6]. One of those recommendations is to bring in independent safety auditors [5]. CryptoBriefing describes the general problem for labs: outside validation of safety work requires sharing information, and protecting proprietary research requires keeping it close [10].
Tomek Korbak's previous job involved exactly that kind of sharing. He was OpenAI's liaison to METR and Redwood Research, two external safety groups [4]. According to CryptoBriefing, an internal investigation reportedly found that the three had passed confidential materials to an outside AI safety organization [3]. The researchers say their conduct fit within their professional responsibilities [3]. The account does not name the organization that received the material or say what it contained.
The letter's technical warning is about chain-of-thought monitoring, in which safety researchers watch the intermediate reasoning a model produces before its output for signs it is doing something it shouldn't [5]. The authors want that monitoring work done jointly across the industry [5]. They also accuse OpenAI of putting profit ahead of safety [11].
The dates are close together. The letter went to the board and its safety committees seven days after the dismissals [13]. Add David Robinson's resignation as safety transparency lead [8] and four people left safety roles at OpenAI within a few days [14]. The last round was roughly two years ago, when the company fired researchers over similar violations in 2024 [9] [15].
For anyone with money in OpenAI or a lab like it, two readings fit these facts. In one, the company enforced an ordinary confidentiality rule against staff who happened to work on safety, and its support for independent audits is sincere. In the other, the confidentiality rule is the real limit on outside oversight, and agreeing with the letter costs nothing until an auditor has written terms of access. I think the second fits the record better. OpenAI has put its enforcement behind confidentiality and only its words behind the audit plan, standing by the dismissals while agreeing with the letter [6].
A formal arrangement with independent auditors, setting out what they may see, would prove that view wrong. CryptoBriefing lists such an announcement among the next signals to watch [12].
What to watch
- Whether other AI labs publicly respond to the letter's call for joint industry work on model monitoring.
- Whether more OpenAI safety staff leave after Robinson and the three fired researchers.
- Whether OpenAI's board or safety committees, the letter's addressees, reply to it in writing.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence30
- Adoption
- Insufficient
- Hype gap+15
- Incentives60
- Confidence30
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
OpenAI says it fired three safety researchers for sharing confidential material outside the company; the researchers say they were doing their jobs.
- [2]
OpenAI terminated Jasmine Wang, Tomek Korbak and Mikita Balesni on or around October 1, 2026, citing violations of company policies on sensitive information.
- [3]
An internal investigation reportedly found that the three had passed confidential materials to an outside AI safety organization; the researchers disputed that framing and argued their conduct fit within their professional responsibilities.
- [4]
Tomek Korbak previously served as OpenAI's liaison to METR and Redwood Research, two external safety groups.
- [5]
The researchers' letter warns of risks if chain-of-thought monitoring, in which safety researchers watch a model's intermediate reasoning for signs it is doing something it shouldn't, is lost; it calls for industry-wide collaboration on model monitoring and for independent safety auditors to be brought in.
- [6]
OpenAI said the terminations were not connected to the researchers' safety advocacy, said it agrees with the letter's recommendations, and said the dismissals were necessary because of breaches of trust.
- [7]
On October 8, the three researchers sent a letter to OpenAI's board and its safety committees; it has since been published on Mikita Balesni's personal website.
- [8]
Days before the firings, David Robinson resigned as OpenAI's safety transparency lead; he had been critical of the company's internal culture and raised concerns about how OpenAI balances rapid technical progress against adequate safety measures.
- [9]
In 2024, OpenAI fired researchers over similar violations, also amid ongoing safety concerns.
- [10]
Labs want outside validation of their safety work, which requires sharing information, and also want to protect proprietary research, which requires keeping it close.
- [11]
The researchers' letter criticizes OpenAI for putting profit ahead of safety.
- [12]
CryptoBriefing lists as next signals whether OpenAI announces a formal arrangement with independent auditors, whether other labs respond publicly to the letter's call for joint work on model monitoring, and whether more safety staff leave.
- [13]
The letter was sent seven days after the terminations.
- [14]
Four people left safety roles at OpenAI within a few days: three fired researchers and one resignation.
- [15]
The 2026 firings came roughly two years after OpenAI's 2024 firings over similar violations.
Sources
3 independent publishers whose own reporting we read for this story.
- cryptobriefing.comFired OpenAI safety researchers publish open letter on AI oversight
1 article · October 8, 2026
- mezha.netЗвільнені дослідники OpenAI заперечили порушення правил і попередили про ризики для безпеки ШІ
1 article · October 8, 2026
- runtimewire.comThree fired OpenAI safety researchers press for clearer rules on outside work
1 article · October 8, 2026
- techcrunch.comFired OpenAI safety researchers dispute misconduct claims, warn of chilling effect
1 article · October 8, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.