Browser context is the central advantage
Opera AI's strongest feature is not a unique foundation model. It is the position of the assistant inside the browser. The current product page says the assistant can understand the active webpage or an entire Tab Island, while the R3 release explains that this context is deliberately scoped so the system does not automatically mix unrelated browsing contexts.12
That design can remove a large amount of copy-and-paste work. A user reading a long article can ask for a summary without pasting the text; a researcher can work across a grouped set of tabs; a shopper can ask questions about the page already open; and a user can disable page access before sending the first prompt when the context is not appropriate.12
The current product page also exposes a practical control that matters more than broad privacy slogans: page access can be switched off in the Opera AI interface, after which the assistant will not read the webpage or tab content for its answer.1 Opera AI itself can also be disabled completely in browser settings.
The rebuilt 2026 assistant is broader than the old Aria chatbot
Opera's January 2026 R3 release describes the current assistant as a rebuilt browser AI using architecture derived from Opera Neon's agentic engine. Opera says this architecture improved response speed by about 20% and added better page/Tab Island context, YouTube understanding and wallpaper generation.2
The current feature surface adds file analysis, image understanding and generation, video summarization/translation, up-to-date web answers and support for more than 50 languages.13 On Android, Opera documents contextual page answers, page summaries, image understanding, voice input/output, document/PDF analysis and wallpaper generation.4
The assistant therefore covers a useful middle ground between a conventional chatbot and a fully autonomous browser agent. It can reason over the browsing context presented to it, but the mainstream Opera AI experience should not be conflated with every experimental or premium agentic feature Opera has demonstrated elsewhere.
Agentic claims need careful product separation
Opera experimented with Browser Operator in 2025, an agent that could navigate pages and perform multi-step browsing tasks. The Register tested the preview and found it slow and only partly competent, while also noting that users could intervene and that final purchases still required authorization.5 That evidence is historically useful but does not test the rebuilt 2026 Opera AI assistant.
Similarly, 2025 AI Tab Commands let Aria organize or close tabs from natural-language instructions. TechRadar described the feature as useful for heavy tab users and highlighted Opera's claim that tab metadata remained local while only the command text went to the server.6 Those capabilities show the direction of travel, but they belong to the predecessor-era product and are not transferred automatically into a score for current Opera AI.
Opera's wider browser strategy now also includes Browser Connector, which can let external assistants such as ChatGPT or Claude receive live Opera context through MCP in supported/experimental surfaces. That makes Opera's browser increasingly an AI integration layer rather than a single-assistant silo, but Browser Connector should be evaluated separately from the native Opera AI assistant.7
Current independent testing is encouraging but insufficient
A useful current external test comes from AIMultiple's 2026 AI-browser comparison. Its testers reported that page context was broken in their original Opera test and explicitly recommended re-testing after Opera One R3, which Opera says rebuilt the AI engine and context behavior.8 This is useful because it identifies a concrete reliability dimension instead of repeating vendor feature claims.
It is not enough to conclude that page context is currently broken: the test and the R3 rebuild straddle a product change. The fair conclusion is narrower. Contextual browsing is Opera AI's defining capability, and there is not yet enough current independent re-testing to establish how reliably it works across difficult pages, long Tab Islands, dynamic sites and mixed media.