What this error means

responses.create() hangs indefinitely with GPT-5 models; direct REST API call completes successfully is a OpenAI API failure pattern reported for developers trying to fix sdk hang bug where responses.create() blocks forever with gpt-5 models, while identical requests succeed via raw rest api — requiring migration away from python sdk. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #2725 on openai/openai-python (opened Nov 1, 2025, by pietroperona). The Python SDK hangs on responses.create() with GPT-5 models but raw HTTP works fine. This directly impacts developer productivity and signals deep library bugs. 3 comments, 1 linked PR shows active fix effort.

Common causes

  • GitHub Issue #2725 on openai/openai-python (opened Nov 1, 2025, by pietroperona). The Python SDK hangs on responses.create() with GPT-5 models but raw HTTP works fine. This directly impacts developer productivity and signals deep library bugs. 3 comments, 1 linked PR shows active fix effort.

Quick fixes

  1. Confirm the exact error signature matches responses.create() hangs indefinitely with GPT-5 models; direct REST API call completes successfully.
  2. Check the OpenAI API account, local tool state, and provider configuration involved in the failing workflow.
  3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.