opera-browser-cli – Opera Neon's Open-Source Command-Line Tool

1. What Is opera-browser-cli

opera-browser-cli is an open-source CLI from the Opera Neon team, built on opera-devtools, letting local AI agents (e.g., Claude Code) control the browser from the terminal. No cloud relay or heavy OAuth—two commands to install—turning AI from Q&A into action for web testing, scraping, and app prototyping. It signals browsers entering the agent era with a low-friction automation pattern.

Technical positioning and domain: Browser automation × AI agents—direct local control via Opera Neon's DevTools on port 9224, unlike Playwright script farms or cloud Browserless/MCP-heavy setups.

Development background: Opera Software, leveraging Neon architecture to fix slow, auth-heavy remote browser control for agents.

Core value: Local, low-latency, privacy-friendly browser as an agent "limb"—38 commands plus Neon-only Do/Make/Research AI ops, auto SKILLs for Claude Code, MIT-friendly open source.

Technical characteristics: opera-devtools protocol; session persistence; Node.js global install; works with any CLI-capable agent.

2. Key Features

• Terminal-driven browser: Open URLs, snapshots, navigation over DevTools—headless-friendly for CI/servers. Example: opera-browser-cli open https://example.com.

• AI agent commands (Do/Make/Research): Neon-exclusive—Do executes actions, Make generates runnable web apps from natural language, Research searches and summarizes—callable directly from CLI.

• Testing and scraping: Agents run functional tests, scrape dynamic pages, fill forms end-to-end without hand-written Playwright for every flow.

• SKILLs auto-setup: Detects Claude Code and configures skills on setup—minimal integration glue.

• 38 CLI commands: Navigation, screenshot, click, type, evaluate JS, make apps, etc.—pipe-friendly Unix design.

• Session persistence: Save/load cookies, storage, and page state across agent restarts for long jobs.

3. How to Use

1. Requirements: Node.js ≥ 20, npm; Windows PowerShell 7+ recommended; Opera Neon installed and signed in (no extra OAuth).

2. Install:

   npm install -g opera-browser-cli && opera-browser-cli setup
   

   setup finds Neon, binds port 9224, configures Claude SKILLs (~30s).

3. Open a page:

   opera-browser-cli open https://operaneon.com
   

   Headless by default; --headless=false for UI.

4. Automate:

   opera-browser-cli snapshot --output screenshot.png
   opera-browser-cli make "create a simple to-do list app with HTML, CSS, and JavaScript"
   

   Use --help on subcommands; env vars OPERA_BROWSER_PATH, OPERA_PORT override defaults.

5. Best practices: Chain commands in shell scripts or agent SKILLs; session save for long runs; combine with Claude Code for full dev loops.

4. Pros and Cons

5. Comparison with Similar Tools

Selection guidance: Neon users → opera-browser-cli. Cross-browser or heavy scripts → Playwright/Puppeteer. Token-sensitive cloud agents → Vercel Agent Browser. Existing MCP → chrome-devtools-mcp.

6. Editor's Take

Clear positioning: browser as agent limb via local CLI, not just test harness. Zero-cloud design matters for enterprise privacy. Make for NL→app is a standout productivity hook.

Tradeoff is Neon lock-in—fine for Neon shops, less so for Chrome-default teams. Docs/community need growth; cross-browser support would widen appeal.

— −1 for single-browser dependency and immature ecosystem; strong in its niche.

7. Use Cases

• AI-driven regression tests: Login flows, assertions, screenshots from natural language.
• Dynamic scraping: Authenticated, JS-heavy sites with session persistence → CSV/JSON.
• Rapid prototypes: make generates and previews todo apps, dashboards, landing pages.
• Form automation: Bulk booking, applications, surveys with structured fills.
• Dev workflows with Claude Code: GitHub → clone → test → fix loops via SKILLs.

8. FAQ

Q: Chrome or Firefox?
A: Neon only today; CDP-adjacent but not adapted—use Playwright/Puppeteer otherwise.

Q: Node too old?
A: Require Node ≥ 20; upgrade via nvm or official installers.

Q: How Do/Make/Research work?
A: Call Neon's built-in AI engine—results to stdout or --output file.

Q: Claude Code integration?
A: Run setup; SKILLs auto-register for browser commands.

Q: Session restore scope?
A: Cookies, localStorage, page state saved; dynamic WebSockets may need reconnect.

9. Project Links

• GitHub: https://github.com/operasoftware/opera-browser-cli
• Protocol library: https://github.com/operasoftware/opera-devtools-mcp