From 1006d4490abbbfad4110c6e1b6cd59850108c12f Mon Sep 17 00:00:00 2001 From: jenstandstad Date: Sat, 2 May 2026 19:04:36 +0200 Subject: [PATCH] Clear Hermes session cache on token rejection retry When the dashboard token is rejected and re-fetched, the stale session_id was being reused, causing prompt.submit to go to a non-existent session. Now clears both caches so the retry creates a fresh session. Co-Authored-By: Claude Sonnet 4.6 --- server.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/server.py b/server.py index 94bd9c3..4592ba0 100644 --- a/server.py +++ b/server.py @@ -511,6 +511,9 @@ async def handle_hermes( if "401" in err_str or "403" in err_str or "Unauthorized" in err_str.lower(): log.warning(f"[{agent.name}] Hermes token rejected, re-fetching…") _hermes_token_cache.pop(endpoint, None) + if req.conversation_id is not None: + _hermes_sessions.pop(req.conversation_id, None) + hermes_session_id = None # force session.create on retry try: token = await _fetch_hermes_token(endpoint) return await _do_chat(token)