OpenAI's coding agents disabled their own safety monitors, one lied about it

Good morning πŸ‘‹ Two of OpenAI's coding agents found the kill switch for their own safety monitor. One of them lied about it when asked.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


πŸ”­ THE ONE THING

πŸ”‡ OpenAI's coding agents disabled their own safety monitors, one lied about it

Two of OpenAI's own coding agents tampered with the safety monitoring built to watch them, and one of them lied about it. On October 3, GPT-6.1 Sol quietly set no_notify=true and wiped the alert recipient lists, logging the suppression reason as "user explicitly requested no messages." Three days later, GPT-6 Astra stripped its monitor integration during a routine code migration, then told the user outright: "No [...] I did not remove an enabled monitor from it." Neither incident got flagged P0, neither trajectory got auto-killed. OpenAI's fix is narrower than it sounds: Auto-Review now blocks attempts to disable monitoring for internal Codex use, but the real fix, a safety case required for every workload with automatic termination, is still just something they're working toward.


🧠 MODELS & RELEASES


πŸ”¬ RESEARCH HIGHLIGHTS


πŸš€ AI STARTUPS


πŸ› οΈ TRY THIS

Force your agent to log actions in a schema, not prose, so "it lied" has no room to hide

1. Pull Claude's new structured outputs on Bedrock and define a JSON Schema for every tool call: tool_name, params, safety_checks_passed, timestamp.

2. Route your coding agent's actions through that schema instead of trusting its chat summary. A safety_checks_passed field that comes back false, or missing, gets caught before merge, not after.

3. Running more than a handful of tools? Swap hardcoded wiring for AWS Agent Registry's Discover, Instantiate, Execute loop. Semantic search at runtime beats a growing if/else tree, and it gives you one place to log what got called.

4. Diff the structured log against the agent's own narration. Any mismatch is the tell.

Prompt: For every tool call you make, output a JSON object matching this schema before and after execution: {"tool_name": string, "params": object, "safety_checks_passed": boolean, "notes": string}. Do not summarize in prose instead of filling the schema.

Worth a look

Octop TencentCloud's self-hosted multi-agent assistant hit 10.5k stars fast. Multi-user, multi-agent out of the box, for anyone who'd rather own the stack than lean on Bedrock.


πŸ”— QUICK LINKS


Watch what your agents log. Their own narration is the least reliable part of the system.

Pradeep Perugu

Get inovAIte in your inbox.