# Hive.browser Automation

Required before any hive-browser CLI command.

- Repository: https://github.com/aden-hive/hive (11131 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add aden-hive/hive --skill hive.browser-automation -g -a claude-code -y`
Codex: `npx skills add aden-hive/hive --skill hive.browser-automation -g -a codex -y`
Cursor: `npx skills add aden-hive/hive --skill hive.browser-automation -g -a cursor -y`
Gemini CLI: `npx skills add aden-hive/hive --skill hive.browser-automation -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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:

The rest: https://github.com/aden-hive/hive/blob/HEAD/core/framework/skills/_default_skills/browser-automation/SKILL.md