Browser-native side panel for Hermes Agent — connect web context to your local Hermes runtime.
# Add to your Claude Code skills
git clone https://github.com/abundantbeing/hermes-browser-extensionGuides for using ai agents skills like hermes-browser-extension.
hermes-browser-extension is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by abundantbeing. Browser-native side panel for Hermes Agent — connect web context to your local Hermes runtime. It has 53 GitHub stars.
hermes-browser-extension's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/abundantbeing/hermes-browser-extension" and add it to your Claude Code skills directory (see the Installation section above).
hermes-browser-extension is primarily written in JavaScript. It is open-source under abundantbeing on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh hermes-browser-extension against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Browser-native side panel for Hermes Agent — connect active web context to your local or remote Hermes runtime.
Created by Jon Komet (
@abundantbeing). Community extension for Hermes Agent by Nous Research.
Hermes Browser Extension is not a browser chatbot. It is a Chrome/Edge/Chromium side panel for the real Hermes Agent runtime. It talks to your Hermes Gateway/API server — local by default, remote when you configure a reachable URL — so it can use the models, tools, skills, sessions, memory, and MCP servers already configured in Hermes.
This repo is specifically for the extension. A future standalone Hermes Browser may become a separate native macOS/Linux/Windows app built on the groundwork from this extension.
| Side panel | Theme settings | Local agents |
|---|---|---|
http://127.0.0.1:8642.debugger, nativeMessaging, click/type/form-submit, cookies, history, bookmarks, downloads, or browser-control permissions in v0.1.git clone https://github.com/abundantbeing/hermes-browser-extension.git
cd hermes-browser-extension
npm install
npm run build
The loadable extension is generated at:
dist/
chrome://extensions or edge://extensions.dist/ folder — not the repo root and not extension/.After code updates, run npm run build again and click Reload on the Hermes Browser Extension card in the browser extensions page.
Local-only is the safest default. Put this in ~/.hermes/.env on the machine running Hermes:
API_SERVER_ENABLED=true
API_SERVER_HOST=127.0.0.1
API_SERVER_PORT=8642
API_SERVER_KEY=<strong-local-secret>
API_SERVER_CORS_ORIGINS=chrome-extension://<your-extension-id>
Start or restart the gateway:
hermes gateway run
Verify the API server:
HERMES_GATEWAY_URL=http://127.0.0.1:8642
HERMES_API_TOKEN='<your-api-server-key-or-browser-token>'
curl "$HERMES_GATEWAY_URL/health"
curl -H "Authorization: Bearer $HERMES_API_TOKEN" "$HERMES_GATEWAY_URL/v1/models"
Then in the extension side panel:
http://127.0.0.1:8642.API_SERVER_KEY.https:// page and ask: Summarize this page in one sentence.For a remote Hermes machine, bind the API server to a reachable trusted interface and keep CORS narrow:
API_SERVER_ENABLED=true
API_SERVER_HOST=0.0.0.0
API_SERVER_PORT=8642
API_SERVER_KEY=<strong-remote-secret>
API_SERVER_CORS_ORIGINS=chrome-extension://<your-extension-id>
Use Tailscale/VPN/reverse proxy + HTTPS where possible. Do not expose the Hermes API server naked to the public internet. The Hermes API server can access the real Hermes runtime and tools.
If you run Hermes elsewhere and only expose the OAuth-gated dashboard, select Remote, enter the dashboard's https:// URL, and leave the API key blank. With no key, the extension connects over the dashboard's /api/ws socket instead of the REST API server.
Auth uses a single-use WebSocket ticket minted from a signed-in dashboard tab:
Limitations in this mode: image attachments are inline-only, and the skills/profiles lists are unavailable because those are REST-only and the dashboard's REST surface is not reachable cross-origin.
After connection, the side panel loads from the connected Hermes gateway:
/v1/models — all providers/models Hermes can enumerate, including provider-qualified IDs./api/sessions — recent Hermes sessions grouped by source./v1/skills — slash-command skill suggestions in the composer./v1/profiles — profile picker when the gateway exposes profile metadata./v1/capabilities — feature flags such as audio transcription and Browser upload support.The DOM/context chip should show a non-zero page-context count on normal readable pages. Browser internal pages such as chrome://extensions are intentionally restricted.
You can ask Hermes to help install it:
Install Hermes Browser Extension from https://github.com/abundantbeing/hermes-browser-extension. Clone it, run npm install, run npm run build, then use computer use to open chrome://extensions, enable Developer mode, load the dist folder unpacked, and help me connect it to my local or remote Hermes Gateway API server. Do not reveal, print, screenshot, or commit my API key.
Hermes Browser Extension is intentionally conservative in v0.1:
debugger, nativeMessaging, cookies, history, downloads, or bookmarks permissions.See SECURITY.md for details.
Make sure you loaded dist/, not the repo root. The selected folder must contain manifest.json directly.
Check that Hermes Gateway/API server is running and reachable from the browser:
curl http://127.0.0.1:8642/health
# or, for remote mode:
curl http://<trusted-remote-host>:8642/health
If /v1/models fails, check API_SERVER_KEY, the extension's stored API key/browser token, and API_SERVER_CORS_ORIGINS. For remote mode, the browser extension origin (chrome-extension://<id>) must be allowlisted on the Hermes machine.
0 charsOpen a normal https:// page and refresh context. Browser internal pages (chrome://, edge://, extension pages, devtools, etc.) are restricted by design.
Chromium side panels can suppress microphone permission prompts. Hermes Browser Extension handles this with a visible extension voice page:
If Chromium still says the mic is blocked, click Open microphone settings in the voice tab and set Microphone to Allow for chrome-extension://<the Hermes extension id>/, then return to the voice tab and try again.
Use Manual setup with your local/remote Gateway URL and API ke