cli-anything-browser

Automate browser navigation and DOM inspection via a CLI.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/edwifiguy/era-agents-ops --skill cli-anything-browser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-anything-browser
Source: https://github.com/edwifiguy/era-agents-ops/tree/main/skills/era-agents-op/cli-anything/browser/agent-harness/cli_anything/browser/skills
Command: npx skills add https://github.com/edwifiguy/era-agents-ops --skill cli-anything-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This CLI provides a deterministic, scriptable way to automate browser interactions by exposing the page's DOM via a filesystem-like interface backed by the DOMShell MCP server. Users can navigate with commands like ls, cd, and cat to inspect structure and drive actions.

Core Features & Use Cases

  • Filesystem-style DOM navigation: Traverse the Accessibility Tree as if it were a virtual filesystem.
  • Command groups: Use page for navigation, fs for DOM exploration, act for interactions, and session for lifecycle management.
  • Use Case: Automate end-to-end browser tasks such as form filling, data extraction, and automated testing in developer workflows.

Quick Start

Install the CLI, start the DOMShell harness, and issue simple browser-automation commands to open pages and navigate the DOM.

Frequently Asked Questions about cli-anything-browser

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

FAQPage Schema
How do I automate browser interactions from the command line?

The DOMShell CLI supports page navigation, element interaction, DOM inspection, and automated testing across web workflows. It exposes the page's DOM via a filesystem-like interface using page, fs, act, and session command groups.

How does filesystem-style DOM navigation work for web automation?

Traverse the Accessibility Tree as a virtual filesystem using ls, cd, and cat commands to inspect DOM structure. This deterministic approach enables scriptable end-to-end browser tasks like form filling and data extraction in developer workflows.

Do I need the DOMShell integration to use this browser automation CLI?

Yes, the DOMShell MCP server integration is required. You must install the CLI, start the DOMShell harness, and issue browser-automation commands to open pages and navigate the DOM for automated testing and web workflows.

Can I use shell commands to inspect and interact with web pages for automated testing?

Yes, use the fs command group to explore the DOM and the act command group to perform element interactions. This enables scriptable end-to-end browser tasks like form filling, data extraction, and automated testing across web workflows.

What are the limitations of using a filesystem interface for browser automation?

Limitations include the dependency on the DOMShell MCP server backend and the need for URL and permission validation. Complex web workflows may require explicit session lifecycle management using session commands to maintain state across automated testing.