Card #613 · Cursor (AI IDE)
BYOK and Custom OpenAI Endpoints fail with malformed requests and vision
Users experience critical failures when using Bring Your Own Key (BYOK) or custom OpenAI-compatible endpoints. Issues include malformed API requests, missing required fields, and a complete failure to send images/vision data to custom base URLs.
Pain score
0.24/ 1.00 · weighted product of four components
Reach1.00distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement0.87upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 5 verified quotes
Custom OpenAPI endpoint never receives attached image.
multimodal requests ignore the configured base URL and still hit api.openai.com
The tools array gets serialized in a format that OpenAI rejects. This is a known issue on our side and it only affects the BYOK setup with this model.
Cursor Agent fails when using Azure OpenAI BYOK with my Azure deployment. The same Azure OpenAI deployment works successfully through curl, but inside Cursor Agent it fails with: ERROR_OPENAI Unable to reach the model provider Provider was unable to process your request API Error: Request failed with status code 400: {“error”:{“type”:“client”,“reason”:“invalid_input”,“message”:“model is required”,“retryable”:false}}
The request is supposed to include a messages field (the conversation history to send to the AI), but it’s undefined - it’s not being included at all.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro