Bug Description
After configuring the MiniMax provider (the global one, not the China one) in Hermes, with the correct API key (I have a coding plan), running hermes doctor shows me a ⚠ and "(HTTP 404)" next to MiniMax.
Steps to Reproduce
- Run
hermes setup.
- Add MiniMax (the global one, not the China one) as a provider, with a correct MiniMax API key
- Run
hermes doctor
Expected Behavior
I should not see a ⚠ and "(HTTP 404)" next to MiniMax in the output of hermes doctor because the detection is broken.
Actual Behavior
I see an "(HTTP 404)" next to MiniMax in the output of hermes doctor, even though MiniMax actually works in, for instance, an interactive session.
Affected Component
Other
Messaging Platform (if gateway-related)
No response
Operating System
Ubuntu 24.04
Python Version
3.11.11
Hermes Version
vv1.0.0
Relevant Logs / Traceback
◆ API Connectivity
✓ OpenRouter API
⚠ MiniMax (HTTP 404)
Root Cause Analysis (optional)
I checked the hermes-agent source code and this because the doctor module tries to detect whether the provider is functioning by senting an HTTP request to "https://api.minimax.io/v1/models" (
|
("MiniMax", ("MINIMAX_API_KEY",), "https://api.minimax.io/v1/models", "MINIMAX_BASE_URL"), |
), but MiniMax does
not actually support that endpoint, so the doctor module shows HTTP 404.
Proposed Fix (optional)
We need a different way to detect the correct configuration of MiniMax, or not detect at all, if there is no way to do it without wasting token quota.
Maybe just say that we see an API key configured and not mark it with a ⚠.
Are you willing to submit a PR for this?
Bug Description
After configuring the MiniMax provider (the global one, not the China one) in Hermes, with the correct API key (I have a coding plan), running
hermes doctorshows me a ⚠ and "(HTTP 404)" next to MiniMax.Steps to Reproduce
hermes setup.hermes doctorExpected Behavior
I should not see a ⚠ and "(HTTP 404)" next to MiniMax in the output of
hermes doctorbecause the detection is broken.Actual Behavior
I see an "(HTTP 404)" next to MiniMax in the output of
hermes doctor, even though MiniMax actually works in, for instance, an interactive session.Affected Component
Other
Messaging Platform (if gateway-related)
No response
Operating System
Ubuntu 24.04
Python Version
3.11.11
Hermes Version
vv1.0.0
Relevant Logs / Traceback
Root Cause Analysis (optional)
I checked the hermes-agent source code and this because the doctor module tries to detect whether the provider is functioning by senting an HTTP request to "https://api.minimax.io/v1/models" (
hermes-agent/hermes_cli/doctor.py
Line 496 in 36328a9
Proposed Fix (optional)
We need a different way to detect the correct configuration of MiniMax, or not detect at all, if there is no way to do it without wasting token quota.
Maybe just say that we see an API key configured and not mark it with a ⚠.
Are you willing to submit a PR for this?