Ollama does not use apikey when using custom url

[ItsOnlyBinary]

App Version

3.28.0

API Provider

Ollama

Model Used

N/A

Roo Code Task Links (Optional)

No response

🔁 Steps to Reproduce

Open settings.
Point your Ollama Base URL to a request catcher instance.
Set an Ollama API Key.
Save -> Done.
Reopen settings.

💥 Outcome Summary

In the request catcher instance you will see GET requests for /api/tags without an Authorization header.

If the UI accepts an API Key it should be used in the requests.

📄 Relevant Logs or Errors (Optional)

[roomote]

I'm exploring a potential fix for this issue where the Ollama API key is not being included in the Authorization header when using a custom URL. I'll open a PR to share progress.

[roomote]

I've opened PR #7903 with a fix for this issue: #7903

The fix ensures that when an Ollama API key is configured, it's properly included in the Authorization header for all API requests to /api/tags and /api/show endpoints. This enables authentication with Ollama cloud or other authenticated Ollama instances.

The implementation includes:

• Updated type definitions to support optional API key
• Modified the getOllamaModels function to include Authorization headers
• Updated all callers to pass the API key when available
• Added comprehensive test coverage

Feedback welcome!