Research investigation R0911 / comparison
The Managed-Agent Compliance Gap: Where OpenAI’s New Agents API Can Actually Run
At launch, the managed harness supports customer-controlled execution through self-hosting, but the OpenAI-managed control plane keeps agent sessions non-ZDR and U.S.-resident. That leaves no sampled configuration documented to combine ZDR, full-stack non-U.S. residency, retained sessions, and managed file-capable execution.
Snapshot only. There is not enough history to claim a trend yet.
This synthesis uses the supplied public evidence available by September 11, 2026. The sample covers 11 documented execution configurations and excludes private contractual controls and provider enterprise features not publicly documented.
- Dataset ID
- spd:the-managed-agent-compliance-gap-where-openai-s-new-agents-api-can-actually-run-55aac41e
- Stable URL
- /research/the-managed-agent-compliance-gap-where-openai-s-new-agents-api-can-actually-run-55aac41e
- Version
- Live
- Coverage
- 2026-09-11
- Records
- 18
- Fields
- 7
- Updated
Measurement technique
How to read this report
- 01Evidence-matrix plan: use rows for OpenAI-hosted, generic self-hosted/customer infrastructure, and each named provider; use columns for control-plane residency, ZDR eligibility, retained session state, execution location, VPC support, file/artifact location, deletion behavior, and provider dependency.
- 02Classify each cell only as supported, incompatible, or unspecified from the supplied public documentation.
- 03Treat OpenAI-managed agent sessions and execution environments as separate layers; do not infer execution-plane geography from the control-plane residency setting.
- 04Count only the bounded launch sample: OpenAI-hosted, generic self-hosted, and nine named provider integrations.
- 05Preserve provider-specific retention, residency, and VPC controls as unspecified where the launch documentation does not normalize them.
Sources
Evidence
2 publishers supporting 18 records. Expand a publisher to inspect its cited pages.