hermes: fall back to sference when hyper is unavailable #12
Loading…
Reference in a new issue
No description provided.
Delete branch "hermes-fallback"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sets
fallback_providersto sference'szai-org/GLM-5.3-Flashso sessions keep running when the hyper subscription is out of credits or failing.How the auto-return works (no cron/checker needed): Hermes fallback is turn-scoped — every new message retries the primary (hyper) first. If hyper is still out of credits, the turn runs on sference; once the subscription renews, the next message naturally succeeds on hyper. Result: 'automatically on hyper again' with zero intervention, and no staleness window from a scheduled checker.
Eval-verified:
containers.hermes.config.services.hermes-agent.settings.fallback_providers=[{model: "zai-org/GLM-5.3-Flash", provider: "sference"}].b77afb3483b3a5efeabcb3a5efeabc47a1e79b1147a1e79b11ab23193bfdab23193bfd4dd5a44530Rebased onto main after #29 landed. The branch's other hunks had already landed separately —
extraPackagesvia #27, theci-deploy-keysops rule via #11 — so the branch was reset onto main and now carries only the still-unique delta: thefallback_providersblock (sference as fallback when hyper is unavailable).Verified:
nix evalof thefreun-devandaputoplevel drvPaths succeeds.4dd5a4453002cd67291b02cd67291bc619002aa7c619002aa7d4af2250a6d4af2250a68609d69ff98609d69ff90c695fd77aView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.