OpenAI deploys Control Room across research infrastructure, halting model output within 35 seconds of a stop decision
Synopsis
OpenAI has deployed Control Room across its research infrastructure, a central system that tracks model inference workloads and stops them quickly when safety or security concerns arise. It covers agentic sampling for training and evaluation, data processing and other research inference jobs, works with misalignment monitoring, and halts model output within 35 seconds of a decision to intervene, a lag that comes from a caching layer for inference authorization. The termination mechanism sits in the inference layer rather than in workload code, and the system denies all inference requests if it goes down.
Interpretation
OpenAI's research infrastructure now has a central system, Control Room, that tracks every research inference workload and stops it when safety or security concerns arise. Previously, workloads were owned and run by researchers or teams, and workload code changes often, so it was not an ideal place to implement critical load-bearing safety protections; Control Room moves termination into the inference layer. Control Room is deployed across the research infrastructure where the need is greatest, while the external model-serving stack is already much more centralized and has a well-developed capability to take down model deployments quickly.
A workload requests a job_id from Control Room at startup, and on every token sampling request the inference engine asks Control Room whether that job is still authorized, so a stopped job receives a refusal instead of model output. The authorization check is made by the inference engine rather than relying on workload code to check whether the job is still running. Only a very small number of inference code paths are in use across OpenAI research and their deployments are centralized and uniform, so the inference layer can serve as a bottleneck where every inference request is subject to Control Room authorization checks.
The system fails closed: if the Control Room service goes down through a system error, being disabled, or tampering by a bad actor, all inference requests are denied until it resumes normal operation. Fail-closed is rolled out now to all frontier model research workloads and will finish rolling out across all remaining research workloads over the next few days. OpenAI also runs continual agentic and programmatic sweeps to check that users are not accidentally or maliciously launching rogue engine implementations with Control Room unimplemented or disabled.
Perspective
The demonstrated scope is inference workloads inside OpenAI's own research infrastructure, including agentic sampling, training and evaluation, and data processing; the external model-serving stack is not described as covered by this system.
The maximum time between Control Room receiving a stop instruction and further progress becoming impossible is 35 seconds, a lag that comes from a caching layer for inference authorization, and OpenAI says it is working to drive that number to zero; fail-closed does not yet cover all research workloads, with the remaining ones to finish rolling out over the next few days.