v0.1.5

v0.1.5

Release date: June 27, 2026
Channel log since the initial v0.1.5 tag: 6 follow-up commits · 2 merged PRs · 9 files changed · 1 community contributor

The compatibility + trust release. v0.1.5 makes Hermes Browser Extension clearer about what it can reach, what it sends to Hermes, and how it behaves when a connected Hermes runtime does not expose every optional browser-facing route. The initial release added capability-aware UI, safer context receipts, voice/gateway fallbacks, and public security docs. Follow-up channel updates tightened the DOM context chip and added contributor-friendly static checks without changing the extension permission model.

✨ Highlights

• Hermes compatibility panel — Added a capability panel backed by /v1/capabilities, with legacy fallback for older gateways that do not expose the newer capability route.
• Cleaner first-run Connect flow — If browser pairing is not advertised by the connected runtime, Connect now skips dead pairing routes and guides users directly to Manual setup.
• Capability-gated voice dictation — Voice features now prefer Hermes STT when available and fall back to Browser speech when audio transcription is not exposed by the connected runtime.
• Token hygiene UI — Added masked token state, connection mode, last-tested timestamp, and one-click token clearing so users can see security state without exposing secrets.
• “What Hermes saw” receipts — Sent turns now include a collapsible receipt showing the active tab/context/attachment/redaction payload that was sent.
• Safer optional API behavior — Image upload and profile APIs are now capability-gated, so missing routes become clear fallback warnings instead of confusing failures.
• Clearer Remote gateway behavior — With an API key, Remote means a remote API server and same-LAN http://host:8642 is supported. With a blank key, Remote means HTTPS dashboard WebSocket mode.
• Public permissions, data-flow, and privacy docs — Documented the shipped permission model and browser-context data flow for users and contributors.
• Update troubleshooting — Added guidance for stale unpacked extension cards that still show 0.1.4 after an update, plus native Hermes computer-use troubleshooting pointers.

🧭 v0.1.5 channel updates after the initial tag

These updates landed on main after the first v0.1.5 tag so this release page can act as the public changelog for the v0.1.5 line.

DOM context chip states

Contributed by @iruzen-dono in #19.

• Replaced the misleading initial 📎 DOM · 0 chars · ~0 tok state with explicit chip states:
  • 📎 Loading...
  • 📎 Restricted · N/A
  • 📎 Error · N/A
  • 📎 DOM · X chars · ~Y tok
• Distinguished page-loading, browser-restricted pages, context-capture failures, and normal captured DOM context.
• Added follow-up regression coverage for loading, restricted, error, and captured context states.

Contributor linting + fresh-clone tooling

Contributed by @iruzen-dono in #18, finalized by maintainer follow-up.

• Added ESLint flat config and npm run lint / npm run lint:fix scripts for JavaScript static checks.
• Added the browser/extension globals needed for the current extension runtime.
• Added package-lock.json so npm ci works for fresh clones and future automation.
• Updated contributor docs to call out linting for JavaScript changes.
• Cleaned redaction-helper regex escapes surfaced by lint while preserving token redaction behavior.

🙌 Contributors

• @iruzen-dono / Zhou Jules — DOM chip state fix in #19 and ESLint/static-checking foundation in #18.
• @abundantbeing — v0.1.5 compatibility/trust release, regression coverage, release packaging, and final tooling hardening.

✅ Verification

Initial v0.1.5 package verification:

• npm run verify passed.
• npm run build passed.
• Built unpacked extension at dist/.
• Packaged release archive: artifacts/hermes-browser-extension.tar.gz
• Archive SHA256: cf4451ba8c02f78651f9fc798067bf15a6e7475b178aa02ef47a7508b5f711e3

Current v0.1.5 channel verification on main after follow-up updates:

• npm ci passed.
• npm run test passed: 78/78 tests.
• npm run lint passed with 0 errors. There are 4 existing unused-helper warnings in extension/sidepanel.js.
• npm run verify passed.
• npm run build passed.

Install / update

Download the archive below, extract it, then load the extracted extension folder in chrome://extensions / edge://extensions with Developer Mode enabled.

If Chrome still shows 0.1.4, remove the old unpacked extension card and load the fresh extracted v0.1.5 folder again.

Source users can pull main for the follow-up v0.1.5 channel updates listed above.