--- title: Nous Portal Refresh Token Invalid — Context Summaries Unavailable type: incident status: open created: 2026-10-26 updated: 2026-11-11 verified_on: 2026-11-11 review_after: 2026-12-11 confidence: high tags: [hermes, router, memory, incident, unresolved] sources: [gateway-log, live-config, live-probe] --- # Nous Portal Refresh Token Invalid — Context Summaries Unavailable (2026-10-22 →) `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 **eight** `auxiliary:` 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. > **Re-verified 2026-11-11 — the refresh-token failure is gone from the logs, and the exposure has > changed shape rather than closed.** > > - **Zero `invalid_grant` / refresh-token lines** now appear in `~/.hermes/logs/errors.log` (which > covers the window through 2026-11-10 19:19) — so the credential is no longer failing at *auth*. > `~/.hermes/.env` carries no `NOUS_API_KEY`; `~/.hermes/auth.json` is present and live. > - What appears instead is **404 `insufficient_credits_for_paid_model`** for > `anthropic/claude-haiku-4.5` — 3 occurrences, most recent **2026-11-10 19:19:33**, from session > `20261031_190813_95fbde`. > - **A ninth auxiliary slot now points back at `nous`.** The 2026-10-25 remediation moved all > *eight* slots off `nous` onto `custom:omni-101` / `no-think/freeapi/auto`, but > `auxiliary.pulse_memory` (`provider: nous`, `model: anthropic/claude-haiku-4.5`) was added > afterwards and **is** the slot producing those 404s. So the masking is intact for the original > eight slots but a new, single-slot nous dependency exists and is **failing on credits**, not on > auth. > - `nous` is **still the first entry** in `fallback_providers` > (`meituan/longcat-2.5-preview:free`) — that is a *free* model and has not been observed failing, > so the failover risk described below is now "may burn an attempt", not "guaranteed dead". > > **Revised open item:** decide whether `auxiliary.pulse_memory` should be moved onto > `custom:omni-101` like the other eight slots (it is the only active nous path left, and it is > currently erroring), and/or add credits for paid nous models. The original re-authenticate item > is **superseded** — auth works now. ## Related - [[systems/model-providers]] - [[systems/current-profile]] - [[systems/hermes-agent]]