Debug share created: please help me with this thank you :))
Report: https://paste.rs/oc7cN
agent.log: https://paste.rs/FEyqR
gateway.log: https://paste.rs/yQ5Mk
Auto-delete: 6 hours
Delete now: hermes debug delete <url>
#grok not working? i just got the subscription but its failing
glossy oak
shrewd gulch
The Grok OAuth login itself is not what’s failing in these logs. The actual Grok call reaches https://api.x.ai/v1 with grok-4.3, then xAI rejects the request because Hermes is sending 306 to 308 tools and xAI’s limit is 200.
The Grok subscription/OAuth connection is not the failing part in this debug share.
Hermes is reaching xAI directly with:
provider: xai-oauth
model: grok-4.3
endpoint: https://api.x.ai/v1
The provider response is:
HTTP 400: Maximum tools limit reached. 308 tools have been provided but the maximum is 200.
A later attempt shows the same thing with 306 tools. So the immediate issue is that this Hermes session has too many tools enabled for xAI/Grok, not that the new Grok subscription is missing.
The later fallback errors are separate noise after the Grok call already failed:
- Xiaomi fallback hits quota
- Nous fallback returns 403
- Ollama fallback is missing
qwen2.5:7b - opencode/openrouter have their own auth/account issues in the fallback chain
For now, reduce the active tool surface before using Grok. Since this looks like you were trying X/Twitter search, keep x_search enabled and disable broad tool/MCP groups you do not need.
You can do that interactively with:
hermes tools
or start a narrower temporary session with:
hermes --toolsets x_search,web,terminal
Then retry Grok. The important part is keeping the total provided tools under xAI's 200-tool limit.
glossy oak
thank you so much gille!