TL;DR

The Ollama provider routing bug may be resolved by verifying the host/baseUrl configuration to ensure it correctly points to the Windows Ollama instance.

Guidance

• Review the host/baseUrl configuration in the ollama provider settings to confirm it matches the expected Windows Ollama endpoint.
• Attempt to switch to the ollama/qwen3.5:27b model again after verifying the configuration to see if the issue persists.
• Check the network connectivity between the WSL2 (Ubuntu 20.04) environment and the Windows host to ensure the Ollama instance is reachable.
• Consider adding error handling or logging to detect and report cases where the provider is unreachable, rather than falling back to a default model.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details.

Notes

The provided information does not specify the exact cause of the issue, so these steps are intended to help diagnose and potentially resolve the problem. Further investigation may be necessary to determine the root cause.

Recommendation

Apply workaround: Verify and correct the host/baseUrl configuration to ensure accurate routing, as this is the most direct step to address the potential misconfiguration.