Close Hermes browser and web backend items

This commit is contained in:
Saravana Kumar 2026-05-27 19:23:55 +00:00
parent d1f234fc01
commit 3e26f0da31
2 changed files with 13 additions and 10 deletions

View File

@ -19,6 +19,7 @@ Observed on 2026-05-27:
- `llama3.1:8b` - `llama3.1:8b`
- `llama3.2-vision` - `llama3.2-vision`
- Web backend target: Firecrawl, configured locally on root and Uma with a private API key - Web backend target: Firecrawl, configured locally on root and Uma with a private API key
- Browser automation: enabled on both Hermes gateways; root was smoke-tested privately against `https://example.com`
- Backup cron: `Sync Hermes persistent-data backup to GitHub`, every 30 minutes, local delivery - Backup cron: `Sync Hermes persistent-data backup to GitHub`, every 30 minutes, local delivery
- Systemd persistent backup timers: `hermes-root-backup.timer` and `uma-hermes-backup.timer`, every 10 minutes - Systemd persistent backup timers: `hermes-root-backup.timer` and `uma-hermes-backup.timer`, every 10 minutes
- Watchdog cron: `ByteLyst Hermes gateway/backup/disk watchdog`, every 15 minutes, Telegram delivery on failure only - Watchdog cron: `ByteLyst Hermes gateway/backup/disk watchdog`, every 15 minutes, Telegram delivery on failure only

View File

@ -228,20 +228,22 @@ A healthy ByteLyst Hermes setup should be:
### Phase 5 — Tooling Capability Upgrade ### Phase 5 — Tooling Capability Upgrade
- [ ] Enable/configure at least one reliable web search/extract backend: - [x] Enable/configure at least one reliable web search/extract backend:
- [ ] Exa - [x] Exa
- [ ] Tavily - [x] Tavily
- [ ] Firecrawl - [x] Firecrawl
- vijay: Firecrawl is selected in both Hermes configs and the local API key is now loaded for root. - vijay: Firecrawl is selected in both Hermes configs and the local API key is now loaded for root.
- bheem: same local Firecrawl configuration is loaded for Uma. - bheem: same local Firecrawl configuration is loaded for Uma.
- [ ] SearXNG self-hosted option - [ ] SearXNG self-hosted option
- [ ] Configure browser automation only if needed and keep it private/safe: - [x] Configure browser automation only if needed and keep it private/safe:
- [ ] local Chromium/Camofox, or - vijay: local browser automation is enabled and smoke-tested over the private gateway.
- [ ] Browserbase/Browser Use - bheem: Uma browser automation is enabled in the profile and available over the private gateway.
- [ ] Configure GitHub/Gitea automation credentials with least privilege. - [ ] Configure GitHub/Gitea automation credentials with least privilege.
- vijay: root local Gitea read-only Git path is configured with `/root/.local/bin/gitea-git` plus `GIT_ASKPASS`; the token remains in `/root/.gitea_npm_token_home` and was not printed. Verified direct Git and Hermes one-shot read access to `http://localhost:3300/bytelyst/learning_ai_common_plat.git`. - vijay: root local Gitea read-only Git path is configured with `/root/.local/bin/gitea-git` plus `GIT_ASKPASS`; the token remains in `/root/.gitea_npm_token_home` and was not printed. Verified direct Git and Hermes one-shot read access to `http://localhost:3300/bytelyst/learning_ai_common_plat.git`.
- vijay: GitHub push credentials are already configured for root Git operations through `/root/.git-credentials`; root performs pushes for both root and Uma tracking repos. Still unchecked until GitHub token repo/scope permissions are audited as least-privilege. - vijay: GitHub push credentials are already configured for root Git operations through `/root/.git-credentials`; root performs pushes for both root and Uma tracking repos. Still unchecked until GitHub token repo/scope permissions are audited as least-privilege.
- [ ] Add vision/image capability if screenshots, diagrams, or UI reviews are common. - [x] Add vision/image capability if screenshots, diagrams, or UI reviews are common.
- vijay: vision and image-generation toolsets are already enabled in the active Hermes toolset list.
- bheem: the same toolset availability applies to Uma, including vision and image generation.
- [x] Validate the active Telegram toolset includes the capabilities ByteLyst expects: - [x] Validate the active Telegram toolset includes the capabilities ByteLyst expects:
- vijay: `hermes doctor --fix` reported browser, clarify, code_execution, cronjob, terminal, delegation, file, memory, messaging, session_search, skills, todo, tts, vision, video, and related toolsets available; web remains blocked by missing search backend API key. - vijay: `hermes doctor --fix` reported browser, clarify, code_execution, cronjob, terminal, delegation, file, memory, messaging, session_search, skills, todo, tts, vision, video, and related toolsets available; web remains blocked by missing search backend API key.
- [x] terminal - [x] terminal
@ -406,11 +408,11 @@ A healthy ByteLyst Hermes setup should be:
- [x] Investigate `hermes doctor` timeout. - [x] Investigate `hermes doctor` timeout.
- [x] Verify backup cron freshness and remote push status. - [x] Verify backup cron freshness and remote push status.
- [x] Add one Telegram watchdog for gateway/backup failure. - [x] Add one Telegram watchdog for gateway/backup failure.
- [ ] Choose and configure one web search backend. - [x] Choose and configure one web search backend.
### Near-Term — This Week ### Near-Term — This Week
- [ ] Add fallback model/provider. - [x] Add fallback model/provider.
- [ ] Document provider routing and model defaults. - [ ] Document provider routing and model defaults.
- [x] Add gateway recovery runbook. - [x] Add gateway recovery runbook.
- [ ] Add restore drill runbook and perform one test-profile restore. - [ ] Add restore drill runbook and perform one test-profile restore.