NewsAI & DevelopmentDeveloper ToolsNews & Analysis

OpenAI DevDay 2026: Managed Agents — What Developers Must Know

OpenAI DevDay 2026 Managed Agents platform visualization with countdown and AI agent network
OpenAI's Managed Agents platform launches at DevDay 2026 on September 29

OpenAI’s Managed Agents platform was supposed to be a DevDay surprise. It wasn’t. Developers spotted it in the codebase three weeks before the September 29 event in San Francisco. But the actual headline isn’t the new platform — it’s Agent Builder, which OpenAI shipped just eight months ago, dying on November 30. If you built on Agent Builder, you’re already on a migration clock whether you knew it or not.

Agent Builder Shuts Down November 30

This is the most urgent thing in the DevDay story. OpenAI announced on June 3 that both Agent Builder and Evals would stop working at the end of November. Evals go read-only on October 31 — that’s your hard deadline to export anything you care about.

The migration isn’t clean. OpenAI’s own export tool moves the structure of your workflow but explicitly cannot transfer the following items to the new platform:

  • External credentials and OAuth grants
  • Connected app tokens (CRM connections, third-party integrations)
  • Knowledge bases and retrieval configurations
  • Control flow branches and triggers
  • Permissions and authorization scopes

You’re left with skeleton code and a manual reconnection job. The two official migration paths are the Agents SDK for code-first workflows, or Workspace Agents in ChatGPT for teams that don’t need to write code. There is no automatic path between them.

What Managed Agents Actually Is

Before the official DevDay announcement, TestingCatalog found four core capabilities in the codebase: agent creation and configuration, environment management, skills and plugin enablement, and session-based orchestration. That is the architecture.

The positioning fills the gap between the Agents SDK (write code, manage everything yourself) and Workspace Agents (natural language, no code). Managed Agents sits in the middle — a hosted runtime for teams that want more control than a no-code tool but don’t want to manage infrastructure.

What’s not confirmed yet: pricing, HIPAA eligibility, whether self-hosted environments will be available at launch, and rate limits. For enterprises in regulated industries, those answers determine whether this is usable at all. The parallel to Anthropic’s offering is direct — the codebase analysis notes the new platform “broadly follows what Anthropic currently offers.”

The Eight-Month Platform Risk

Agent Builder launched in October 2025. It was deprecated in June 2026. It dies in November 2026. That’s eight months from ship to shutdown.

That is not a bug — it is a pattern. OpenAI moves fast and deprecates fast. Developers who built production workflows on Agent Builder are paying for that speed now. The lesson for Managed Agents, AgentKit, and anything OpenAI ships at DevDay: avoid building deep integrations on platform-specific abstractions.

The practical hedge is MCP (Model Context Protocol), an open standard that works across agent runtimes. Build your tool integrations on MCP and you survive platform changes without rebuilding connectors. Anthropic co-created it, OpenAI supports it, and it is the standard that outlives the products built on top of it.

Build vs. Rent: The Real Decision

Managed Agents makes sense when your workload involves long-running tasks, stateful sessions, secure sandboxes, or scheduled deployments — cases where managing your own infrastructure adds overhead without adding value.

Roll-your-own remains the right call when you have HIPAA BAA requirements, Zero Data Retention constraints, fine-grained loop control needs, or unusual tool semantics that don’t fit standard patterns. Until OpenAI confirms self-hosted environment support and compliance eligibility, enterprises with those constraints have no clean path to Managed Agents.

The Rest of DevDay 2026

Managed Agents was not the only announcement at DevDay 2026. ChatGPT hit 800 million weekly users; the developer count doubled to 4 million; API token throughput increased 20x to 6 billion tokens per minute.

The Apps SDK lets developers build interactive applications that run inside ChatGPT conversations, with Booking.com, Spotify, Canva, and Zillow as launch partners. Codex officially shipped with Slack integration and enterprise admin tools. GPT-5 Pro is now available via API for high-accuracy use cases in finance, legal, and healthcare. Sora 2 is in preview with synchronized audio and image references. GPT-Realtime-Mini cuts voice model costs by 70%.

That is a dense release. But the migration deadline and platform-risk lesson are what matter most to developers with code running in production today.

What to Do Before September 29

You do not need to wait for DevDay to act. The timeline is already in motion:

  • Now: Audit your Agent Builder workflows and document all external integrations, credentials, and knowledge sources
  • Before October 31: Export all Evals data before it goes read-only
  • Before November 30: Complete migration to Agents SDK or Workspace Agents; validate with full test coverage including tool failures and unauthorized access scenarios
  • Going forward: Wire tool integrations through MCP to hedge against the next deprecation cycle

Managed Agents may be the better long-term platform once pricing and compliance details land after September 29. But right now, the only thing confirmed is the shutdown date for what you’re already using. Start there.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

    Your email address will not be published. Required fields are marked *

    More in:News