Settings → Models BYOK fields (OpenAI API Key + Override Base URL) do not accept keyboard input; BYOK cannot be configured

[Nirbhay_Hiwse]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On Windows, the OpenAI API Key and Override OpenAI Base URL input fields in Settings → Models do not accept keyboard input. Clicking the fields shows the cursor, but typing does nothing — no characters appear.

This used to work; after a recent update/reinstall the UI stopped accepting input. Clearing cache, reinstalling, and restarting did not fix it.

Because of this, I cannot configure BYOK (Bring Your Own Key) with a custom OpenAI-compatible endpoint (e.g. Baseten). The Override OpenAI Base URL toggle can be turned ON, but the URL field stays at https://api.openai.com/v1 and cannot be edited.

When I try to use a custom model added under Models (e.g. deepseek-ai/DeepSeek-V4-Flash-0731), chat shows: “AI Model Not Found — Model name is not valid” — likely because BYOK was never applied.

Steps to Reproduce

Open Cursor IDE on Windows (v3.15.13).
Go to Settings (gear icon) → Models.
Scroll to OpenAI API Key.
Click the input field “Enter your OpenAI API Key”.
Type any characters on the keyboard.
Actual: Nothing appears in the field.
Toggle Override OpenAI Base URL ON.
Click the base URL field and try to type
Actual: Field does not accept input;
(Optional) Add a custom model name under Models and select it in chat → “Model name is not valid” error.

Expected Behavior

API Key field should accept pasted/typed text.
Base URL field should accept a custom OpenAI-compatible endpoint when override is ON.
After saving, BYOK requests should route to the custom base URL with the provided API key.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

IDE:
Version: 3.15.13
VSCode Version: 1.128.0
Commit: db56c26fed834fb7fd3e85a82d5acd0b393b9dc0
Date: 2026-08-08
OS: Windows x64

For AI issues: which model did you use?

Custom BYOK model: deepseek-ai/DeepSeek-V4-Flash-0731 via Baseten
Also tried Cursor subscription models — those work when BYOK is not needed.

For AI issues: add Request ID with privacy disabled

Privacy mode ON hai to Request ID nahi milega. Agar post karte waqt privacy band kar sakte ho, ek failed chat se Request ID add kar dena.

Additional Information

Pro Plan user ([email protected]).
Problem is UI-only for typing in Models settings — not a bad API key on the provider side.
Tried: cache clear, full reinstall, reload window — issue persists.
Override OpenAI Base URL toggle works; text inputs do not.
Installed extensions include Kilo Code, CommandCode, AI Key Manager — issue may be unrelated but worth checking for UI overlay conflicts.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the detailed report with screenshots and the version. This is a known issue in 3.15.x. The OpenAI API Key and Override OpenAI Base URL fields in Settings → Models don’t get focus when you click them, even though the toggles next to them work. That matches what you’re seeing.

A workaround that helps:

• Click near the field, or click a nearby element.
• Press Tab to move keyboard focus into the input.
• After that, typing and paste Ctrl+V work. Enter your API key and custom base URL.

As an alternative, you can temporarily roll back to 3.14.27. In that version, the inputs can be edited with the mouse as usual.

About the “Model name is not valid” error on deepseek-ai/DeepSeek-V4-Flash-0731. It’s most likely happening because BYOK didn’t actually save, so the key and base URL never applied. Set up BYOK using the Tab workaround above, and the custom model should start routing to your Baseten endpoint.

We’re tracking this issue, but I can’t share an exact ETA yet. I’ll post here if there’s an update. Let me know if the Tab trick works for you.

[Nirbhay_Hiwse]

Thanks for confirming this is a known 3.15.x issue.

The Tab workaround works for me — I can paste the API key and base URL after pressing Tab to move focus into the field. “Secret saved” appears after entering the key.

However, clicking the input still does not focus it, so every time I need to change the key or URL I have to use Tab navigation. This is much slower than normal click-and-type and easy to miss for new users.

I also had a typo in the base URL initially because the field behavior is unclear without focus.

Could you confirm:

1. Will this be fixed in the next 3.15.x patch?
2. Is rolling back to 3.14.27 still the recommended option if I need to edit BYOK settings frequently?

After applying the correct base URL via Tab, I will test the custom model again and report back.

Windows 11, Cursor 3.15.13

[deanrie]

Glad the Tab workaround worked and the key was saved. On your questions:

1. About the next 3.15.x patch, I don’t have an exact timeline yet, and I can’t guarantee it’ll land in the very next release. The issue is known and we’re tracking it. I’ll post an update here as soon as I have one.

2. Yes, if you often need to edit BYOK settings, rolling back to 3.14.27 is a reasonable option. In that version the fields are editable with the mouse as usual. If you only edit it occasionally, you can stay on 3.15.13 and use Tab navigation.

About the initial typo in the base URL, that’s expected. When the field doesn’t show visual focus on click, it’s easy to miss. After using Tab, the field behaves normally, so please double-check the URL after entering it.

Let me know how the custom model test goes after applying the correct base URL. If anything doesn’t work, tell me.

[deanrie]

@Nirbhay_Hiwse, quick update on your request.

The fix for the OpenAI API Key and Override Base URL fields not getting focus on mouse click is already done and will ship in one of the next Cursor updates (a version newer than your current 3.15.13). After you update, clicking the field will focus it like normal again, and the Tab workaround won’t be needed. I can’t share an exact date or version number yet.

On your questions:

1. Yes, the fix is on the way, but I can’t promise it’ll be in the very next 3.15.x patch. Once it’s in a public release, I’ll reply here.
2. If you edit BYOK settings often, rolling back to 3.14.27 is still a solid option until the update. If you rarely change them, you can stay on 3.15.13 and use Tab.

Let me know how the custom model works after you apply the correct base URL.