Nous Portal runtime credentials unavailable: Invalid refresh token. Run hermes model to re-authenticate.
Occurrences (gateway logs, counted 2026-10-26)
Day
Lines
Notable
2026-10-22
1
11:32:20 tui_gateway.server: llm.oneshot failed
2026-10-24
3
—
2026-10-25
20
last at 14:53:04 — agent.context_compressor: Failed to generate context summary
2026-10-26
0 (to 00:1x)
none since the 19:27:13 restart
Effect
Context compression failed outright. Sessions could not summarise, so working context grew unchecked —
one cron fire reached 148 k tokens on 10-25 and ran 1 h 55 m.
→ incidents/2026-10-25-gmail-digest-runaway-and-refire
Every auxiliary LLM path pointed at nous failed with it.
What changed — and what did not
2026-10-25, config.yaml written 19:13 AWST: all eightauxiliary: slots moved off nous to
no-think/freeapi/auto on custom:omni-101, each with the chain
no-think/freeapi/deepseek-v4-flash → no-think/kg/kilo-auto/free, free_only: true
(compression timeout 90 s, vision timeout 180 s). → systems/model-providers
The credential is still invalid. The fault is masked, not fixed — no hermes model
re-authentication has been run, and nous is still the first entry in fallback_providers.
Zero invalid_grant lines appear after the 2026-10-25 19:27:13 gateway start, so the masking is holding.
Open
Re-authenticate the Nous Portal credential, or remove nous from fallback_providers.
Until then, a failover event will attempt a dead credential silently.