opencli-browser
Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing adapters — see opencli-adapter-author for that.
Security Assessment
About opencli-browser
The opencli-browser skill enables an agent to control a live Chrome browser directly through the OpenCLI interface. It allows automated interaction with web pages, including inspecting page content, filling out forms, clicking through complex or logged-in workflows, and extracting data on demand. This skill addresses the challenge of programmatically navigating dynamic web pages while maintaining reliability and accuracy in element selection, making it ideal for tasks that require precise, real-time browser manipulation without relying on static adapters.
Key features of opencli-browser include a selector-first target contract, where each command targets a specific element via numeric references or CSS selectors, and a structured envelope response that reports matches and confidence levels. It supports compound form fields, handling of stale references, and network activity capture. Additional capabilities include managing tab leases to keep browser sessions alive, binding to existing user tabs for logged-in workflows, and controlling foreground visibility and live inspection modes. The skill emphasizes reliability with detailed feedback on element matching and DOM changes, helping agents navigate even in complex or evolving web environments.
This skill is primarily intended for agents needing direct browser automation rather than developers creating reusable adapters. Typical use cases include automating tasks on web applications with login flows, scraping structured data from interactive pages, or performing ad-hoc browser inspections for debugging or analysis. Users are expected to meet prerequisites such as having Chrome running with the necessary OpenCLI extensions and ensuring proper tab access. OpenCLI agents, automation engineers, and developers seeking precise, programmatic control of live web sessions are the main target audience for this tool.
FAQ
How do I ensure opencli-browser is ready to use?
Run `opencli doctor` and confirm that all checks are green. Common issues include Chrome not running, the OpenCLI extension not installed, or debug ports blocked by other extensions.
Can I use opencli-browser on already open tabs with logged-in sessions?
Yes, by using `opencli browser bind` to attach a bound workspace to an existing tab. This preserves the current session and position, preventing accidental navigation or tab closure.
What browsers and environments are supported?
opencli-browser is designed to drive a real Chrome instance with the OpenCLI extension installed. Other browsers are not supported.
What happens if a bound tab is closed or becomes non-debuggable?
The binding fails closed, meaning the workspace will stop working. You must re-run the `bind` command on a valid tab to continue automation.
Does opencli-browser automatically handle DOM changes?
Yes, envelope responses indicate `match_level` as `exact`, `stable`, or `reidentified` to show how confident the match is, allowing agents to adapt to moderate DOM drift.
Install opencli-browser
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
jackwener/opencli