Skip to content

v0.1.8

Choose a tag to compare

View all tags
@abundantbeing abundantbeing released this 04 Jul 03:10
v0.1.8
6b3ff9f

Hermes Browser Extension v0.1.8 update ad

Hermes Browser Extension v0.1.8

Release Date: July 4, 2026
Since v0.1.7: 11 commits · 31 files changed · 2,103 insertions · 220 deletions · 145 tests passing

Steer the run. Keep the tools. Know the meter. v0.1.8 makes Hermes Browser feel like a real Hermes client instead of a thin page-context chat box: active turns can be steered, tool calls render as live runtime activity, selected models and provider settings are actually carried into the request path, and the context meter now separates live context from cumulative token spend.

The important part: this stays full Hermes. Tools, skills, page context, tab selection, voice, local/remote gateways, dashboard pairing, and Desktop/TUI-style session behavior stay in the product. This release tightens the controls and telemetry around that power instead of stripping it down.

✨ Highlights

  • Active-run steering is now first-class — while Hermes is already working, text-only composer submit steers the active turn by default. Queue is explicit, Stop remains visible, and backend-queued steer text is restored to the draft instead of silently becoming the next prompt.

  • Runtime model routing is real — Browser sends the selected model, provider, reasoning controls, and fast/service-tier options with session chat. The API path now acknowledges the effective runtime so the UI can distinguish what was selected from what actually ran.

  • Context tracking no longer lies — the context bar uses runtime prompt/context values when Hermes reports them, falls back to the local estimate when it has to, and keeps cumulative token spend separate. Chat-only mode stays lean instead of looking like it is burning the whole window.

  • Live tool activity is readable — tool calls stream into a compact activity strip with tool names, statuses, timings, and sanitized previews instead of leaking raw tool markdown into assistant messages.

  • Model discovery is tougher — Refresh Models now walks the real discovery ladder: Hermes API catalog when available, dashboard model options when paired, and session-discovered models as a fallback. A one-row /v1/models response no longer wipes a deliberate model selection.

  • Fresh Browser sessions behave like Browser sessions — panel-open startup now creates a fresh Browser session by default, keeps transcript scope separate from browser context scope, and avoids accidental auto-resume confusion.

  • Chat-only and tab context are cleaner — Chat only disables browser context capture without switching sessions. Pinned-tab, selected-tab, and follow-active modes keep their own scope, and tab include/exclude controls preserve scroll position instead of fighting the panel.

  • Gateway failures are easier to understand — Hermes runtime/tool tracebacks show as connected-with-warning when the gateway is reachable. Missing routes, API-key issues, CORS/config problems, and upstream runtime failures get more specific diagnostics.

  • Composer and voice polish landed — Enter submits, Shift+Enter inserts a newline, busy composer controls stay compact, the mic hides while a run is active, voice dictation uses the Desktop-compatible transcription route, and sidepanel microphone-block cases fall back to a visible dictation tab.

  • Public alpha hardening — restricted URLs stay protected, obvious secrets are redacted before prompt assembly, remote API validation is stricter, manifest/version checks catch drift, and the package/build metadata now tracks the shipped commit.

Install / update

git clone https://github.com/abundantbeing/hermes-browser-extension
cd hermes-browser-extension
npm install
npm run build

Then open chrome://extensions / edge://extensions, enable Developer mode, click Load unpacked, and select the repo’s dist/ folder.

If Chromium still shows an older build after updating, click Reload on the extension card. If it still looks stale, remove the extension and load the fresh dist/ folder again.

Runtime compatibility

Hermes Browser can still fall back on older Hermes runtimes where possible, but the best v0.1.8 path expects a Hermes API server that exposes the current capabilities contract — especially session runtime reporting and run steering. The extension checks capabilities instead of blindly assuming every route exists.

Verification

  • npm run verify — 145/145 tests passing, JS syntax checks passing, manifest check passing.
  • npm run package — rebuilt the unpacked dist/ folder and packaged the release archive.
  • Live Browser/gateway QA confirmed active steering works against the local Hermes gateway.
  • Packaged archive build metadata: 0.1.8 at commit e1d0f16 with dirty: false.

Assets

  • hermes-browser-extension-v0.1.8.tar.gz
    • SHA256: c1deb37787a8e7c8932210e5216fe2b95ca6c121646e388e6f4e4426f1c88560
  • hermes-browser-extension-v0.1.8-update-ad.png
    • Existing approved v0.1.8 update image retained.
Assets 4
Loading