Performance and resource usage
Is Oasis too heavy? How CPU, memory, disk, and network are used—for browsing, the assistant, and optional on-device features.
Browse short, product-grounded articles about Oasis Browser: what is available, how things work in the UI, and how capabilities fit together. For story-style deep-dives, see Oasis features.
Questions? Join the community or reach out to support.
Showing 1–9 of 88 articles
Is Oasis too heavy? How CPU, memory, disk, and network are used—for browsing, the assistant, and optional on-device features.
How Oasis training works, whether anonymous training leaves the device, privacy-first trainable browser, personalized vs anonymous modes, and daily bonus tokens.
What leaves the device (chat to model, voice, usage events) vs what stays local (IndexedDB chats, bookmarks, history, password vault, on-device embeddings).
How Oasis imports bookmarks, passwords, history, extensions, and autofill from Chrome, Edge, Safari, Brave, and more—and where that data lives relative to the cloud assistant.
Users can skip browser data import during onboarding (browser.oasis.onboarding.importOptOut).
In-panel checklist guides import from other browsers (Chrome, Edge, Safari, Brave), privacy framing, OAuth sign-in, and “first AI turn”—with dismiss and progress prefs.
How to permanently delete your Oasis account and what happens to your data.
Multiple light and dark themes for the assistant chrome (not only system theme); choice syncs via prefs / bridge.
See exactly what JSON Kahana receives from Oasis assistant interactions: default anonymized payloads vs opt-in personalization with user fields. Transparent, minimal data collection.