[ENHANCEMENT] When custom url is used in Openrouter, model retrieval and costs are still pointing to the official one #8947
Description
Problem (one or two sentences)
When a custom URL is set in Openrouter, model retrieval and cost calculations still interact with the official Openrouter endpoints instead of the custom one provided.
Context (who is affected and when)
This affects users who need to point Roo Code to a self-hosted, proxy, or third-party Openrouter-compatible endpoint for privacy or cost management, and expect all functionality (model selection + pricing) to be redirected, not just API calls.
Desired behavior (conceptual, not technical)
When a custom URL is configured, all interactions including model retrieval and displaying usage/costs should use the custom endpoint fully, with no fallback or request to the official Openrouter servers.
Constraints / preferences (optional)
Prefer to allow seamless switching with clear communication in the UI about which endpoint is in use. Privacy and cost transparency are essential. Ensure the system never leaks information or queries to the official Openrouter when a custom URL is configured.
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear context and impact
Roo Code Task Links (optional)
No response
Acceptance criteria (optional)
No response
Proposed approach (optional)
No response
Trade-offs / risks (optional)
No response