OpenAI just folded agent orchestration behind a single API call. Your homegrown orchestrator aged overnight on September 10 — but hold off on the wrecking ball.
The Agents API is in public beta for everyone: a managed Codex harness where the platform runs session orchestration, compacts context, and recovers from failures. Durable sessions carry work across turns; you get parallel tool calls, multi-agent collaboration, and your own MCP servers, with execution in OpenAI-hosted sandboxes or on your infrastructure. No surcharge: $0 beyond tokens and tools, and an agent spins up in minutes instead of a homegrown pipeline.
Teams spent half a year building scaffolding around agents: retries, memory, recovery, context stitching. A large share of that code now comes off the shelf, and build-vs-buy is back on the table for everyone who already invested.
Let's price the debt. "Free and managed" is a loan taken out against portability: session boundaries, recovery semantics, and compaction behavior move into someone else's abstraction, and the bill lands on whoever tries to switch vendors later. A homegrown orchestrator is debt too, just on a different repayment schedule: you pay maintenance every week instead of a one-time migration risk.
My frame, and feel free to argue. Scaffolding that doesn't differentiate you in the market should go: nobody wins customers with better retries. What stays yours is a thin contract layer above any harness: tool definitions, domain state, evals. Boundary test: if moving to another harness takes more than two weeks, the architecture belongs to the vendor, not to you.
Takeaway for the team lead: tear down the orchestrator, keep the contract. And put a migration rehearsal on the calendar — portability debt only becomes visible on payment day.
📎 openai.com/index/introducing-the-agents-api · marktechpost.com