Hermes Connector 0.2.6

Hermes Connector 0.2.6 — companion session service + security fixes

Install companion 0.2.6 only when chrome://extensions shows Hermes Connector 0.2.6. Extension and
companion must always share the same version.

0.2.6 supersedes the v0.2.5 prerelease, which was never submitted to the Chrome Web Store: 0.2.5
was built before the fixes listed below and did not contain them.

Why this release

Hermes releases from October 2026 serve Hermes Desktop through one shared local gateway that no
longer exposes the per-profile backend 0.2.4 discovered, and that never publishes the dashboard
session token. With 0.2.4 the side panel therefore showed “Hermes dashboard unavailable” (and
Chrome's “127.0.0.1 refused to connect” page) unless a separate hermes dashboard was running.

What changes

• Session list through the companion. The side panel asks a connected companion for your
  Hermes sessions over the same authenticated loopback connection it already uses for browser
  actions. Works with Hermes Desktop or the Hermes CLI, with or without a web dashboard.
• Only what the panel needs leaves Hermes: session id, profile, title, display name, source,
  last activity and active flag — never working directories, costs or message content.
• Web-dashboard mode unchanged: when hermes dashboard runs, the embedded dashboard still
  appears in the panel and is no longer reloaded on every 15-second refresh or after a temporary
  failure. The legacy Desktop headless-backend mode is kept for older Hermes releases.
• Honest status: when nothing answers, the panel says what to start instead of rendering a
  connection error page.
• Security and robustness fixes first published on main after 0.2.4 (#9, #10, #12, #13):
  pairing is accepted only on the broker's literal success value, wait delays are validated and
  bounded, key targets are validated and authorization is rechecked before every key action,
  and accessibility snapshots escape backslashes in element names.
• Broker protocol stays 5 on port 8767; new message kinds are additive and bounded (timeout,
  per-browser cap, answers accepted only from the companion that was asked). No new permission.

Upgrade

1. Chrome updates the extension automatically; confirm 0.2.6 in chrome://extensions.
2. Download hermes-connector-0.2.6-companion.zip below and run the installer
   (Install Hermes Connector.cmd on Windows, ./install.sh on macOS/Linux). It updates every
   existing Hermes profile; rerun it after creating a new profile.
3. Fully quit and reopen Hermes Desktop (or restart your Hermes CLI/gateway).

Verification

Fast release gate (114 Python + 77 JavaScript tests, including the security regression suites),
Chromium acceptance (16 checks incl. the three session-source scenarios), snapshot-escaping
acceptance through a real broker and extension, POSIX installer exercise, and packaged-pair
acceptance on these exact archives. Details: docs/TEST-EVIDENCE.md.

Artifacts

File	SHA-256
hermes-connector-0.2.6-chrome.zip	08e2645a409523ea6c037ce0d4633988c8efbf3a9c2702e828ec18d36eb414b5
hermes-connector-0.2.6-companion.zip	80fc7bc42e9f7e5d9a02c81f79b3f132b08fc29db47d167db365df3bbc36aeb6
release-0.2.6.json	release manifest (source commit, sizes, hashes)

Hermes Connector 0.2.5 (superseded by 0.2.6)

Superseded by 0.2.6 — do not install. This prerelease was built before the security fixes published on main after 0.2.4 and was never submitted to the Chrome Web Store. Use 0.2.6.

Hermes Connector 0.2.5 — companion session service

Install companion 0.2.5 only when chrome://extensions shows Hermes Connector 0.2.5. Extension and
companion must always share the same version.

Why this release

Hermes releases from October 2026 serve Hermes Desktop through one shared local gateway that no
longer exposes the per-profile backend 0.2.4 discovered, and that never publishes the dashboard
session token. With 0.2.4 the side panel therefore showed “Hermes dashboard unavailable” (and
Chrome's “127.0.0.1 refused to connect” page) unless a separate hermes dashboard was running.

What changes

• Session list through the companion. The side panel asks a connected companion for your
  Hermes sessions over the same authenticated loopback connection it already uses for browser
  actions. Works with Hermes Desktop or the Hermes CLI, with or without a web dashboard.
• Only what the panel needs leaves Hermes: session id, profile, title, display name, source,
  last activity and active flag — never working directories, costs or message content.
• Web-dashboard mode unchanged: when hermes dashboard runs, the embedded dashboard still
  appears in the panel. The legacy Desktop headless-backend mode is kept for older Hermes releases.
• Honest status: when nothing answers, the panel says what to start instead of rendering a
  connection error page.
• Broker protocol stays 5 on port 8767; new message kinds are additive and bounded (timeout,
  per-browser cap, answers accepted only from the companion that was asked).

Upgrade

1. Chrome updates the extension automatically; confirm 0.2.5 in chrome://extensions.
2. Download hermes-connector-0.2.5-companion.zip below and run the installer
   (Install Hermes Connector.cmd on Windows, ./install.sh on macOS/Linux). It updates every
   existing Hermes profile; rerun it after creating a new profile.
3. Fully quit and reopen Hermes Desktop (or restart your Hermes CLI/gateway).

Verification

Fast release gate, 94 Python + 27 JavaScript tests, Chromium acceptance (16 checks incl. the three
discovery scenarios), packaged-pair acceptance, and three green real-Hermes runs
(sessionListVia: companion). Details: docs/TEST-EVIDENCE.md.

Artifacts

File	SHA-256
hermes-connector-0.2.5-chrome.zip	047cfd24a76766c6ceaedb58d72a4b5b2544667f9ac0411f76b34ac3649a7f07
hermes-connector-0.2.5-companion.zip	5779f58a8265cd11f7bd46b0e2855569bffde2d071c81002b44c0187ec944e93
release-0.2.5.json	release manifest (source commit, sizes, hashes)

Hermes Connector 0.2.4

Hermes Connector 0.2.4 adds first-class support for both Hermes Desktop and Hermes CLI.

Highlights

• Discovers live Hermes Desktop backends on their dynamic loopback ports.
• Keeps the existing CLI and multi-profile routing paths fully supported.
• Moves the local bridge to protocol 5 on 127.0.0.1:8767 with strict extension/companion version checks.
• Prevents the Connector broker from locking Hermes' replaceable virtual environment during Desktop or CLI updates.
• Migrates validated protocol-4 local bindings once and removes only exact legacy Connector brokers.
• Improves first-run setup, companion detection, update guidance, site-access guidance, privacy disclosures, screenshots, and support documentation.

Upgrade

Chrome will update the extension automatically after version 0.2.4 is approved and published in the Chrome Web Store. The matching companion must also be installed again from hermes-connector-0.2.4-companion.zip, then Hermes Desktop/CLI processes must be restarted. Standard installations migrate from port 8766 to 8767 automatically; explicitly configured custom ports remain unchanged.

Verification

• Chrome ZIP SHA-256: 335b35a7531722e58a84054ba102dceda9672699c7d60fc859f7d4c3bd072967
• Companion ZIP SHA-256: 3ec1c1c0428441d5f98fd9458bb099808dbb7b39ab9d34dea2dc5ecc29ff5cae
• Release commit: 2c0cb7e40705638726e38db0385fa52237ce68f5

Validated on Windows, Ubuntu, and macOS; the exact packaged Chrome ZIP also passed live Hermes Desktop 0.21.0 acceptance on Windows.

Hermes Connector 0.2.3

Hermes Connector 0.2.3 fixes Windows companion startup and routing compatibility, strengthens installer version checks, and tightens release validation.

Chrome Web Store rollout: 0.2.3 is now live on the existing Store listing. Keep the Chrome extension and local companion on exactly the same version; install companion 0.2.3 after chrome://extensions shows Hermes Connector 0.2.3.

Official links:

• Chrome Web Store: https://chromewebstore.google.com/detail/hermes-connector-%E2%80%94-by-cor/cdhaldcgafmkcnpanlmmpaebabnlledm
• Setup, downloads, and compatibility: https://corsenai.github.io/hermes-connector/
• Support and upgrade guide: https://corsenai.github.io/hermes-connector/support/
• Complete installation and live browser-control demo: https://youtu.be/4akSq9cMmFw
• Corsen AI official website: https://corsen.ai/

Verified release evidence:

• source commit: 4225197
• protocol 4, loopback port 8766
• 64 Python checks (58 passed, 6 expected platform/privilege skips) + 19 JavaScript tests
• Windows, macOS, Ubuntu, real Chrome, multi-browser, and exact packaged-pair acceptance passed
• chrome ZIP SHA-256: 039d0b569f623a70e8c1f180a3372595d7f733d3160bc195dc1c52864edfc3e7
• companion ZIP SHA-256: 32fbae02a31874af223cdd06bcce7e02443fa366a0327cc06419aec6db9f55f6

Hermes Connector 0.2.2

Hermes Connector 0.2.2 fixes exact-session browser routing, compact tab controls, first-run installation guidance, reconnect safety, and protocol authentication hardening.

Important rollout note: Chrome Web Store approval is separate. Existing Store users remain on 0.2.0 until Google publishes 0.2.2, then Chrome updates them automatically. Re-run the 0.2.2 companion installer once after the extension update. Do not pair Store extension 0.2.0 with this protocol-4 companion.

Verified release evidence:

• source commit: b9805ec
• protocol 4, loopback port 8766
• 61 Python tests + 19 JavaScript tests
• real Chrome, multi-profile, and exact packaged-pair E2E passed
• chrome ZIP SHA-256: bb321fe897394043ffd8fdd424e7ca373e27429bb10bf743328e68a2e285c2a1
• companion ZIP SHA-256: 597e9f724abf3916fdb778e71b23341d67e021a5a0220429d8fbedccf2baa2c6

Hermes Connector 0.2.1

Hermes Connector connects local Hermes profiles and sessions only to the Chrome tabs the user explicitly selects.

Important upgrade step

Chrome Web Store users receive the extension update automatically. If you used version 0.2.0, reinstall the 0.2.1 companion once because this release uses security protocol 4, then restart Hermes.

1. Download and extract hermes-connector-0.2.1-companion.zip.
2. On Windows, double-click Install Hermes Connector.cmd. On macOS/Linux, run ./install.sh.
3. Restart any running Hermes process.
4. Open the extension, enter the pairing code shown by the installer, select a Hermes session, and attach only the tabs you want Hermes to control.

What is new

• Guided first-run setup that detects Windows, macOS, Linux, an existing companion, reinstalls, and additional Chrome profiles.
• Protocol 4 mutual authentication over the loopback interface; the pairing secret is never sent over the wire.
• Exact session-to-tab routing with fail-closed behavior for stale, unbound, or transferred sessions.
• Concurrent isolated Chrome profiles with explicit session transfer.
• Hardened atomic installers and broker state handling.
• Full packaged-browser acceptance on Windows and Ubuntu, plus cross-platform release gates on macOS.

No browsing data, page content, credentials, or telemetry is sent to Corsen AI. Browser actions stay between the local extension and local Hermes installation.

SHA-256

• Chrome Web Store archive: 292508104f2967b23de7e33284014ac0d949c2bdf5999af5c9345aa1f6cb4420
• Companion archive: ae1f4dab8b613c4c2eb1cfd7c17aa2318553f2cdaa8ae9b213cadf16a5667121

Unofficial community project by Corsen AI. Not affiliated with or endorsed by Nous Research or Google.

Hermes Connector 0.2.0

Hermes Connector attaches exact local Hermes profiles and sessions to only the Chrome tabs a user explicitly selects.

Install

1. Download and extract hermes-connector-0.2.0-companion.zip.
2. Run install.ps1 on Windows or install.sh on macOS/Linux.
3. Restart running Hermes processes.
4. Install the matching Chrome extension, paste the pairing code printed locally, select a Hermes session, and attach its permitted tabs.

The -chrome.zip file is the exact Chrome Web Store submission artifact. The companion and extension both use protocol 3.

SHA-256

• Chrome: 06c42c6a98590523b2467074cddaeedb7c62010a799244596ebbc74a40428365
• Companion: bc6286dae03a8343885fea86672cce86578cc7970551d254552afcfddb3f43c5

Unofficial community project by Corsen AI. Not affiliated with or endorsed by Nous Research or Google.