Oasis Browser: Guest vs. Signed-in
Not every AI browser feature should require an account on day one. Oasis still needs a clear line between guest and signed-in so people know what to expect.
Insight for other users:
Guests can try limited assistant flows (good for a quick taste before you commit).
Signed-in users get the full experience: cloud routing, voice transcription, chat history in IndexedDB keyed to your user, and the plan-aware daily token bar.
Typical sign-in moments: Voice hits a “please sign in” gate. You reach a usage or billing limit. You want history and quota to follow your Kahana account.
How to navigate it:
Browse or try constrained demos signed out if the product allows it.
Open the in-panel Auth screen and sign in when prompted.
Sign out on shared machines. The UI should return to auth instead of a stale guest layout (see our welcome-back doc). Some local data (hints, training progress) may remain until you clear browser storage.
Note: Exact guest allowances can change with product policy. Trust the in-product message you see at that moment over any static summary.
Doc: https://kahana.co/docs/guest-vs-signed-in
Related: https://kahana.co/docs/kahana-supabase-sign-in | https://kahana.co/docs/welcome-back-after-sign-out | https://kahana.co/docs/chat-history-indexeddb
Questions we would love your take on:
Try before sign-up
How much should guests get without an account before it feels like a crippled demo?Sign-in prompts
When should Oasis block vs gently nudge (voice, long chat, training tokens)?Shared computers
Is sign-out plus return to auth enough, or do you want automatic local history wipe on sign-out?OAuth vs email
What sign-in method do you prefer inside the browser panel?For the Oasis team
Did you hit a feature that required sign-in sooner than you expected? Which guest capability mattered most?
Tell us what “guest mode” should mean for a privacy-first browser.
Replies