[Bug] OpenRouter Custom Models Fail with “Quota Exceeded” (402) in Eclipse, While Working in VS Code

[ivanzhao1982]

Environment

• Eclipse IDE: 2025-06
• GitHub Copilot: Latest version from Eclipse Marketplace
• Subscription: GitHub Copilot Pro (Individual)
• Remaining AI Credits: ~1500
• Operating System: Windows 11

Problem Description

GitHub Copilot works correctly in Eclipse when using the built-in Copilot models.

However, when I switch to a custom model provider (OpenRouter), every request fails immediately with:

Quota Exceeded

The Eclipse Error Log shows:

[LS:GitHub Copilot Language Server][Error] [toolCallingLoop] Fetch failed: {
type: 'failed',
reason: 'Quota Exceeded',
requestId: '...',
code: 402,
retryAfter: undefined,
ghRequestId: undefined,
capiErrorCode: undefined
}

Expected Behavior

Requests routed through OpenRouter should use the configured OpenRouter provider and API credentials.

Since:

• My GitHub Copilot Pro subscription is active
• I still have approximately 1500 AI Credits remaining
• The same OpenRouter configuration works correctly in VS Code

I would expect custom model requests in Eclipse to behave the same way.

Actual Behavior

• Built-in Copilot models: ✅ Work correctly
• OpenRouter custom models: ❌ Always fail with HTTP 402 / “Quota Exceeded”
• Chat mode: ❌ Fails
• Agent mode: ❌ Fails
• Same OpenRouter account and model configuration in VS Code: ✅ Works correctly

Additional Notes

This does not appear to be a GitHub Copilot subscription or AI Credits issue because:

1. Built-in Copilot models work normally in Eclipse.
2. The account still has available AI Credits.
3. The exact same OpenRouter configuration works in VS Code.

It seems possible that the Eclipse implementation is performing Copilot quota validation for requests that should instead be routed through the external OpenRouter provider, or that custom provider usage is not being handled consistently with the VS Code implementation.

Could you please confirm whether OpenRouter custom providers are officially supported in Eclipse and whether this behavior is a known issue?

Thank you.