Skip to content

The agent that grows with you

catalog: update Hermes Fleet Connector to 0.3.0

Tony Simons5b0dfd84e0fa
diff --git a/plugin-catalog/hermes-fleet-connector.yaml b/plugin-catalog/hermes-fleet-connector.yaml
index 265883ebb10..8ddb286a866 100644
--- a/plugin-catalog/hermes-fleet-connector.yaml
+++ b/plugin-catalog/hermes-fleet-connector.yaml
@@ -1,19 +1,20 @@
name: hermes-fleet-connector
title: Hermes Fleet Connector
repo: https://github.com/tony-simons-aiowa/hermes-fleet-connector
-sha: "64dfb9a364c912952214a0996f114430b5d3573d"
-description: "Owner-authorized Telegram pairing for Hermes Fleet through a separate connector service and private HTTPS origin. Phone invitations grant broad fleet:operator access. Disclosure — runs a separate connector service you start yourself, which launches a local `hermes serve` backend and a reverse proxy behind your HTTPS origin; a phone paired via a 120-second QR invitation (requested from your owner Telegram DM) gets broad operator access over the internet, including creating, editing and deleting cron jobs (unattended agent runs), dispatching Kanban tasks and reading media; it opens a private browser window locally to show the QR and keeps a control socket in the system temp directory."
+sha: "e55e62ea183aa2f7731f419fc031dee107237b1b"
+description: "Owner-approved universal phone pairing and bundled read-only Live Operations reporting for selected Hermes profiles. Disclosure — paired phones retain broad fleet:operator access, including cron jobs (unattended runs), Kanban task dispatch and media reads. Runs an explicitly activated background connector/reverse proxy and may launch a local Hermes backend; legacy QR flow opens a private local browser. Keeps an owner-only local control socket, pairing state and shared local snapshots; reads selected profiles' session registries through private read-only imports. Local idle/retirement maintenance is explicit and not exposed to phones. Reporting adds no control power."
maintainer: tony-simons-aiowa
tier: community
category: platform
requires_hermes: ">=0.21.6"
-version: "0.1.5"
+version: "0.3.0"
readme: true
platforms: [linux, macos]
known_issues:
- - "Validated with clean stock Hermes v0.21.6 and v0.22.1, Python 3.14, and plugins.isolation: in_process."
- - "Requires qrencode and a logged-in local GUI session with a private browser window and screen; headless or SSH-only display is refused."
- - "WSL2 to Windows Edge browser paint is experimental; native Windows is unsupported."
+ - "Native platform/auth-provider operation requires plugins.isolation: in_process; host-isolated and mixed/multiplexed reporting contexts fail closed. Isolation is never downgraded."
+ - "macOS local acceptance includes existing phone pairing continuity and nine healthy idle reporting processes; Linux and other runtime/OS results are separate CI evidence. Active agent/delegation acceptance is not claimed."
+ - "Private read-only Hermes registry imports can break on future releases. Validator retains a service caution and private-import warnings; no core runtime override is detected."
+ - "Trusted HTTPS origin reachable from host and phone is required. Legacy QR display additionally requires qrencode and an authenticated GUI/browser; terminal approval-code pairing does not require Telegram. Native Windows is unsupported; WSL browser display is experimental."
capabilities:
provides_tools: []
provides_hooks: []