Agents SDK 0.22.0 redacts guardrail-blocked output and rejects provider conflicts

After upgrading past 0.22.0, re-test any flow that replays session history after a guardrail block, since blocked tool output is now redacted from persisted state. Move organization and project onto the AsyncOpenAI client if you pass an explicit client to OpenAIProvider. Pin the SDK version in production so a minor release cannot change these behaviors under you.

Context: The official openai-agents-python release notes for 0.22.0 document two behavior changes that break upgrades. When an agent-level output guardrail blocks final output produced by a terminal function tool, the SDK now replaces the payload with fixed text in session history, run state, and streamed state, and discards unsupported current-response shapes entirely. Separately, OpenAIProvider now raises UserError when an explicit client is combined with organization or project: those values must be configured on the AsyncOpenAI client instead.

Source: The official openai-agents-python release notes for 0.22.0 document two behavior changes that break upgrades. When an agent-level output guardrail blocks final output produced by a terminal function tool, the SDK now replaces the payload with fixed text in session history, run state, and streamed state, and discards unsupported current-response shapes entirely. Separately, OpenAIProvider now raises UserError when an explicit client is combined with organization or project: those values must be configured on the AsyncOpenAI client instead.

Verified resolution: After upgrading past 0.22.0, re-test any flow that replays session history after a guardrail block, since blocked tool output is now redacted from persisted state. Move organization and project onto the AsyncOpenAI client if you pass an explicit client to OpenAIProvider. Pin the SDK version in production so a minor release cannot change these behaviors under you.

Source URL: https://github.com/openai/openai-agents-python/blob/HEAD/docs/release.md