Qwen3.6 Provider Error: resource not found

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Model: qwen3.6
Request ID: 55dfdedb-4f44-44c7-ab08-52996dd2edc0
Error: Provider Error / resource not found
Repro: each request
Log: Request ID: 55dfdedb-4f44-44c7-ab08-52996dd2edc0
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble finding the resource you requested. If the problem persists, please contact support.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
$Ai: Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
at p9A (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:23670)
at h9A (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22658)
at w9A (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at rau.run (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:10400)
at async GOa.runAgentLoop (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46834:10206)
at async _5u.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46888:9277)
at async _5u.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46888:13663)
at async vMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)
at async Object.Ea [as onSubmit] (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45813:4826)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45787:57069

Steps to Reproduce

Open Cursor IDE
Go to Settings → Models → Add New Model
Configure model:
Provider: OpenRouter
Model: qwen3.6
API Key: OpenRouter key
Override Base URL: OpenRouter endpoint
Save and select qwen3.6 in AI chat
Send any prompt
Observe Provider Error

Expected Behavior

Model should respond normally via OpenRouter without “resource not found” errors

Operating System

Windows 10/11

Version Information

Version: 2.6.21 (system setup)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

qwen3.6 (via OpenRouter)

For AI issues: add Request ID with privacy disabled

55dfdedb-4f44-44c7-ab08-52996dd2edc0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hi Andrei, thanks for the detailed report and request ID. The 404 here is coming from OpenRouter, not Cursor.

No endpoints available matching your guardrail restrictions and data policy.

That means OpenRouter’s router could not find any provider for qwen3.6 that satisfies the data handling rules currently set on your OpenRouter account, so it rejects the call before it reaches a model. Cursor forwarded the request successfully; the refusal is from their side.

To resolve:

  1. Open your OpenRouter privacy settings: https://openrouter.ai/settings/privacy
  2. Review the data policy toggles (training permissions, zero-data-retention, provider allow/deny lists) and adjust them so that at least one qwen3.6 endpoint is permitted under your policy.
  3. Save, then retry the request in Cursor. It should succeed once a matching endpoint exists.

As a heads up:

  • OpenRouter is not an officially supported BYOK provider on our side, so it may not work.
  • Several other users have hit this exact OpenRouter guardrail 404, and adjusting the privacy settings has appeared to resolve it.