From 08f32a79e8b2bee8dad020e9df13a68c682d29dd Mon Sep 17 00:00:00 2001 From: root Date: Wed, 27 May 2026 18:46:32 +0000 Subject: [PATCH] Clarify remaining Hermes fallback verification --- docs/hermes-setup-upgrade-roadmap.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/hermes-setup-upgrade-roadmap.md b/docs/hermes-setup-upgrade-roadmap.md index 5e27953..c4de081 100644 --- a/docs/hermes-setup-upgrade-roadmap.md +++ b/docs/hermes-setup-upgrade-roadmap.md @@ -210,20 +210,22 @@ A healthy ByteLyst Hermes setup should be: - [x] Add at least one fallback provider for resilience: - vijay: configured a shared local Ollama fallback chain for both Hermes instances and kept routing disabled on the primary path. - bheem: same shared local Ollama fallback chain configured for Uma. - - local/Ollama is now the active fallback path for low-risk offline tasks. + - local/Ollama fallback is configured and verified with direct model smoke tests. - [x] Configure provider credentials through Hermes auth/config flows; do not commit keys. - vijay: documented the command path; provider additions requiring new credentials remain pending. - [x] Define model routing tiers: - vijay: fast/cheap = `qwen2.5:0.5b` or `llama3.2:1b`, strong coding = `qwen2.5-coder:7b`, general/long-context = `llama3.1:8b`, vision-capable = `llama3.2-vision`. - bheem: same local tier map applies to Uma. - routing remains disabled until a separate routed path is proven safe. -- [x] Test fallback behavior by switching models in a new session. - - vijay: verified the fallback chain is configured and the local models can be pulled and invoked on demand; `gemma4` was rejected by the installed Ollama runtime and was replaced with `llama3.2-vision`. - - bheem: verified the same shared host fallback path is available to Uma. +- [ ] Test fallback behavior by switching models in a new Hermes session. + - vijay: direct Ollama smoke tests passed for `qwen2.5-coder:7b`, `llama3.1:8b`, and `llama3.2-vision`; live Hermes session-switch verification still needs to be done. + - bheem: same live Hermes session-switch verification still needs to be done for Uma. - [x] Document the preferred default model and fallback order. - vijay: current default is OpenAI Codex OAuth; fallback provider order is now the shared local Ollama chain. - vijay: preferred default is explicitly `gpt-5.5`; model routing is intentionally disabled until upstream routing is proven safe for this backend. +- [ ] Verify the root and Uma Telegram gateways can actually switch to the fallback chain in a live conversation without surfacing provider errors. + ### Phase 5 — Tooling Capability Upgrade - [ ] Enable/configure at least one reliable web search/extract backend: