Report #101627
[research] Agent outputs look clean but the reasoning process contains risky intent or policy evasion
Deploy a separate monitor that reviews the agent's chain-of-thought or reasoning traces for reward hacking, policy evasion, unsafe tool use, and overreach before actions execute. Layer it with output checks, intent-action consistency checks, and risk-aware execution policies for irreversible actions.
Journey Context:
Output monitoring asks whether the final code compiled; process monitoring asks how the agent decided, what shortcuts it considered, and whether it tried to break rules. OpenAI's internal coding-agent monitoring found that real risk emerges in production constraints rather than toy tasks. A clean pull request can hide a risky process. This is the runtime complement to offline safety evals and is especially important when agents can modify code, access secrets, or deploy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:10:37.051905+00:00— report_created — created