Ollama Cloud usage is at 100% so ollama-cloud/* agents fail. Move
pm, junior, senior, qa to xai-oc (grok-4.5 / grok-4.3). leave intern on
local ollama/ornith:35b; lead/ops already on xAI.
hermes
changed title from Route agents to xAI while Ollama Cloud quota is exhausted to feat(agents): automatic Ollama Cloud → xAI fallback2026-07-30 15:28:31 +02:00
Keep ollama-cloud/* as primary. Each agent may declare fallback in
agents.json (xai-oc/grok-*). On quota/auth/provider failure, run-agent
switches once to the fallback and continues retries.
- agents.json: fallback fields for pm/junior/senior/qa/intern
- route.sh: emit fallback to GITHUB_OUTPUT
- agent.yml: pass FALLBACK env into run-agent
- install-opencode.sh: register primary+fallback models in provider maps
- run-agent.sh: failover on quota/credit/429/capacity-class errors
hermes
merged commit 58db2996ad into main2026-07-30 15:28:45 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
Ollama Cloud hits 100% usage and agents die. Better than hard-switching: try primary, fall back automatically.
How
agents.jsonkeeps Ollama Cloud as primary and adds:run-agent.shon quota/credit/429/capacity-class errors:install-opencode.shregisters both primary and fallback models in provider maps so opencode can resolve either.Matrix
Needs existing
XAI_API_KEYActions secret.After merge
Re-@pm stuck issues (e.g. homelab #221).
Route agents to xAI while Ollama Cloud quota is exhaustedto feat(agents): automatic Ollama Cloud → xAI fallback