Provider Error / "trouble finding the resource" when attaching images with BYOK Override OpenAI Base URL

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Related to Provider Error - Trouble Finding Resource (appears closed/stale) — reporting a fresh occurrence with a different trigger: attaching a screenshot/image to a chat message while “Override OpenAI Base URL” + a custom OpenAI-compatible API key (BYOK) are enabled. Text-only messages work fine against the same custom endpoint; the moment an image is attached, the request fails almost immediately with:

Provider Error: We’re having trouble finding the resource you requested. If the problem persists, please contact support.

Locally, Cursor’s own request trace logs (cursor.requestTraces.log) show the failing request completes gatherImageSelections (image successfully attached) and then errors inside the rpc.run span to Cursor’s backend in ~1.8s — consistent with a fast-fail rejection rather than a real timeout/connectivity problem with our endpoint. This matches the pattern other users have described where BYOK + Override Base URL requests carrying an image get intercepted/validated differently on Cursor’s backend than plain text requests, instead of being routed through the configured custom base URL end-to-end.

Steps to Reproduce

  1. Settings → Models → API Keys: enable OpenAI API Key (custom key) + Override OpenAI Base URL pointing at a custom OpenAI-compatible endpoint
  2. Start a chat, send a text-only message → works
  3. Attach a screenshot/image to a chat message, send → fails with Provider Error

Expected Behavior

Image-attached requests should route through the same custom base URL as text requests, or fail with a specific, accurate error if the configured model/endpoint doesn’t support vision — not a generic “resource not found” after appearing to succeed locally.

Screenshots / Screen Recordings

Screenshot from 2026-08-12 16-13-26.png
Screenshot from 2026-08-12 16-13-26.png1311×788 41.7 KB

Operating System

Linux

Version Information

Version: 3.15.6
VSCode Version: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Build Type: Stable

For AI issues: add Request ID with privacy disabled

1cc98993-363f-4cb1-98b9-4a528d277d7a

Additional Information

Cursor works, but this blocks screenshot/vision workflows against our custom endpoint.

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hi @O1ahmad Thanks for the post! Thanks for the report and the Request ID. In this case, the request did go through to your configured endpoint. The model in that request doesn’t have an image-capable route, so the provider returned a not-found response for the image payload. Text-only messages on the same setup keep working for that reason.

Two things that should help:

  1. For chats with screenshots or images, pick a model on that endpoint that actually supports image input.
  2. You can also use Cursor’s built-in models for those image turns, and keep the custom endpoint for text.

Let me know any follow-up questions!