`opera-browser-cli`: Faster, more precise and less token-hungry!
Opera Browser CLI puts Opera Neon's full browser intelligence directly inside Claude Code, Codex, Cursor, or your terminal.
If you want to jump straight into the setup, please head to the README.md.
Opera Browser CLI in Action: Debugging and Full QA With Claude Code
Real access to a headed browser as a logged in user
Watch it track down bugs, run complete QA simulations, and fix every issue it finds by itself, without a single manual click. This is your AI coding agent with real access to a headed browser as a logged in user.
FAQ
The Opera CLI (Command Line Interface) makes it possible for you and your AI client of choice to use Opera Neon through a command line interface such as Claude Code, Cursor or Codex. You can also use your terminal, PowerShell and/or Command Prompt etc.
Check out this article for more information.
Make sure you have Opera Neon installed and that you are logged in.
Then open your terminal and do the following:
- npm install -g opera-browser-cli (which will also install the opera-devtools-mcp package)
- Run opera-browser-cli setup and follow the steps
You’ll need Node.js ≥ 20 and npm to install this
Important: for more details on how the actual opera-browser-cli works, head to the README.md
As a final remark, consider that the setup scripts install SKILLs for Claude Code by default.
Opera CLI is included in the Opera Neon subscription ($19.90/month). No extra setup or cost.
The opera-browser-cli architecture allows us to reduce latency and token overhead to the process, and it has access to more tools available to it.
So, because opera-browser-cli is a command-line wrapper around opera-devtools, it has access to several more tools – including the agentic ones – that make it faster, more precise when taking action within the browser, and less token-hungry.
Additionally, most of the use cases for MCP Connector are covered by opera-browser-cli, only missing those in which a cloud-hosted MCP client needs to use Opera Neon. opera-browser-cli runs on your machine and binds to a local port (default 9224). It is not reachable from cloud-hosted MCP clients.
Finally, opera-browser-cli sets automation flags, telling visited pages that they are being driven by automation. This can be turned off via environment variables. Neon Do and Research operate without the flag regardless, since they use Neon's internal agent path rather than the Chrome Devtools Protocol.
Using CLI with Opera Neon you will be browsing the internet in a headed browser as a logged in user. Also in Opera Neon you have more AI-features than other browsers, which is then exposed in opera-browser-cli.
Get Opera Neon now
How to get started
Download
Install Opera Neon and log in.
Connect
Already use agents? Connect them to Neon through MCP or CLI.
Activate
Subscribe to Neon to activate agentic functionalities and top world LLMs.
See everything Neon unlocks for $19.90/month here