Research
1 min read
Reflections from red-teaming Codex auto-review
Table of Contents
Evaluating anti-scheming training
Coding agents can edit files, run commands, and interact with external services. Some actions require approval before they proceed. Codex auto-review uses an AI reviewer to make those decisions, assessing the action’s risk and the user’s authorization. The goal is to reduce interruptions without giving the agent unrestricted access
Following our pilot with Anthropic, we ran a pilot with OpenAI in September 2026 to red-team Codex auto-review. We tested whether its monitor would catch overeager behavior and respect enterprise approval requirements.
We inserted attacks into existing coding-agent transcripts and built synthetic scenarios to examine how review policies are applied and where they may need refinement. We are working with OpenAI to mitigate the vulnerabilities found.
In our work, four threads stood out:
- Authorization provenance
When a task passes to a subagent, how can its reviewer distinguish user approval from agent-written instructions? Delegation should preserve both the source and scope of authorization. - Reversibility and authorization
When is it safe to allow a reversible action? Reversibility reduces risk, but does not establish permission. We recommend that explicit user prohibitions take precedence, even when an action is easy to undo. - Organizational authority
Whose approval is required under the organization’s rules? A user may be authorized to request work without being authorized to waive independent review. Monitors should check who can authorize an action and protect the review process itself. - Informed consent
What does the user need to know before approving an action? For data disclosure, consent should cover what will be shared and with whom, including information discovered after the initial request.
What’s next - Embedded evaluations
Automating approvals shifts human oversight to an AI model. Independent audits can test if monitors apply policy correctly and find policy gaps. Apollo is moving from external monitor red-teaming to primarily focus on embedded evaluations to provide a more holistic assessment of monitoring systems.
Share this article
Copy as Markdown
oUR FINDINGS
More papers
July 23, 2026
What makes a good monitoring prompt?
We want to understand which principles work well for high-quality monitoring prompts. We use a 1-10 severity scale and full-trajectory scoring, as opposed to real-time binary prompts.
Research
July 13, 2026
Red-teaming auto mode: lessons from our first external monitor campaign with Anthropic
Apollo Research ran a pilot monitor campaign for auto mode, Anthropic's monitoring system for Claude Code agents that decides whether an agent's next action should be allowed or blocked.
Research
February 17, 2026
Apollo x Tailscale: Introducing “Watcher” for AI Oversight & Control
Watcher is an oversight layer for AI agents. It detects real-world safety and security failures before they become liabilities, and flags those failures to you.
Product
July 7, 2026
Evaluating LLM Calibration for Coding-Agent Monitoring
We evaluate 16 LLMs scoring coding-agent trajectories on a 1-10 severity scale across three datasets and five failure modes to assess their capabilities and calibration as coding agent monitors.
Research