Hermes Connector (unofficial · by Corsen AI) · last updated 2026-07-20
Hermes Connector lets a Hermes agent running on your computer read and control Chrome tabs that you explicitly attach. Corsen AI does not operate a relay, analytics service, account system, or telemetry endpoint for the extension.
The extension does not read cookies or authentication storage. Password, one-time-code, and payment-field values are redacted from accessibility snapshots. Visible text and screenshots can still contain sensitive information, so attach only tabs you are comfortable sharing with your Hermes configuration.
The extension communicates with the separately installed companion over an authenticated loopback WebSocket (ws://127.0.0.1 or ws://localhost) and loads the user-selected local Hermes dashboard over HTTP loopback. Page data is sent only to that local Hermes installation to perform requested actions. It is not sent to Corsen AI.
What Hermes does next depends on the user's Hermes configuration. A local model can keep processing on-device. If the user configured a remote model or service, Hermes may transmit content to that chosen provider under the provider's terms. Corsen AI does not select or receive that transmission.
Chrome local storage retains the browser identifier, local addresses, pairing preference, and tab bindings until extension data is cleared or the extension is removed. The extension does not persist page snapshots, text, screenshots, or form content. The companion retains its pairing credential and browser-binding preference under the user's Hermes home. Hermes may retain chats or tool results under the user's settings.
Corsen AI does not receive, sell, rent, monetize, or use this data for advertising, profiling, creditworthiness, or unrelated purposes. Corsen AI personnel cannot access locally processed data.
Hermes Connector's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
The companion binds only to loopback. It uses a high-entropy secret with role-bound mutual HMAC authentication; the secret is never sent over the WebSocket. Each Hermes profile/session is routed only to its explicitly attached tabs. An unbound session is rejected rather than sent to another tab.
<all_urls> and scripting: read and act on any web origin the user attaches; Chrome also requires broad host access for a requested visible-tab screenshot.storage: retain local identity, settings, and bindings.sidePanel: provide connector controls and the local Hermes dashboard.alarms: keep the local WebSocket available during an active task.debugger: Chrome does not permit this as an optional permission. The extension attaches it only when the user enables Trusted input, for reliable input and dialogs in the selected tab. Chrome displays its debugging banner while attached.Tabs are inaccessible until the user attaches them to a specific Hermes session. The user can detach a tab, disable Trusted input, clear extension storage, disable the companion plugin, or uninstall the extension at any time.