Browser Daemon

Name: Browser Daemon
Availability: InStock
Author: Jack

Maintain a persistent Playwright-driven Chrome session via file-based IPC commands.

16|7|Updated Nov 20, 2025

Search Tags:#automation #debugging #playwright #browser-daemon

Ready to run

npx skills add https://github.com/jackspace/ClaudeSkillz --skill browser-daemon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Browser Daemon
Source: https://github.com/jackspace/ClaudeSkillz/tree/main/skills/playwright-skill
Command: npx skills add https://github.com/jackspace/ClaudeSkillz --skill browser-daemon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a persistent Playwright-based browser daemon that stays open, accepts commands, and returns results. Ideal for interactive debugging, development, and browser-driven testing workflows.

Core Features & Use Cases

Maintain a single browser instance across commands
Navigate, execute JS, inspect console output
Capture and review network activity and page events
Lightweight IPC via file-based commands and results
Extensible for broader browser automation tasks

Quick Start

Start the daemon, then send commands like navigate, exec, or status to perform browser tasks without reopening a browser.

Frequently Asked Questions about Browser Daemon

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

FAQPage Schema

How do I set up a persistent browser instance for automated testing?▼

Browser Daemon maintains an open Playwright-driven Chrome session that accepts commands via file-based IPC, eliminating the need to reopen a browser for each test. Send navigate, exec, console, and status commands through .browser-command files to control the session and retrieve structured results including URL, title, and console logs.

Can I use Playwright for interactive debugging without restarting the browser?▼

Yes. Browser Daemon runs a persistent Chrome instance with visible UI that stays open across multiple commands. Issue debugging commands like navigate, execute JavaScript, and inspect console output without restarting, making it ideal for development and interactive testing workflows.

How do I capture console output and page state during browser automation?▼

Browser Daemon captures all console logs and returns structured output including the current URL, page title, and console messages in .browser-result files. Each command execution preserves this state, allowing you to review network activity and page events across your testing session.

What's the best way to control a browser through file-based commands?▼

Browser Daemon uses lightweight file-based IPC with .browser-command and .browser-result files, eliminating complex socket or HTTP setup. Write commands to trigger navigation, JavaScript execution, and status checks, then read structured results—ideal for simple, reliable browser automation in testing and debugging.

Does Browser Daemon preserve state when the daemon restarts?▼

Yes. Browser Daemon preserves the last navigated URL across restarts, ensuring your session context persists. This enables reliable resumption of testing workflows and debugging sessions without losing your navigation history.

Can I extend Browser Daemon for custom browser automation workflows?▼

Browser Daemon's daemon-based IPC design is extensible for broader browser automation tasks. The file-based command interface and structured output format support adding custom commands and integrating with larger testing and debugging pipelines.