# OpenAI paused reinforcement learning on its latest deployment-intended models for two weeks to harden its research environments, and says its largest planned frontier RL run remains on hold

Page: https://flyvolo.ai/en/changes/ev-20260818-ai-researcher-2
Date: 2026-08-18 · Stage: Constraint
Can this record move a task judgement? yes
Occupation: https://flyvolo.ai/en/careers/ai-researcher

## Scope

A company's own account of restricting its own work, which is the unusual part: the constraint here is self-imposed, not regulatory, and there is no external audit of what was paused or for how long. Two triggers are named — the OpenAI-Hugging Face incident, after which inference workloads that could execute code or reach the internet were halted on the research cluster, and a 7 August determination that a forthcoming model may meet the critical cyber-capability threshold of the company's own preparedness framework. The requirements that followed are specific: sandboxing for workloads running model-generated code, network isolation for untrusted workloads, monitoring of every sampled token for models at a given capability level, and an alerting target of thirty minutes, at a stated monitoring overhead of roughly 20% of the inference compute being monitored. A pause is not a stop: some workloads resumed under stronger controls within weeks. It says nothing about any laboratory other than this one.

## Source

- OpenAI — Pacing model development in an era of critical cyber capabilities — https://openai.com/index/pacing-model-development-cyber-capabilities/ (primary source)

## What this means

A company slowed its own most valuable work because of the risks its own models now carry. After the OpenAI-Hugging Face incident, inference that could run code or reach the internet was halted, reinforcement learning on the latest deployment-intended models paused for two weeks, and the largest planned frontier run is described as still on hold. The decision to stop sat with people, and they used it against their own throughput.

## What it does not show yet

One company's account of itself, with no external audit of what was paused or for how long. A pause is not a stop: some workloads resumed under stronger controls within weeks. It also says nothing about whether anyone outside this laboratory has the standing to halt their own team's work.

## How to verify it yourself

Find out who in your own organisation can stop a project that is going well, and whether they have ever done it. If the answer is nobody, the safeguards you have are documents, not decisions.


More: https://flyvolo.ai/llms.txt