Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Browser extension that connects web context to local/remote Hermes Agent runtime via side panel
triggers
["install the hermes browser extension","set up hermes browser side panel","connect browser to hermes agent","configure hermes browser extension","use hermes with browser context","send webpage content to hermes","attach browser context to hermes","troubleshoot hermes browser extension"]
Hermes Browser Extension is a Chrome/Edge/Chromium side panel that connects active web page context to a Hermes Agent runtime (local or remote). It is not a standalone chatbot—it's a browser interface for the real Hermes Gateway/API server, accessing your configured models, tools, skills, sessions, memory, and MCP servers.
Key capabilities:
Side panel UI powered by Chrome Side Panel API (MV3)
Connects to local (http://127.0.0.1:8642) or remote Hermes API server
Syncs providers, models, profiles, skills, sessions, and capabilities from Hermes
Captures and sends active tab context (title, URL, readable text, selected text, metadata, headings, links, forms, buttons)
Supports per-tab or global side panel mode
Streams responses from Hermes
Voice dictation via Hermes STT or browser speech fallback
Read-only context capture (no browser control, no form submission)
Never commit API keys. Use $(hermes auth token create --scope browser) to generate scoped tokens, or reference secrets from environment/vault.
Troubleshooting
Extension loaded but nothing works
Ensure you loaded dist/, not repo root
Selected folder must contain manifest.json directly
Check chrome://extensions shows version 0.1.6+
Cannot connect to Hermes
# Verify API server is running and reachable
curl http://127.0.0.1:8642/health
# Check models endpoint with auth
curl -H "Authorization: Bearer your-key-here" http://127.0.0.1:8642/v1/models
Common issues:
API_SERVER_ENABLED=true not set in ~/.hermes/.env
Hermes Gateway not running (hermes gateway run)
Wrong API_SERVER_KEY or extension API key
CORS origin mismatch (extension ID not in API_SERVER_CORS_ORIGINS)
Firewall blocking port 8642
Wrong version after update
Browser cached old unpacked folder:
Run npm run build to generate fresh dist/
Open chrome://extensions
Click Reload on Hermes Browser Extension card
If still wrong, click Remove, then Load unpacked and select fresh dist/
Verify version: click Details → see Version field
No page context captured
Extension cannot read restricted pages:
chrome:// or edge:// internal pages
chrome-extension:// pages
Banking, crypto, password, payment, health, government domains (intentional security restriction)
On normal https:// pages, check:
Context scope is not "Chat only"
Page has readable text (not just images/video)
Click "What Hermes saw" to inspect captured context
Voice dictation not working
Check Hermes capabilities: extension queries /v1/capabilities for STT support
If Hermes STT unavailable, extension falls back to browser speech recognition
Browser speech requires microphone permission (granted on first use)
Some browsers/OSes may not support Web Speech API
Computer use / browser automation not working
Hermes Browser Extension is read-only. It does not have browser control permissions (debugger, click, type, form submit).
For native computer use:
# On machine running Hermes
hermes tools list
hermes computer-use status
Computer use comes from Hermes Agent's computer_use toolset via cua-driver, not the browser extension.
CORS errors in console
Extension origin must be allowlisted on Hermes API server:
Find extension ID at chrome://extensions. Restart hermes gateway run after changing.
Session persistence issues
Extension binds one Hermes session per pinned tab
Switching tabs creates new sessions (unless "Follow active tab" is enabled)
Check /api/sessions in Hermes to see active sessions
Clear local history: Settings → Browser behavior → Clear history
Streaming response fails
Extension auto-falls back to non-streaming if:
Gateway does not support stream: true
Network drops chunks
Response is not SSE format
Check gateway logs for streaming errors. Non-streaming mode still works.
Security notes
Extension is intentionally conservative:
Read-only: no click, type, form submit, download, or browser control
No sensitive permissions: no debugger, nativeMessaging, cookies, history, downloads, bookmarks
Content wrapped as untrusted: page text marked as external context before Hermes sees it
Local-first default: connects to 127.0.0.1:8642 unless you configure remote
Bearer auth required: strong API key for all API access
CORS allowlist: extension origin must be explicitly allowed
See repo docs: SECURITY.md, PERMISSIONS.md, DATA-FLOW.md, PRIVACY.md.
Key files
dist/ # Built extension (load this)
extension/
manifest.json # MV3 manifest with side_panel, activeTab, scripting
background.js # Service worker, message routing
sidepanel/
index.html # Side panel UI entry
app.jsx # Main React app
content/
content-script.js # Page context capture
lib/
hermes-client.js # Hermes API/WebSocket client
storage.js # Chrome storage wrapper
context-capture.js # DOM scraping logic
Common workflows
Install and connect to local Hermes
git clone https://github.com/abundantbeing/hermes-browser-extension.git
cd hermes-browser-extension
npm install
npm run build
# On Hermes machine, edit ~/.hermes/.env:# API_SERVER_ENABLED=true# API_SERVER_HOST=127.0.0.1# API_SERVER_PORT=8642# API_SERVER_KEY=<secret># API_SERVER_CORS_ORIGINS=chrome-extension://<id>
hermes gateway run
# In browser: chrome://extensions → Load unpacked → select dist/# In side panel: Connect to Hermes → Local gateway → http://127.0.0.1:8642 → paste key → Test → Save
Switch between multiple local Hermes instances
Settings → Localhost agent picker:
Port 8642 - Default gateway
Port 8643 - Dev gateway
Port 8644 - Testing gateway
Click to switch. Extension stores per-port settings.
Use with remote Hermes on Tailscale
# On remote Hermes machine
API_SERVER_HOST=0.0.0.0
API_SERVER_PORT=8642
API_SERVER_CORS_ORIGINS=chrome-extension://<id>
# In extension# Remote gateway → http://100.x.y.z:8642 → paste key → Test → Save
Capture and analyze open tabs
In side panel:
/tabs
# Or manually:
List all my open tabs and summarize each one
Extension sends tab list (title, URL) for all open tabs to Hermes.
Pin to specific page for isolated conversation
Open page you want to analyze
Click context menu in composer header → Page only
Panel shows pinned tab indicator
All messages in this panel now tied to that tab, with isolated Hermes session
Switch tabs → panel stays on pinned tab
Click context menu → Follow active tab to resume auto-switching
This skill covers: installation, local/remote configuration, context capture, voice dictation, quick commands, streaming, theming, security model, and troubleshooting for the Hermes Browser Extension.
