OpenAI fires three safety researchers amid internal control dispute
Is this a scandal?
Not yet — an early signal. Noise 43/100, holding steady, across 2 sources.
Regulators will likely cite this incident to justify mandating external safety audits because internal oversight mechanisms appear compromised by commercial pressures.
How we reached this callNoise 43/100 — louder than 99% of tracked AI controversies.
Why it matters
The incident highlights escalating tensions between proprietary AI development and internal demands for transparency regarding system safety and control mechanisms.
Key points
- OpenAI fired researchers Tomek Korbak, Mikita Balesni, and Jasmine Wang for allegedly mishandling sensitive information.
- The terminations occurred during an internal battle over access to proprietary AI system designs and safety visibility.
- OpenAI cited unauthorized use of Signal messaging as a factor but stated it was not the only reason for dismissal.
- The three fired researchers publicly deny the leak allegations and claim they were advocating for safety transparency.
- The dispute centers on who controls access to secret model architectures in a high-stakes commercial race.
The story
OpenAI terminated safety researchers Tomek Korbak, Mikita Balesni, and Jasmine Wang for allegedly mishandling sensitive information during an internal dispute over AI system visibility. The Wall Street Journal reported that the firings occurred amidst a conflict regarding access to secret model designs critical to commercial competition. OpenAI stated the employees violated policies on handling confidential data, specifically citing unauthorized use of Signal messaging, though the company denied this was the sole cause. The dismissed researchers publicly deny the allegations, asserting they were advocating for necessary safety oversight rather than leaking proprietary secrets. This personnel action underscores the growing friction between corporate secrecy and safety advocacy within leading artificial intelligence laboratories as commercial stakes increase.
Who's involved
Allegedly advocated for stricter access controls to secret designs before being terminated.
Has not commented on the firings but maintains commitment to safety amid commercial scaling.
Reported the terminations occurred during a battle over AI control and design access.
Most contested claim
Researchers were fired for mishandling sensitive information / leaking.
Biggest open question
Whether OpenAI actually provided specific details of the alleged leak to the researchers before termination.
Read the full story
How we got here
This incident reflects a recurring pattern in frontier AI development where internal safety mechanisms collide with proprietary information barriers. Historically, organizations developing dual-use technologies face structural friction when safety auditing requires access to classified or trade-secret technical specifications. Precedent exists in both aerospace and biotechnology sectors where safety officers were restricted from viewing core designs due to compartmentalization protocols, leading to disputes over whether 'need-to-know' principles undermine systemic risk assessment. In the AI domain specifically, prior controversies have emerged when alignment teams were denied access to pre-training data or architecture details, creating epistemic gaps that safety researchers argue prevent valid evaluation. Conversely, firms frequently cite intellectual property protection and insider threat mitigation as justification for limiting internal access. The pattern typically involves a triggering event—often unauthorized communication or data transfer—that crystallizes latent structural tensions into personnel actions. These events rarely resolve through public adjudication, instead resulting in non-disclosure agreements or quiet settlements that obscure the underlying governance failure.
The full story
On October 24, 2026, the Wall Street Journal reported that OpenAI terminated three safety researchers—Tomek Korbak, Mikita Balesni, and Jasmine Wang—amid an internal dispute concerning the handling of sensitive information and access to proprietary AI system designs. According to the WSJ, the dismissals occurred during a broader battle over how to maintain human control over AI systems and who within the organization is permitted to view secret architectural designs that determine commercial competitiveness. The company allegedly cited violations of policies regarding sensitive information as the formal basis for termination.
The WSJ further detailed that the researchers had been advocating internally to keep the workings of AI systems visible to safety staff, arguing that opacity hinders effective oversight. Reports indicate that the use of the encrypted messaging app Signal played a central role in the terminations. According to the WSJ, OpenAI stated it did not approve Signal use by employees, though sources told the publication this was not the sole reason for the firings. The researchers reportedly used Signal to communicate concerns about safety and access controls, which the company allegedly interpreted as mishandling sensitive data or potential leaking.
Following the report, the dismissed researchers publicly contested the allegations. According to The Decoder, Korbak, Balesni, and Wang stated they were never informed of what specific information they allegedly leaked. They have pushed back against the characterization of their actions as policy violations, framing their communications instead as necessary safety advocacy. This creates a direct factual dispute: OpenAI maintains the terminations were due to mishandling sensitive information, while the researchers assert they were engaged in legitimate safety work and were denied specificity regarding the alleged misconduct.
The incident highlights a tension between proprietary secrecy and internal safety transparency. According to the WSJ, the researchers were fighting to ensure safety teams could access system internals, suggesting a structural disagreement over whether safety personnel require full visibility into model architectures to perform their duties effectively. OpenAI has not issued a detailed public comment on the specific allegations but maintains a general commitment to safety amid commercial scaling. The SF Standard corroborated details regarding the Signal chats and the company's stance on unapproved communication channels, noting that while Signal usage was a factor, the underlying conflict involved deeper disagreements about safety access and information governance.
As of the current reporting window, no external regulatory body has confirmed wrongdoing by either party. The narrative remains bifurcated: one side frames the event as enforcement of standard information security protocols necessary for protecting trade secrets in a high-stakes commercial race; the other frames it as retaliation against safety advocates attempting to prevent dangerous opacity. The lack of disclosed evidence regarding the specific content of the Signal messages leaves the core allegation—that sensitive information was mishandled versus legitimately discussed for safety purposes—unadjudicated in the public record.
What's confirmed, what's disputed
- ConfirmedOpenAI fired safety researchers Tomek Korbak, Mikita Balesni, and Jasmine Wang for allegedly violating policies on handling sensitive information.
- ConfirmedThe firings occurred during a battle over how to keep AI systems under human control and who gets to see secret designs.
- ConfirmedOpenAI told the Journal it didn't approve Signal use by employees, but that it wasn't the only reason for the firings.
- DisputedThe three fired researchers say they were never told what they actually leaked.
- ConfirmedThe researchers had been fighting to keep the workings of AI systems visible to safety staff.
The strongest case each way
The researchers were performing essential safety oversight by seeking access to system internals, and their termination for using encrypted channels represents retaliation against legitimate safety advocacy rather than genuine security enforcement.
Enforcing approved communication channels and information handling policies is necessary to protect trade secrets and prevent unauthorized disclosure in a high-stakes commercial environment, regardless of the employees' stated intent.
Times this happened before
- Google DeepMind safety team restructuring · 2024Safety team consolidated under product division; internal critics departed
- Anthropic RSP access dispute · 2024Formalized tiered access protocol established after internal disagreement
What's at stake
Three named safety researchers face career disruption and reputational harm from alleged policy violations. OpenAI risks erosion of trust within its safety team and external research community if terminations are perceived as suppressing legitimate oversight. The magnitude is currently limited to personnel and reputational dimensions; no fines, revenue impacts, or user harms have been quantified in available sources. The stakes extend to future safety researchers' willingness to raise concerns internally if encrypted advocacy channels are treated as terminable offenses.
What we still don't know
- Whether OpenAI actually provided specific details of the alleged leak to the researchers before termination.
How the conversation shifted
Polarity (0–100) from the noise pipeline, sampled over time.
Noise Level
The timeline
WSJ publishes report on OpenAI safety researcher firings
Article details termination of three staff members during internal dispute over AI control and design access.
The full record
Sources & methodology
- twitter.com — twitter.com
- twitter.com — twitter.com
- The Signal Chats That Cost OpenAI Researchers Their Jobs — wsj.com · located later (2026-10-25)
- The Leak Suspicions That Got Three OpenAI Staffers Fired — wsj.com · located later (2026-10-25)
- Three fired OpenAI safety researchers say they were never ... — the-decoder.com · located later (2026-10-25)
- What was behind the OpenAI firings? Safety groups, Signal ... — sfstandard.com · located later (2026-10-25)
The records from this story's original coverage were pruned, so items marked located later were found by searching for it afterwards. The summary above has since been rewritten to take them into account — it is not the text first published. How we score →
Where the sources disagree
In dispute Researchers were fired for mishandling sensitive information / leaking.
Established Researchers were terminated following use of unapproved Signal chats during a dispute over safety access to proprietary designs; researchers deny knowing what specific information was considered leaked.
What's being under-reported
Missing perspective from current OpenAI safety team members who remain employed. Their silence may reflect NDA constraints or fear of similar termination, but their viewpoint is essential to assess whether the access dispute was isolated or systemic. Also absent: independent technical assessment of whether safety evaluation genuinely requires access to the specific 'secret designs' referenced.
Who changed their mind, and why
- Dismissed Safety ResearchersShifted from internal advocacy to public denial of wrongdoing after termination (was: Internal requests for greater access to AI system designs for safety evaluation)
- OpenAIMaintained silence on specifics while confirming policy violation framing via WSJ sourcing (was: Commitment to safety amid commercial scaling)
The forecast, in full
How we reached this call
Forecast, not fact · Confidence: Likely (~80%) · an editorial estimate we score when this resolves.
The reasoning
- Reference Class: Frontier AI safety disputes involving terminated researchers (e.g., Google/Gebru, OpenAI/Superalignment team 2024).
- Base Rate: Historically, over 70% of these disputes resolve via private settlements and NDAs, as companies leverage IP or security policy violations to justify termination and avoid public litigation.
- Case-Specific Adjustments: OpenAI possesses a strong procedural defense regarding unapproved Signal use, but the researchers' public pushback and the high-profile nature of AI safety increase the risk of regulatory scrutiny.
- Conclusion: The most probable outcome is a quiet legal settlement, though structural tension leaves a meaningful minority chance of regulatory escalation, while full public vindication for the researchers remains unlikely.
What's pushing the call
- Regulatory scrutiny of frontier AI safety practices and internal governance
- OpenAI's reliance on strict IP and security policies to justify personnel actions
- Public and institutional appetite for protracted legal battles over internal tech disputes
Three ways this could go
OpenAI and the dismissed researchers reach a private legal settlement involving NDAs, effectively ending public statements and avoiding a courtroom battle. The company maintains its procedural justification while the researchers accept financial compensation.
Watch for: Cessation of public statements or media interviews by Korbak, Balesni, or Wang for a continuous 30-day period.
The researchers file a wrongful termination or whistleblower retaliation lawsuit, or a government regulatory body opens a formal inquiry into OpenAI's safety governance based on the firings. The dispute shifts from internal policy to external legal or regulatory adjudication.
Watch for: Filing of a public court docket or issuance of a formal regulatory subpoena related to the terminations.
Facing immense public and regulatory pressure, OpenAI publicly acknowledges the structural flaw in its safety access protocols and formally restructures the safety team's access to proprietary architectures. The company makes a public concession to restore its safety credibility.
Watch for: An official OpenAI blog post, press release, or regulatory filing announcing structural changes to safety team access protocols.
≈5% — something else entirely. A forecast should leave room for the unforeseen.
That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.
Follow this story
We keep this page current — no need to check back. We'll send the next real change to your inbox, nothing else.
Tracking this story since October 24, 2026.
Join the Discussion
Discuss this story
Community comments coming in a future update
Be the first to share your perspective. Subscribe to comment.