hermes - 💡(How to fix) Fix [Bug]: Explicit local OpenAI-compatible config still resolves back to OpenRouter [1 comments, 2 participants]

Additional Logs / Traceback (optional)

TL;DR

Hermes may not be correctly configured to prioritize the local OpenAI-compatible provider over OpenRouter, leading to unexpected resolution.

Guidance

• Verify that the local OpenAI-compatible endpoint is correctly configured and accessible, ensuring it can handle requests from Hermes.
• Check the Hermes configuration files or environment variables to ensure that the local provider is explicitly set as the primary or default provider.
• Review any relevant documentation for Hermes v0.11.0 to understand how provider priorities are handled, as this might be a version-specific issue.
• Test the local provider directly (outside of Hermes) to confirm it's functioning as expected and can process requests without resolving to OpenRouter.

Example

No code example is provided due to the lack of specific technical details about the configuration or implementation.

Notes

The solution might depend on the specific configuration options available in Hermes v0.11.0 and how it handles provider priorities. Without more detailed logs or a clear understanding of the configuration, it's challenging to provide a precise fix.

Recommendation

Apply workaround: Given the information, the best course of action seems to be to carefully review and adjust the Hermes configuration to ensure it correctly prioritizes the local OpenAI-compatible provider. This approach allows for a targeted fix without assuming the presence of a newer version with the issue resolved.