After integrating the Open API key, the existing AI becomes unusable

Support Bug Reports
1

20260131_151241
20260131_1512411461×853 46.5 KB

"I purchased the GLM-4.7 model, integrated it with Cursor using the API, and confirmed it works properly.

However, when I activate the Open API Key, the AI models I previously used in Cursor now show errors like ‘We’re having trouble connecting to the model provider’ and cannot be used.

When I deactivate the Open API Key, they become usable again.

Is it normal behavior that after integrating and activating the Open API Key, only the integrated AI can be used and the existing AIs cannot be used?

I have tried restarting Cursor and several other methods, but the issue persists."

Bug Report: After enabling custom models, Gemini models become unavailable
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

Hey @QLXM

Thank you for reaching out! This is a known limitation of the Bring Your Own Key (BYOK) feature. When you override the OpenAI Base URL/Key, this configuration is applied to all model providers. We have identified this as a bug, and I have attached your report to our existing ticket.

In the meantime, you will need to disable these settings before switching to other models that do not route through this URL.

5

@Colin

Please support setting separate URL and key for each custom model while maintaining the availability of using the official models.