Hermes Connector support
Current public Chrome Web Store release: 0.2.4
Match the companion to the extension version shown by Chrome
The Store now serves 0.2.4. Check chrome://extensions, then install companion 0.2.4 when Chrome shows Hermes Connector 0.2.4. Never mix extension and companion versions.
Hermes Desktop compatibility is publicly available
Version 0.2.4 adds automatic discovery of Hermes Desktop's dynamic local backend. After the matching companion is installed and Hermes Desktop is fully restarted, choose the Desktop session and attach tabs in Chrome, then continue the conversation in Hermes Desktop. A separately opened web dashboard is not required.
Chrome updates can roll out gradually. Use companion 0.2.4 only when chrome://extensions explicitly shows Hermes Connector 0.2.4; otherwise keep the companion matching the version Chrome still shows.
Extension and companion compatibility
Open chrome://extensions, find Hermes Connector, and read the installed version before downloading a companion. Use only the companion from the same row.
| Chrome extension | Matching companion | Protocol / default port | When to use |
|---|---|---|---|
| 0.2.4 · current public Store build | Companion 0.2.4 | Protocol 5127.0.0.1:8767Automatic Hermes Desktop backend discovery |
Current release. Install when Chrome explicitly shows extension 0.2.4. |
| 0.2.3 · legacy released build | Companion 0.2.3 | Protocol 4127.0.0.1:8766 |
Only while Chrome still explicitly shows extension 0.2.3. |
| 0.2.2 · legacy released build | Companion 0.2.2 | Protocol 4127.0.0.1:8766 |
Only while Chrome explicitly still shows extension 0.2.2. |
| 0.2.1 · legacy released/sideloaded build | Companion 0.2.1 | Protocol 4127.0.0.1:8766 |
Only when Chrome explicitly shows extension 0.2.1. Upgrade to the latest Store version when possible. |
| 0.2.0 · legacy build | Companion 0.2.0 | Protocol 3127.0.0.1:8765 |
Only while Chrome still shows extension 0.2.0. Follow the disk-recovery notice below. |
Do not mix versions. A newer companion is not a compatible upgrade by itself. Update the extension first, then install the companion with exactly the same version.
Install and pair the matching version
- Install Hermes Connector from the Chrome Web Store and read its version in
chrome://extensions. - Download and extract the companion from the matching row above.
- On Windows, double-click
Install Hermes Connector.cmd, or run.\install.ps1in PowerShell. On macOS/Linux, run./install.sh. - Fully quit and reopen Hermes Desktop, or restart every running Hermes dashboard, gateway, and chat process. Re-run the installer after creating a new named Hermes profile.
- Open the Chrome side panel, paste the private pairing code printed locally, choose the exact Hermes profile/session, and attach only the tabs it may control.
Upgrading to 0.2.4
- Confirm that
chrome://extensionsshows Hermes Connector 0.2.4. If it still shows 0.2.3, keep companion 0.2.3. - Install companion 0.2.4 from the matching row above.
- The installer safely retires the verified older broker on port
8766. Fully quit Hermes Desktop and any Hermes CLI process, then reopen Desktop or restart the CLI. The updated plugin announces Desktop's dynamic loopback backend to the version-checked protocol 5 broker on port8767. - Open the connector panel, choose the Desktop profile/session, and attach the intended tabs. Continue chatting in Hermes Desktop; there is no dashboard address to configure for the normal Desktop setup.
Your pairing code is normally preserved. If pairing is rejected, rerun the 0.2.4 installer and save the locally displayed code again.
Upgrading to 0.2.3
- Chrome normally updates the Store extension automatically. Confirm the installed version in
chrome://extensions. - When Chrome shows 0.2.3, install companion 0.2.3. If Chrome temporarily still shows 0.2.2, keep companion 0.2.2 until the extension updates.
- Restart every running Hermes process. Default installations migrate from legacy port
8765to protocol 4 on port8766. - If you deliberately configured a custom bridge port, reboot the computer once after installation, or safely stop only the known legacy broker process before restarting Hermes.
Your pairing code is normally preserved by the companion upgrade. If pairing is rejected, rerun the matching installer and save the locally displayed code again.
Version 0.2.0 disk-growth recovery
Version 0.2.0 could repeatedly write extension state and enlarge Chrome's LevelDB journal. Version 0.2.1 and later stop the known repeated writes, but Chrome may not immediately reclaim disk space that was already consumed.
- Upgrade the extension and companion to the latest matching version shown by Chrome.
- Close every Chrome window completely, wait for Chrome processes to exit, and reopen Chrome.
- If the extension's storage remains abnormally large, remove and reinstall Hermes Connector from the Chrome Web Store. This clears this extension's local settings.
- Paste the pairing code again, name the Chrome profile if required, reselect the Hermes session, and reattach the permitted tabs.
Do not manually delete arbitrary files from the Chrome profile. Removing the extension clears its settings, including pairing and tab/session bindings, but does not remove the separately installed Hermes companion.
Troubleshooting
- Companion offline: verify that extension and companion versions match, restart Hermes, and confirm that the matching default port is available:
8767for 0.2.4,8766for 0.2.1/0.2.2/0.2.3, or8765for 0.2.0. - Hermes Desktop unavailable in 0.2.4: fully quit and reopen Hermes Desktop after installing companion 0.2.4. The Desktop backend uses a dynamic loopback port and should be discovered automatically; do not enter that temporary port manually.
- Pairing rejected: rerun the matching companion installer to display the current local pairing code, then save it again in the extension.
- Action refused: select the exact Hermes session and attach a permitted normal web tab. Chrome internal pages and other restricted pages cannot be controlled.
- Wrong tab or stale session: detach the tab, select the intended session, and attach it again. The connector fails closed instead of silently using another active tab.
- Chrome debugging banner: disable Trusted input unless native input events or dialog handling are required.
Contact
Report reproducible defects in the public issue tracker. For privacy or security questions, email hello@corsen.ai.
Hermes Connector is an unofficial community project by Corsen AI. It is not affiliated with or endorsed by Nous Research or Google.