skills.rest
samlaggz
samlaggzCOMMUNITY
Explore all skills by this author →
GitHub

live-browser-cdp-workflows

Share a live CDP-backed Chromium browser across GUI and Hermes automation.

Updated May 21, 2026
Search Tags:#debugging#cdp#systemd#browser-automation#noVNC#chromium#live-browser
One-click install
npx skills add https://github.com/samlaggz/hermes-agent-sam --skill live-browser-cdp-workflows
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: live-browser-cdp-workflows
Source: https://github.com/samlaggz/hermes-agent-sam/tree/main/backup/skills/automation/live-browser-cdp-workflows
Command: npx skills add https://github.com/samlaggz/hermes-agent-sam --skill live-browser-cdp-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables users to run a single, self-hosted visible browser session that can be reused by Hermes browser tools for non-GUI automation, ensuring consistent state across GUI watching and automated tasks.

Core Features & Use Cases

  • Shared CDP session: a visible Chromium instance with a fixed remote debugging port that both GUI workflows and Hermes non-GUI operations can reuse.
  • Durable configuration: persist browser.cdp_url and browser.engine settings so the same browser state is reused automatically.
  • Verification & safety: built-in checks to confirm the CDP endpoint is active before tool actions and guidance for troubleshooting common blocks.

Quick Start

Launch a self-hosted visible Chromium session with a fixed remote debugging port, then configure Hermes to reuse that CDP endpoint for both GUI and non-GUI tasks.

Frequently Asked Questions about live-browser-cdp-workflows

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

FAQPage Schema
How do I share a single CDP browser session between GUI viewing and non-GUI automation?▼

To share a CDP browser, launch a self-hosted Chromium instance with a fixed remote debugging port, then configure your non-GUI automation tools to reuse that CDP endpoint for stateful operations.

What is a shared CDP browser session used for in browser automation?▼

A shared CDP browser session provides a single visible Chromium instance that both GUI viewing and non-GUI automated tasks can reuse, ensuring consistent browser state across sites and login flows.

How do I configure Hermes to reuse a live CDP endpoint for non-GUI browser actions?▼

You configure Hermes by persisting the browser.cdp_url and browser.engine settings to point to your Chromium remote debugging port, ensuring the same browser state is reused automatically across tasks.

Do I need noVNC and systemd to run a visible Chromium remote debugging session?▼

You need a self-hosted Chromium with a stable remote debugging port and a viewer like noVNC for visibility, while systemd can manage the service durability of your live browser session.

Why does my non-GUI browser automation fail to maintain state across different sites?▼

Automation fails state consistency when not pointing to a shared CDP URL, so configuring tools to reuse a single visible Chromium remote debugging port ensures stateful integrated browser operations.

What is the best way to verify a CDP endpoint is active before running automated browser tasks?▼

The best way to verify a CDP endpoint is using built-in checks to confirm the remote debugging port is active before tool actions, providing guidance for troubleshooting common blocks.

Related Skills

Explore More Software Engineering Skills→
samlaggzsamlaggz

self-hosted-live-browser-cdp

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

Community
Advanced
GraffiohGraffioh

web-browser

Automate Chrome browser interactions via the Chrome DevTools Protocol.

Community
Advanced
faustellar1995faustellar1995
1

local-test

Build, deploy, and test IronClaw web gateway changes locally with Docker and Chrome MCP.

Community
Intermediate
szymdzumszymdzum
148

bdg

Automate browser control via Chrome DevTools Protocol from the command line.

Community
Intermediate