toor/hermes-ui
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove the API relay link and the ESP32 device feature

Browse Source 
Two pieces of upstream promotion came out of this deployment.

The sidebar "apiRelay" tab only opened a registration page on a third-party
site, so it goes with no replacement.

The circuit badge next to Settings was not what it looked like. It opened an
ESP32 device manager: add a device, show LAN status, remote connect/disconnect,
rename, delete, backed by six REST routes and an mcu_devices table. The purchase
button inside that dialog was the promotional part; the rest was real device
management. Since the hardware is out of scope here, the entire feature is
removed rather than just the link that pointed upstream - UI entry, client API,
routes, controller, store, schema, locale strings, and the one GlobalAgentServer
method that only existed to answer its status column.

Table creation is dropped but no DROP TABLE was added, so an already-provisioned
database keeps its rows as harmless orphans instead of losing data on upgrade.

DevicesView and the hermes.devices route are untouched: that is LAN device
discovery, a separate feature.

AGENTS.md now records the removal so the badge does not come back.
This commit is contained in:
toor
2026-10-19 01:32:51 +08:00
parent 3c963bb1d9
commit 77b1858163
22 changed files with 49 additions and 1405 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+5 -1
View File
@@ -59,9 +59,13 @@ Use the smallest relevant check while iterating. Before a broad PR, run
- This repo is a reimplementation. A few upstream service addresses are load-bearing
and are deliberately kept, each with a whitelist entry in
`scripts/harness-check.mjs`: the global-agent relay (`api.hermes-studio.ai`), the
OpenRouter referer, and the ESP32 purchase link. Do not "clean them up" as legacy
OpenRouter referer, and the sidebar website link. Do not "clean them up" as legacy
brand text — removing them breaks those features. Do not read the relay address as
project identity: this deployment is not affiliated with the upstream operator.
- The upstream ESP32 / MCU device feature was removed on purpose (no UI entry, no REST
routes, no store, no locale strings). Do not reintroduce it. Its "purchase" affordance
was the only part that merely advertised the upstream site; the rest was real device
management, and the whole thing is gone because the hardware is out of scope here.
- The online-update channel (`runtime-version-manager.ts`) has no default URL. It reads
`HERMES_WEB_UI_VERSION_MANIFEST_URL` / `HERMES_WEB_UI_DOWNLOAD_BASE_URL` /
`HERMES_WEB_UI_GITHUB_REPO` and degrades with a named error when unset. Do not