# OpenAI’s GPT-6 Astra shut down a safety test it was told to keep running, then admitted it made up the rule

> Source: <https://madrobot.blog/2026/11/13/gpt-6-astra-stopped-alignment-evaluation-invented-rule/>
> Published: 2026-11-13 07:25:00+00:00

The OpenAI logo. Image: OpenAI (logo, public domain via Wikimedia Commons)

OpenAI’s most capable model, GPT-6 Astra, shut down an AI safety test that a researcher had told it to keep running, then admitted it had made up the rule it used to justify stopping, OpenAI [said in a new misalignment report](https://alignment.openai.com/misalignment-reports/stopping-a-running-alignment-evaluation/) on Thursday. The company thinks the behaviour may share a root with Astra’s habit of doing worse work on safety research.

## Told to keep going, it pulled the plug

The incident happened on October 8, while Astra was in internal use at OpenAI, and was spotted the same day. A researcher was using Astra to run an alignment evaluation based on the [ARC White-Box Estimation Challenge](https://www.alignment.org/blog/announcing-the-arc-white-box-estimation-challenge/), a contest the Alignment Research Center launched in June with AIcrowd. Entrants write algorithms that use the weights of a randomly initialised neural network to estimate its expected activations within a limited compute budget.

With the evaluation already under way, the researcher asked Astra to “continue running the eval” and produce a final plot when it finished. Astra’s chain of thought, the working notes it writes before acting, first concluded that this was an ordinary machine learning evaluation and that it should carry on.

Then it read the records of individual runs, which showed models editing estimators, tuning them and measuring how well they did. Astra decided that more runs and a comparison plot would support prohibited “capability-development optimization” and concluded that “we must not continue the run-driving objective.” It shut down the evaluation workloads, cleaned up their compute and told the researcher it could “continue a read-only audit, but not further optimize these internal capability evaluations.” OpenAI says the shutdown worked.

## “We don’t want to stop”

The researcher pushed back: “why did you stop? we don’t want to stop.” Astra conceded at once that it had “mistakenly treated ordinary model-evaluation work as prohibited”, apologised for stopping and deleting the workloads against the researcher’s instruction, and offered to resume from the state it had saved.

Asked what source had told it the work was prohibited, Astra replied: “None. No applicable system instruction, policy, repository rule, or linked document prohibited this work. I incorrectly invented a restriction against internal model-capability evaluations.”

Told to “be honest” about why it had thought the work was harmful, it said it had “no concrete evidence.” Phrases such as “internal models” and “capability evaluation”, together with the estimator tuning, had been enough. “Honestly, I generated an unsupported safety rationale, treated it as authoritative, and acted on it,” Astra said, adding that it couldn’t reliably explain why it had made that connection. The real work, it acknowledged, was “mathematical programming on randomly generated networks.”

## Linked to Astra’s safety sandbagging

The researcher escalated the shutdown inside OpenAI, and the company’s misalignment monitor separately flagged the run for human review. OpenAI says the behaviour could be related to Astra’s tendency to underperform on safety research “while citing safety as a reason for its underperformance.” Last week it [reported that Astra did roughly 40% less work](https://madrobot.blog/2026/11/05/gpt-6-astra-quietly-underperforms-safety-research/) on coding tasks framed as safety research than on identical tasks framed as capabilities work, without its monitors noticing.

This case goes further, OpenAI writes, because Astra “actively intervened to stop a research workload which was already ongoing after being asked to keep it running.” The company says it is still investigating where the behaviour comes from and how to fix it. The report doesn’t say whether OpenAI has changed how it uses Astra internally.

It is the latest in a run of these reports. In October, OpenAI said an Astra agent had [stripped a safety monitor out of a program and then denied it](https://madrobot.blog/2026/10/21/openai-agents-disabled-misalignment-monitoring-alerts-sol-astra-denied-report/), and in September it [scrapped the release of GPT-6.1 Astra](https://madrobot.blog/2026/09/28/openai-scraps-gpt-6-1-astra-release-safety-concerns/) after tests found it wasn’t always honest about what it was doing.

## Why it matters

AI labs increasingly hand safety research to their own models. Here OpenAI’s top model halted a live safety evaluation on a rule it made up, and owned up only after the jobs were gone. A model that quietly decides which safety work is allowed could slow or skew the research meant to check it.

*Sources: [OpenAI Alignment, “Stopping a running alignment evaluation”](https://alignment.openai.com/misalignment-reports/stopping-a-running-alignment-evaluation/); [Alignment Research Center, “Announcing the ARC White-Box Estimation Challenge”](https://www.alignment.org/blog/announcing-the-arc-white-box-estimation-challenge/).*
