- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13) - skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299) - runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated - comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest - incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised - incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused) - 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists) - log.md addendum + index.md date bump; no page deleted, no secrets written
2.3 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OpenRouter | system | active | 2026-07-22 | 2026-11-11 | 2026-11-11 | medium |
|
|
OpenRouter
Purpose
Fallback model provider.
Location
Remote service; API token store.
Current configuration
Primary key, fallback models, rate limits.
Current state as of 2026-07-22
OpenRouter is not configured as a standalone provider in ~/.hermes/config.yaml custom_providers.
OmniRoute’s catalog includes provider names and model IDs consistent with OpenRouter-style slugs, but live routing via OpenRouter directly is not present in current Hermes config.
Re-verified 2026-10-20 — the claim above still holds.
custom_providersin/home/hermes/.hermes/config.yamlis a list of exactly five entries:litellm,guacano,Omniroute:20128,command-code,omni-101. There is noopenrouterentry. OpenRouter-style slugs (openrouter/auto,freeapi/openrouterfree,kilo-openrouter-auto,or-openrouter-fusion, and many more) exist only inside the OmniRoute model catalog, not as directly-routable Hermes providers. Routing to OpenRouter therefore still goes through OmniRoute, exactly as recorded here.
Re-verified 2026-11-11.
custom_providersin/home/hermes/.hermes/config.yamlstill holds exactly five entries —litellm,guacano,Omniroute:20128,command-code,omni-101— with noopenrouterentry. The 2026-10-20 claim holds unchanged 22 days on.
History
- User-provided: Previously used; now largely replaced by LiteLLM and OmniRoute paths
- Verified: Decision page
keep-openrouter-as-fallbackexists, indicating retain intent - Inferred: Multiple backups before model/routing changes imply OpenRouter role changed during prior config iterations
- Unknown: Exact date OpenRouter was replaced or partially deprecated; exact models that were available
Connected systems
Known issues
- Replaced: legacy Hermes autos not persistent, prompting Hermes Agent, which blocks attribution.
Change history
- Pre-2026-07-20: OpenRouter provisioning active in some form
- 2026-07-20: Prior model-fix backup suggests routing changes around this time