Kahana / Supabase sign-in
Assistant features tied to billing, voice, and history use signed-in Kahana identity (OAuth/email through the in-panel Auth UI and Supabase session).
What this is
Oasis uses Kahana (backed by Supabase) for identity. Signing in unlocks cloud-backed assistant features: usage limits, voice transcription, chat sync to IndexedDB per user, and more.
How to use it
- Open the assistant and choose Sign in or Create account.
- Prefer OAuth (Google, Apple, etc.) when offered for fewer passwords.
- Stay signed in for the best voice and quota experience; session refresh is automatic when possible.
Notes and limits
If cookies or storage are blocked aggressively, auth may fail—allow first-party storage for the profile.
Related topics
Related Documentation
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.
Training and bonus tokens
How Oasis training works, whether anonymous training leaves the device, privacy-first trainable browser, personalized vs anonymous modes, and daily bonus tokens.
Import data from other browsers
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.
About the Author
I'm the CEO of Kahana, bringing a unique perspective from my management consulting experience at Clarkston Consulting and biomedical engineering background from Duke University. I'm focused on making the future of work more elegant through innovative technology solutions that prioritize user well-being and productivity.