GPT-5.2 - agent mode not working

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

today i’ve been unable to use GPT-5.2 in agent mode, keeps giving me “unable to reach the model provider” error.
the weird part is if i switch to debug or ask mode it works perfectly fine with the same model. it’s only agent mode that’s broken for me.
tried with vpn on and off since there were some amazon/vercel issues in europe today but nothing changed. doesn’t make sense why the same model works in other modes but not agent.

Steps to Reproduce

select gpt 5.2 agent mode and type anything, even on new chats.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.36 (user setup)
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: add Request ID with privacy disabled

Request ID: f396fd9b-8f2b-4d2c-84e7-f391cb0c984a
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:false}

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report with the Request ID.

This is a strange situation - GPT-5.2 works in Debug/Ask but not in Agent mode. A few things to check:

  1. Run Network Diagnostics: Cursor Settings > Network > Run Diagnostics - please share the results

  2. Try enabling “Disable HTTP/2”: App Settings CTRL+, > search for “HTTP/2” > turn on the option

  3. If you are using MCP servers - try temporarily disabling them

  4. Since you mentioned issues with Amazon/Vercel today in Europe - it might be a temporary provider problem. Please try again in an hour or two?

Let me know the diagnostics results.

I disabled mcp servers, and then it worked.
I expected to see the error alert suggest that instead of a generic ERROR_OPENAI, but that’s fine, thanks !

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.