Hive.browser Automation
Required before any hive-browser CLI command.
Install
npx skills add aden-hive/hive --skill hive.browser-automation -g -a claude-code -y- Repository
- aden-hive/hive11.1k
- Category
- AI and agents
- Updated
- 9d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Required before any hive-browser CLI command. The browser is driven from the terminal by running `hive-browser <command> ... --json` via terminal_exec, not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome, never kill or launch browser processes; timeouts are transport issues, not crashes), the screenshot + coordinate workflow (hive-browser interact with a fractional coordinate) that reaches shadow-DOM inputs selectors can't see, the viewport-fraction coordinate rule (not pixels), rich-text editor quirks ("send button stays disabled" failures), and CSP gotchas. Covers Chrome via CDP through the GCU Beeline extension.
GCU Browser Automation
All GCU browser automation drives a real Chrome instance through the Beeline extension and Chrome DevTools Protocol (CDP). You drive it from the terminal: every command is hive-browser <command> ... --json, run through terminal_exec. Always pass --json so the result is machine-readable. That means clicks, keystrokes, and screenshots are processed by the actual browser's native hit testing, focus, and layout engines, not a synthetic event layer. Understanding this unlocks strategies that make hard sites easy.
Browser lifecycle & recovery, read this before "fixing" anything
The bridge attaches to the user's already-running Chrome via the extension. The browser is not yours: it holds the user's logged-in sessions and other agents' work, and the runtime, not you, owns the connection to it. Consequences:
