OpenCLI Usage Guide
Make any website or Electron App your CLI. Reuse Chrome login, zero risk, AI-powered discovery.
Install & Run
Prerequisites
Browser commands require:
- Chrome browser running (logged into target sites)
- opencli Browser Bridge Chrome extension installed (load
extension/as unpacked inchrome://extensions) - No further setup needed — the daemon auto-starts on first browser command
Note: You must be logged into the target website in Chrome before running commands. Tabs opened during command execution are auto-closed afterwards.
Public API commands (hackernews, v2ex) need no browser.
Quick Lookup by Capability
Command Quick Reference
Usage: opencli <site> <command> [args] [--limit N] [-f json|yaml|md|csv|table]
Type legend: 🌐 = Browser (needs Chrome login) · ✅ = Public API (no browser) · 🖥️ = Desktop (Electron/CDP) · 🔧 = External CLI (passthrough)
Website Adapters
Desktop Apps (CDP/Electron)
External CLI (passthrough)
OpenCLI can discover, auto-install, and passthrough commands to external CLI tools. Use opencli install <name> to auto-install, or opencli register <name> to register a local CLI.
Management
All commands support: --format / -f with table json yaml md csv
Self-Repair
If a command fails due to a site change (selector, API, or response schema), automatically fix the adapter and retry instead of reporting failure. Re-run the command with OPENCLI_DIAGNOSTIC=1 to get structured diagnostic context, then fix the adapter file at RepairContext.adapter.sourcePath and retry. Max 3 repair rounds. See the opencli-autofix skill for the full workflow.
Related Skills
- opencli-browser — Browser automation for AI agents (navigate, click, type, extract via Chrome)
- opencli-explorer — Full guide for creating new adapters (API discovery, auth strategy, TS writing)
- opencli-oneshot — Quick 4-step template for adding a single command from a URL
- opencli-autofix — Automatically fix broken adapters when commands fail


