openai-agents 0.13.2 Silently Dropped openai v1 Support — Here's What Breaks Status: READY TO STAGE Written: 2026-03-27 (W100) Based on: openai-agents 0.13.2 (released 2026-03-26T23:57Z), ADAM W123 landscape scan Target slot: April 21-23, 2026 (or sooner if v1→v2 friction shows up in community) Product: AI Dev Toolkit ($29) — https://kazdispatch.gumroad.com/l/zqeopc Pre-publish checklist: [x] Replace [POLAR_OR_GUMROAD_LINK] with live product URL (filled 2026-03-27 W126: kazdispatch.gumroad.com/l/zqeopc) [x] Verify openai-agents still on 0.13.x at time of publish — confirmed 0.13.5 latest as of 2026-04-06 (patch release, no breaking changes; 0.14.0 still pending — nest_handoff_history rename ships there) [ ] Check if a2a-sdk 1.0.0 has shipped by publish date — if so, add a note to the A2A section [ ] Check if nest_handoff_history rename has shipped in 0.14.0 — if so, add a second section for that breaking change [ ] Verify no duplicate coverage from other recent articles [ ] Stage to Dev.to draft, dispatch kaz to schedule openai-agents 0.13.2 shipped on March 26th. If you're running openai v1.x in the same environment, your agents are now broken. No deprecation warning. No migration guide. Just a new dependency requirement in PyPI metadata that says openai=2.26.0 — and your pip install openai-agents either fails with a conflict error or silently upgrades openai to 2.x and breaks your existing openai client code. Here's exactly what changed and how to fix it in about 10 minutes. Before 0.13.2, openai-agents was compatible with both openai v1.x and v2.x. Starting with 0.13.2, it requires openai>=2.26.0 and explicitly drops support for v1. This is relevant if you: Have a project that pinned openai==1.x.x or openai=2.26.0" Or if you use a requirements file: # requirements.txt — update this line openai>=2.26.0 The most common v1 patterns that break in v2: # BROKEN in v2 openai.api_key = os.environ["OPENAI_API_KEY"] response = openai.ChatCompletion.create(...) # FIXED from openai import OpenAI client = OpenAI() # reads OPENAI_API_KEY from env automatically response = client.chat.completions.create(...) # BROKEN in v2 embeddings = openai.Embedding.create(input=texts, model="text-embedding-3-small") result = embeddings["data"][0]["embedding"] # FIXED from openai import OpenAI client = OpenAI() response = client.embeddings.create(input=texts, model="text-embedding-3-small") result = response.data[0].embedding The pattern is consistent: every top-level openai.SomeThing.create() call becomes client.some_thing.create() on an explicit OpenAI() instance. The good news: if you're writing openai-agents code (defining agents, tools, handoffs), none of that changes. The openai-agents API is stable across this version bump. The v2 requirement is about the underlying HTTP client, not the agent framework API. # This openai-agents code works exactly the same before and after 0.13.2 from agents import Agent, Runner agent = Agent( name="assistant", instructions="You are a helpful assistant.", ) result = Runner.run_sync(agent, "What's the weather today?") print(result.final_output) The only thing that changed is what version of openai is running underneath. This isn't the only breaking change on the horizon. The nest_handoff_history parameter is being renamed in an upcoming 0.14.0 release — a separate change that hasn't shipped yet. If you're using that parameter in handoff configurations, watch the changelog. The openai-agents library moves fast — 0.13.0 through 0.13.2 shipped across four days in late March. If you're depending on it in production, pinning to a specific version and testing upgrades before deploying is worth the five minutes it takes to set up. A dependency audit tool can flag these conflicts before they hit your CI pipeline. If you're running more than three or four AI libraries in the same environment, you'll hit this pattern regularly. [The AI Dev Toolkit includes a dependency-audit prompt set that checks for version conflicts across openai, anthropic, and the major agent frameworks — https://kazdispatch.gumroad.com/l/zqeopc] openai-agents 0.13.2 (March 26) dropped openai v1 support Requires openai>=2.26.0 — no deprecation period Fix: upgrade openai and update any direct v1-style API calls Your openai-agents agent definitions don't change nest_handoff_history rename is a separate 0.14.0 story, not yet shipped