hermes-browser-extension

Name: hermes-browser-extension
Author: abundantbeing

Verified

Browser-native side panel for Hermes Agent — connect web context to your local Hermes runtime.

1,664stars

161forks

JavaScript

Installation

# Add to your Claude Code skills
git clone https://github.com/abundantbeing/hermes-browser-extension

Getting Started

Guides for using ai agents skills like hermes-browser-extension.

Caveman: Cut Claude Token Use by 65%
How agent-side prompt compression works, when to use it, and when not to.
What is an AI Skills Marketplace?
Definitions, how marketplaces work, and how to choose between them in 2026.
Getting Started with AI Skills

Security ReportVerified

Last scanned: 6/27/2026

{
  "issues": [],
  "status": "PASSED",
  "scannedAt": "2026-06-27T06:52:36.908Z",
  "npmAuditRan": true,
  "pipAuditRan": true,
  "promptInjectionRan": true
}

Compare with similar skills

See how hermes-browser-extension compares with popular alternatives.

hermes-browser-extension vs hermes agent

See comparison

README.md

Frequently Asked Questions

What is 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 1,664 GitHub stars.

Is hermes-browser-extension safe to use?

Yes. hermes-browser-extension passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.

How do I install hermes-browser-extension?

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).

What programming language is hermes-browser-extension written in?

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.

Are there alternatives to hermes-browser-extension?

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.

AI Courses · Agentic AI, LLM Engineering & MCP

Beginner to professional · First lesson free · Lifetime access

20% off

Comments (0)

to leave a comment.

No comments yet. Be the first to share your thoughts!

Related Skills

ECC

by affaan-m

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

278,805

Developers Also Liked

Based on votes and bookmarks from developers who liked this skill

hermes-agent

by NousResearch

The agent that grows with you

253,603

ghost-os claude-code-my-workflow

⚠️ Third-Party Software Notice

This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.

Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.

Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.

Read the Terms of Service

Hermes Browser Extension

Browser-native side panel for Hermes Agent — connect active web context through a local gateway, Hermes Cloud, or a self-hosted remote gateway.

Created by Jon Komet (@abundantbeing). Community extension for Hermes Agent by Nous Research.

What it is

Hermes Browser Extension is not a browser chatbot. It is a Chrome/Edge/Chromium side panel for the real Hermes Agent runtime. Choose a local gateway, attach to a signed-in Hermes Cloud agent tab, or connect to a self-hosted remote API/dashboard. Local and remote API connections can use the models, tools, skills, sessions, memory, and MCP servers already configured in Hermes; Cloud and dashboard-ticket connections are intentionally Chat-only.

Bot Mode brings your Hermes agent roster into the panel: switch agents, edit profiles, and run group chats where several agents reply in one room. Current group-chat limitation: page-context delivery is not yet reliable; do not assume group bots can see the active page. Hermes Control is not shown in group chats. Individual bot chats retain their existing page-context and control behavior. Chat-only and remote group turns do not capture page context.
File attachments show one card per file per message. Open previews the file, Open on computer reveals the original file's containing folder through local Hermes, and Save downloads a copy.
Tab screenshot stages the visible, approved page as an image attachment when you choose it from the attachment menu. Screenshots are never captured automatically.
Browser Control changes which tabs a turn reads from the composer: This tab, Selected tabs, or a Task set of tabs you pick explicitly.
Live sessions: running chats are highlighted in Sessions. On gateways that expose live sessions, reopen a working chat to follow its reply and tool activity. Supported live sessions offer Steer, Queue, and Stop instead of idle send controls, and steers sent from another client appear in the followed transcript.
Tool activity: a compact expandable list keeps calls out of the reply. Inspect individual calls, close the list without hiding thinking, and keep your place while activity updates.
Message tools: Copy, Edit, and Restore checkpoint on supported turns, with day dividers, message times, and theme-aware bubbles.
Reasoning effort: a slider with tick marks, or buttons if you prefer. The choice is remembered. In a group chat each bot keeps its own effort.
Hermes Assist drafts beside supported text composers and never sends, posts, or submits for you.
Page comments: pick an element, write a note, and queue pins beside Ask Hermes.
Settings: a category home opens one section at a time, with Back navigation, edited-category markers, and direct links from related controls.
Appearance: Light, Dark, or System mode, twelve themes, text zoom, and a font list. Everforest has forest greens and warm parchment; Classic Hermes has amber gold and navy; Anti-Nous has crimson, navy reading panels, and fine gold trim. Nous Light keeps its white shell and Nous Blue accents. Centered background artwork changes when you open the panel and scales with its width; sidecar illustrations rotate independently.

The full list of changes per version lives in the changelog and the releases.

Visual tour

Screenshots use the Mono theme in Dark mode.

Side panel	Bot chats	Edit a bot

Theme settings	Local agents	Hermes Control

Requirements

Hermes Agent installed and working.
For Local or Remote API mode: Hermes Gateway/API server enabled locally or on a reachable remote machine. Hermes Cloud instead requires a signed-in HTTPS agent tab.
Node.js 20+.
Chrome, Edge, Brave, Comet, or another Chromium browser with Side Panel API support (Chrome 116+ baseline). Firefox 142+ is supported via AMO, the Mozilla Add-ons listing. npm run build:firefox is for local/dev Firefox builds only.

Firefox scope

Hermes Browser Extension on Firefox is a chat-and-context client: pairing, the side panel, streaming replies, attachments, and page-context capture all work, but real-tab attach ("Hermes Control") is Chromium-only. Firefox WebExtensions have no equivalent to Chromium's debugger API, so the Firefox package omits that permission and the panel reports Control unavailable with an explanation instead of failing silently.

If you need Hermes to click, type, scroll, or operate tabs on your behalf, load the extension in Chrome, Edge, Brave, or another Chromium browser. The full compatibility matrix is in guides/connection-guide.md.

Quick start

1. Clone and build

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/

2. Load unpacked in Chrome/Edge

Open chrome://extensions or edge://extensions.
Enable Developer mode.
Click Load unpacked.
Select this repo's dist/ folder — not the repo root and not extension/.
Pin/click the Hermes extension icon to open the side panel.

After code updates, run npm run build again and click Reload on the Hermes Browser Extension card in the browser extensions page.

3. Install in Firefox

Open AMO in Firefox.
Click Add to Firefox and confirm the permission prompt.
The extension opens in the Firefox sidebar (Ctrl+Shift+H).

Because this package is Mozilla-hosted on AMO, Firefox receives future signed updates through AMO automatically. No separate update manifest or manual reinstall is required.

Do not sideload the GitHub source zip/tar.gz. Those are source archives, not a Firefox add-on.

Connect to Hermes

Settings exposes the same three product-level choices as Hermes Desktop:

Connection mode	Use it for	Transport and boundary
Local gateway	Hermes running on this machine	Local API server, default `http://127.0.0.1:8642`, with a scoped browser token or `API_SERVER_KEY`.
Hermes Cloud	A signed-in Hermes Cloud agent open in a normal browser tab	Trusted Dashboard Attach mints a short-lived, single-use WebSocket ticket from the active HTTPS agent tab. Chat-only; no page text, selected text, open-tab context, or attachments are sent.
Remote gateway	A self-hosted Hermes backend on another machine or behind a trusted proxy	With a key: remote API server. Without a key: signed-in HTTPS dashboard ticket/WebSocket.

Existing installations migrate automatically: prior local-api settings become Local gateway, while prior remote-api and remote-dashboard settings remain Remote gateway. A legacy remote dashboard is never silently relabeled as Hermes Cloud.

Local API server

Local-only is the safest default. Put this in your Hermes .env on the machine running Hermes: %LOCALAPPDATA%\hermes\.env on native Windows, ~/.hermes/.env on Linux/macOS/WSL, or $HERMES_HOME/.env if you relocated the data dir or use a named profile:

API_SERVER_ENABLED=true
API_SERVER_HOST=127.0.0.1
API_SERVER_PORT=8642
API_SERVER_KEY=<your-api-server-key>
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:

Click Connect to Hermes and approve locally if your Hermes Desktop/gateway supports the approval flow.
If approval is not available yet, click Manual setup.
Choose Local gateway.
Use Gateway URL http://127.0.0.1:8642.
Paste your scoped browser token or API_SERVER_KEY.
Click Test connection, then Save settings.
Open a normal https:// page and ask: Summarize this page in one sentence.

Remote and Cloud

For a remote machine, bind the API server to a reachable trusted interface and keep CORS narrow. Use a private same-LAN/Tailscale/VPN host with HTTP, or put the API