Opera Neon is a separate browser from Opera built around AI agents. Its own agent, Neon Do, browses, fills forms and completes tasks inside the user's logged-in sessions, while Neon Make splits bigger jobs among agents running in a cloud virtual machine that keeps working when the user is offline. Opera announced Neon with a waitlist on May 29, 2025, rolled out paid early access on Sep 30, 2025 and opened it to everyone on Dec 11, 2025 at $19.90 a month.
Two later changes matter more for site owners than Neon's own agents. On Mar 31, 2026 Opera released an MCP Connector that lets outside AI clients, including Claude, ChatGPT, Lovable, OpenClaw and n8n, drive Neon inside the user's live, logged-in browser. On Aug 14, 2026 the browser went free on Windows and macOS, and outside agents can now connect over MCP or a command-line tool at no cost, while Neon's own agents still need the paid Standard plan. Opera hasn't published user numbers, but the effect is that any agent can borrow a real browser on a real person's machine.
How Opera Neon shows up on your site
Neon Do and MCP-driven sessions run on the user's own computer, with their cookies and home IP, and Opera documents no agent marker for them. MIT's AI Agent Index lists Neon as using regular browser user agent strings that don't distinguish it from ordinary browsers. Neon Make is the exception, since it runs in a cloud virtual machine, but Opera hasn't said which cloud provider hosts it or published any IP ranges.
| Check | What Opera Neon does |
|---|---|
| User agent | Regular browser string, per MIT's AI Agent Index |
| Web Bot Auth signature | None published by Opera |
| IP ranges | None. User's IP locally, cloud provider unpublished |
| robots.txt | Not documented |
Why Opera Neon is hard to detect
Neon is a real Chromium-based browser on a real person's computer, so network checks see a normal customer with a residential IP and valid cookies. There is no user agent token, signature or IP list to match, and the person can pause the agent or take over at any point, which means one session can mix human and agent turns.
The MCP Connector makes it harder still. Agent frameworks such as OpenClaw usually leave automation traces when they run their own browser, but when they drive Neon over MCP, their clicks happen inside a real, logged-in browser on a home connection, which hides most of those traces. What stays visible is how the input arrives, such as fields filled instantly and no mouse paths between clicks. Neon Make may come from datacenter IPs, though without a published provider that can't be turned into a rule.
How Verisoul detects Opera Neon
Verisoul does not name Opera Neon yet, because it declares no identity and signs nothing, and we only name an agent when we can confirm which one it is. What Verisoul does pick up is the automated input and page flow while an agent is driving, whether that agent is Neon Do or an outside client over MCP, and those raise the session's bot score while the agent field stays empty.
"agent": nullbot_scoreruns from 0 to 1 and rises as the session looks automated, so 0.97 means the input and page flow look like softwareagentisnullbecause Neon does not declare or sign an identity, so Verisoul does not attach a name- The device is a real Chromium-based browser and local sessions use the user's own IP, so the score depends mostly on how the browser is driven
If Opera adds a declared identity, Neon will get its own entry in Agent Atlas. The AI agent detection docs explain how bot score and the agent field work together.
- 01An agent connects to Neon over MCP
- 02It drives the user's logged-in browser
- 03Your site sees a home IP and cookies
- 04Verisoul scores the automated input
How to detect Opera Neon step by step
- Add the Verisoul SDK to sign-up, login, checkout and payout pages, following the AI agent detection docs
- Treat a high
bot_scorewith a nullagentas a possible Neon or MCP-driven session - Write a stricter rule at sign-up, where outside agents driving Neon can create accounts from residential IPs
- Send payouts and account changes in automated sessions to review, and check the queue weekly
Should you block Opera Neon?
For an established customer, usually not. Neon Do typically acts for the logged-in account holder, so browsing and checkout can stay open, with payouts and account changes sent to review when the bot score is high.
Sign-up is where to be stricter. Because outside agents like OpenClaw can drive Neon for free from a real home connection, an automated sign-up from Neon looks much more like a new person than one from a cloud browser does, and a high bot score at account creation deserves review or a block.