diff --git a/docs/hermes-operations.md b/docs/hermes-operations.md
index 1d96e54..19f0bb3 100644
--- a/docs/hermes-operations.md
+++ b/docs/hermes-operations.md
@@ -18,6 +18,7 @@ Observed on 2026-05-27:
   - `qwen2.5-coder:7b`
   - `llama3.1:8b`
   - `llama3.2-vision`
+- Web backend target: Firecrawl, pending API key or self-hosted Firecrawl endpoint
 - 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
 - Watchdog cron: `ByteLyst Hermes gateway/backup/disk watchdog`, every 15 minutes, Telegram delivery on failure only
diff --git a/docs/hermes-setup-upgrade-roadmap.md b/docs/hermes-setup-upgrade-roadmap.md
index c4de081..9fbc0c1 100644
--- a/docs/hermes-setup-upgrade-roadmap.md
+++ b/docs/hermes-setup-upgrade-roadmap.md
@@ -232,6 +232,8 @@ A healthy ByteLyst Hermes setup should be:
   - [ ] Exa
   - [ ] Tavily
   - [ ] Firecrawl
+    - vijay: Firecrawl is selected in both Hermes configs; waiting on API key or a self-hosted endpoint.
+    - bheem: same pending auth state applies to Uma.
   - [ ] SearXNG self-hosted option
 - [ ] Configure browser automation only if needed and keep it private/safe:
   - [ ] local Chromium/Camofox, or