A practical troubleshooting and configuration skill that makes Hermes browser automation reliable on Fedora Atomic and bootc systems.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install hermes-browser-fedora-atomic
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install hermes-browser-fedora-atomic using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is Hermes Browser on Fedora Atomic?
Hermes Browser on Fedora Atomic diagnoses the two configuration failures commonly mistaken for broken browser tooling: routing through the paid Nous Tool Gateway and attempting to clone a non-Chromium OS-default profile. It provides a durable local-mode configuration using Hermes-managed Chromium, without changing the immutable host or the user's default browser.
This Openclaw Skills resource also clarifies the difference between Hermes built-in browser tools and the separate Browser-Use Python harness, explains SPA rendering limitations, and supplies verification commands for local Chromium lifecycle, reboot safety, and process cleanup.
Hermes Browser on Fedora Atomic Use Cases
- Fix
browser_*failures reporting that the Nous Tool Gateway is unavailable. - Resolve
default browser is not a supported Chromium browsererrors when Firefox, Zen, or another Gecko browser is the OS default. - Configure local browser automation on Fedora Atomic or bootc hosts.
- Render and inspect client-side applications such as Docusaurus and Next.js SPAs.
- Keep a non-Chromium browser as the user's default while Hermes uses an isolated Chromium profile.
- Verify that managed Chromium launches, renders pages, and is reaped cleanly after use.
- Diagnose whether a failure belongs to Hermes local tools or the separate
browser_execBrowser-Use harness.
How Hermes Browser on Fedora Atomic Works
- Identify the active Hermes browser path and determine whether the failure is caused by
use_gateway,use_real_profile, an external CDP target, or the Browser-Use harness. - Set Hermes to
cloud_provider: localso built-in browser tools use the managed local Chromium backend. - Disable
use_gatewayto avoid routing requests to the paid Nous Portal Tool Gateway. - Disable
use_real_profileso Hermes creates a clean throwaway Chromium profile instead of cloning the OS-default browser profile. - Install Hermes's user-space Chrome-for-Testing build with
agent-browser install, without invoking system dependency installation. - Use built-in
browser_*tools or theagent-browserCLI to navigate, render, inspect, and interact with web pages. - Close the browser and confirm the managed process is reaped, avoiding orphaned processes or a persistent debug port.
- Treat
browser_execseparately: it requires a repaired Browser-Use environment and an externally running Chrome exposed throughcdp_urlorBU_CDP_URL.
Hermes Browser on Fedora Atomic Setup
- Edit
~/.hermes/config.yamland configure the browser section:
browser:
cloud_provider: local
use_gateway: false
use_real_profile: false
- Install Hermes's managed Chromium in user space. Do not use
--with-depson Fedora Atomic:
npx --yes agent-browser install
The browser is installed under ~/.agent-browser/browsers/chrome-<ver>/ and persists across reboots. The --with-deps option assumes a classic package-manager workflow and may mishandle Fedora Atomic systems; if a shared library is genuinely missing, layer only the required package deliberately with rpm-ostree.
- Verify local Chromium and single-page application rendering:
npx --yes agent-browser read https://docs.b.ai/llmservice
- Close the browser and check that its process has been reaped:
npx --yes agent-browser close
pgrep -af "agent-browser/browsers/chrome" | grep -v pgrep || echo "reaped OK"
- Use the built-in Hermes browser tools for the primary validation path. Do not rely on
browser_execto validate local mode because it uses a separate Browser-Use Python harness and an externally running Chrome CDP endpoint.
Hermes Browser on Fedora Atomic Data Schema & Taxonomy
Configuration
| Key or file | Purpose |
|---|---|
~/.hermes/config.yaml |
Persistent Hermes browser configuration. |
browser.cloud_provider |
Set to local to force managed local Chromium; other values can route to cloud providers. |
browser.use_gateway |
Set to false to avoid the paid Nous Portal Tool Gateway. |
browser.use_real_profile |
Set to false to use a clean Chromium profile independent of the OS default browser. |
browser.cdp_url |
CDP endpoint consumed by browser_exec and relevant cloud or external-browser modes; it is not the managed local Chromium target. |
Generated browser files
~/.agent-browser/browsers/chrome-<ver>/stores the user-space Chrome-for-Testing installation.- The managed browser uses a temporary or throwaway profile for isolated sessions.
- The local backend automatically launches and reaps Chromium rather than requiring a permanently running
:9222process.
Metadata taxonomy
- Skill name:
hermes-browser-fedora-atomic - Version:
1.0.0 - Author: Hermes Agent
- License: MIT-0
- Supported OS: Linux
- Tags: Hermes, browser, Chromium, Fedora Atomic, bootc, Playwright, agent-browser, troubleshooting, and configuration
- Related concepts: CDP, Camofox, Browserbase, Browser-Use, SPA rendering, and immutable operating systems
Hermes Browser on Fedora Atomic Advanced Features
- Automatic backend resolution follows CDP, Camofox, managed local Chromium, and Browserbase when
engine: autois used. - Explicit local mode overrides backend discovery and avoids fragile static-port browser processes.
- Profile isolation lets Zen, Firefox, or another Gecko browser remain the OS default.
- Built-in browser tools support navigation, snapshots, clicks, typing, scrolling, and JavaScript-rendered page inspection.
- The
agent-browserCLI provides a lightweight verification path independent ofbrowser_exec. - SPA-aware troubleshooting distinguishes empty server-side extraction from successful real-browser rendering.
- CDP configuration remains available for advanced Browser-Use workflows while keeping the managed local path separate.
- The diagnostic model separates gateway entitlement errors, unsupported profile errors, missing shared libraries, and Browser-Use harness packaging failures.
SKILL.md
Loading
Related Openclaw Skills
Device Connectivity
Device Connectivity pairs Android or iOS phones with Linux desktops through the KDE Connect protocol for seamless cross-device control and data sharing.
Hermes Web Tools
Hermes Web Tools provides a read-only workflow for configuring, selecting, and troubleshooting Hermes web_search and web_extract backends.
Starship Prompt
A complete developer reference for installing, configuring, customizing, and troubleshooting the fast, cross-shell Starship prompt.
PDF Creation with fpdf2
Create lightweight, searchable, Unicode-safe PDF documents with Python and fpdf2 when reportlab is unavailable or unsuitable.
AI Web Check
AI Web Check performs an evidence-first, non-mutating assessment of website usability and agent readiness.
Zhongkui Guard
Zhongkui Guard scans AI-related content for suspicious commands, redacts sensitive data, and evaluates configured model APIs with evidence-based reports.
Featured*
