Oasis Browser
Trust beats surprise
The worst security UX is the one that trains people to click OK without reading. Oasis slows the moment that matters: when the browser is about to do something on your behalf that you would notice later.
When a suggestion graduates from chat into action (closing tabs, changing settings, or anything else you would care about if it happened while you looked away), Oasis can ask in plain language first. You get the human explanation and the machine-readable command line highlighted so power users and skeptics alike can sanity-check the same surface.
That pairing is intentional: narrative for speed-reading, syntax for precision. Approve, cancel, or ask for a different approach without playing whack-a-mole with silent failures.
The modal below is a mock. Real copy, icons, and which actions require confirmation evolve with product and policy, and some environments may route certain actions through your org's tooling instead.
In the documentation
Short reference articles that mirror how these capabilities show up in Oasis—timelines, prefs, and product behavior—not marketing fluff.
- guidesDestructive action confirmationsWhen the assistant proposes something irreversible, a confirmation modal blocks until the user approves or cancels.Read article →
- guidesGuest vs signed-inExplain which actions work signed out vs require sign-in (e.g. voice transcription and cloud routing per product rules).Read article →
- guidesPlain-English browser controlUsers describe goals in natural language; Oasis selects browser tools (tabs, windows, search, groups, split view, page summarize, etc.) instead of expecting slash commands.Read article →
Explore more Oasis capabilities
Deep dives on Oasis Browser and Oasis Enterprise: assistant, voice, governance, onboarding paths, and more.
10 capabilities