Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When using a custom model configured via OpenAI base URL override (in my case, Ollama running locally), the model works correctly in the main agent pane. However, subagents cannot use it.
Two failure modes observed:
Custom model selected in subagent config is silently ignored. The model appears in the UI and can be selected, but the Task tool’s model enum is hardcoded to [“fast”] — so the value is never passed through.
Attempting to override an existing model ID (e.g. gpt-4o-mini) as a workaround throws an error every time.
The subagent spawning path does not appear to propagate the custom base URL or custom model registry at all — the main agent and subagents are running in entirely different routing contexts.
Steps to Reproduce
Set a custom OpenAI API key + base URL override pointing to Ollama
Add a custom model name (e.g. llama3.2) via the model settings
Confirm it works in the main agent pane 
Configure a subagent to use that custom model
Trigger the subagent — it does not use the custom model 
Expected Behavior
Custom models configured via base URL override should be accessible to subagents, the same as they are to the main agent.
Operating System
MacOS
Version Information
IDE: 3.2.11
For AI issues: which model did you use?
Custom
For AI issues: add Request ID with privacy disabled
Request ID: 73c0f752-7b51-4741-9352-4bcbdab72c96
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:"Provider returned error: ",“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error Provider returned error:
Cvs: Provider Error Provider returned error:
at Pf_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29432:24260)
at Rf_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29432:23144)
at Uf_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29433:6490)
at q0h.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29433:11307)
at async cQi.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41748:12418)
at async Vnm.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41816:12344)
at async Vnm.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41816:19567)
at async lCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async Va (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:40804:4230)
Does this stop you from using Cursor
No - Cursor works, but with this issue