self-hosted-live-browser-cdp

Name: self-hosted-live-browser-cdp
Availability: InStock
Author: samlaggz

Bind Hermes browser tools to a self-hosted visible Chromium session via CDP.

Updated May 21, 2026

Search Tags:#cdp #browser-automation #chromium #xvfb #live-browser #novnc #watchable-session

Ready to run

npx skills add https://github.com/samlaggz/hermes-agent-sam --skill self-hosted-live-browser-cdp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: self-hosted-live-browser-cdp
Source: https://github.com/samlaggz/hermes-agent-sam/tree/main/backup/skills/dogfood/self-hosted-live-browser-cdp
Command: npx skills add https://github.com/samlaggz/hermes-agent-sam --skill self-hosted-live-browser-cdp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Hermes can drive and observe a self-hosted visible Chromium session with a public watch URL so GUI and non-GUI browser tools share a single browser state.

Core Features & Use Cases

Self-hosted visible Chromium with a public watch URL
Shared browser state between Hermes GUI and automated tools
Stable CDP endpoint and persisted browser state
Step-by-step live-session stack: Xvfb, fluxbox, x11vnc, noVNC, and public tunnel
Use cases include live monitoring, manual observation, and reproducible sessions

Quick Start

Start the desktop stack (Xvfb, fluxbox, x11vnc, and noVNC), expose a public watch URL, and configure Hermes to point to the live CDP URL to drive the shared browser session.

Frequently Asked Questions about self-hosted-live-browser-cdp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up a watchable Chromium session with a public URL for browser automation?▼

A stable CDP endpoint requires a self-hosted stack with Xvfb, fluxbox, x11vnc, and noVNC to maintain the visible Chromium session. You then configure Hermes with a persistent CDP port and browser profile to ensure stable browser automation connectivity.

Can I share a single browser state between manual GUI observation and automated tools?▼

To start live browser monitoring, launch the Xvfb, fluxbox, x11vnc, and noVNC desktop stack, expose a public watch URL, and point Hermes to the live CDP URL. This drives the shared browser session and enables observable automation and manual login monitoring.

Do I need a self-hosted stack to use noVNC and Xvfb for live browser monitoring?▼

Yes, a self-hosted stack is required to provide the visible Chromium session and public watch URL for live browser monitoring. The stack specifically includes Xvfb, fluxbox, x11vnc, and noVNC to render and stream the graphical desktop environment.

Why use a persistent browser profile with a stable CDP port for reproducible sessions?▼

A persistent browser profile and stable CDP port ensure that browser state, including logins and cookies, remains consistent across automated tasks and manual observation. This setup enables reproducible sessions and reliable automated browser control.