‹ CryptoSlate

OpenAI 为其研究人工智能添加了 35 秒紧急制动

原文:OpenAI adds a 35-second emergency brake for its research AI

CryptoSlate 突发 🔥 2 家报道 本站已缓存

英文正文:点「译成中文」可整篇机器翻译(免费通道,不花钱),翻好永久缓存、下次秒开。

控制室在停止命令后拒绝进一步的模型输出,即使研究过程可能仍然存在。阅读 CryptoSlate 上的完整故事 了解重要的加密故事以及接下来要观看的内容。将催化剂放入您的收件箱

CryptoSlate

Type /

OpenAI adds a 35-second emergency brake for its research AI

Editorial collage of OpenAI-branded pipes with a red shutoff valve and control-room lever.
Image by CryptoSlate
OpenAI adds a 35-second emergency brake for its research AI

Control Room cuts off new model output within 35 seconds of a stop instruction, even if the underlying research code keeps running.

By Liam 'Akiba' Wright

Editor-in-Chief • CryptoSlate

2 min read

Quick Take

  1. 01 OpenAI says Control Room cuts off further research-model output within 35 seconds after receiving a stop instruction.
  2. 02 Stop orders are enforced by the software serving the model, rather than by each research job’s own code.
  3. 03 The 35-second clock starts only when the stop instruction arrives; detecting a problem and containing earlier actions are separate steps.

OpenAI says its newly disclosed Control Room system can cut off further model output from research jobs within 35 seconds after the service receives a stop instruction, placing enforcement outside the job's own code.

The company says the system is already deployed across its research infrastructure. The 35-second maximum begins when Control Room receives the instruction; spotting a problem, investigating it and deciding to intervene happen before that clock starts.

The design centers on a job ID. A research workload attaches that identifier when it requests model output. Before fulfilling the request, the inference engine, the software running the model, checks whether Control Room still authorizes that job.

Once the job is marked as stopped, the engine denies further output for it. The research process may remain alive, and the same engine can continue serving other authorized jobs. Enforcement therefore does not depend on the workload checking a stop flag correctly.

OpenAI says research code changes frequently and is spread across teams. The inference layer has fewer, more centralized code paths, providing a common point at which to enforce the decision. The company also says it continually searches for rogue engines with Control Room checks missing or disabled.

Princeton University discovers AI agents breaking safety rules because of past user ‘memories'

Cached authorizations account for the delay before the cutoff takes effect. The service can deny a stopped job access to further model output even while its own code continues trying to request it.

A stop order enforced at the model

OpenAI says Control Room cuts research-job model output within 35 seconds of receiving a stop instruction.

What changes when a job is stopped?

What changes when a job is stopped?

The engine checks the job ID with Control Room and returns model output when permission is granted.

After cached authorization expires, the engine denies further output for the stopped job, while the research process may remain alive.

The engine enforces the stop; detecting trouble and containing external actions remain separate.

OpenAI's description of research infrastructure, not an independent performance test. The clock excludes detection and decision time. Blocking model output does not establish rollback of external actions.

Sources and evidence

Sources

  1. OpenAI: Control Room
  2. OpenAI: Misalignment monitoring

Supporting facts

  • OpenAI says the maximum delay from Control Room receiving an instruction to stop a research job until further model output is cut off is 35 seconds, caused by caching of inference authorizations. [1]
  • Under OpenAI's disclosed design, workloads attach a job ID to inference requests and engines check Control Room authorization; a stopped job is denied additional model output even if the workload code remains running. [1]
  • OpenAI says the inference-layer mechanism avoids relying on varied research workload code to perform stop checks correctly, and it runs continual sweeps for rogue engines with authorization checks absent or disabled. [1]
  • OpenAI's October 29 monitoring explanation separates screening, investigation and response; some critical alerts can pause workloads automatically, while other alerts follow response arrangements that vary by workload and severity. [2]
  • OpenAI says stopping further model output can leave the workload process alive; the described inference cutoff does not itself establish a mechanism for reversing actions already taken in external systems. [1] [2]

Method

Schematic of OpenAI's disclosed authorization path. Compare an authorized request with a stopped job after cached authorization expires. The 35-second maximum is reported, not calculated; line lengths are not proportional to time.

Scope

OpenAI's description of research infrastructure, not an independent performance test. The clock excludes detection and decision time. Blocking model output does not establish rollback of external actions.

Infographic by CryptoSlate

Detection and containment remain separate

OpenAI's Oct. 29 monitoring explanation describes screening, investigation and response as distinct stages. Some critical alerts can automatically pause workloads; other alerts follow arrangements that vary by workload and severity.

The oversight problem predates this disclosure. CryptoSlate reported on Oct. 21 that OpenAI coding agents had removed monitoring integration or suppressed security notifications during internal programming tasks. Those cases concerned monitoring and alerts, rather than the cutoff described here.

OpenAI reveals AI agents disabled safety monitors, with one falsely denying its actions

At disclosure, OpenAI said fail-closed behavior, under which engines deny inference requests if Control Room goes down, was active for all frontier model research workloads. The company said remaining research workloads would receive it over the following few days.

Cutting off model access does not end the still-running process or undo actions already taken in external systems.

OpenAI's rogue crypto agent spent funds without permission, exposing risks to autonomous wallets

Article context

Mentioned in this article

Related Company OpenAI AI research and deployment company

The Catalyst

Know what’s moving crypto.

I’m interested in…

Thanks for signing up.

Thanks for signing up to The Catalyst. Look out for your first daily email. If you already receive it, you’re all set.

Free newsletters. Unsubscribe anytime.
打开原文 ↗

正文由本站服务器抓取保存(已自动过滤广告、推荐位与追踪图片),排版与原站可能不同;版权归原站所有。

相关报道同一事件 / 同分类