Long chats break when the model forgets what you said ten turns ago. Oasis uses optional structured session memory (internal nickname  Railroad ) to help follow-ups stay coherent.

Insight for other users: Session memory extracts structured facts across turns and re-injects them into later prompts so the assistant can remember details within your session and plan limits. You do not edit memory by hand. It updates as you chat.

What it is not: Memory is not a full backup of web pages. It is distilled text used to steer replies, not a copy of everything you browsed.

How to work with it:

Tracking protection is one of the main reasons people pick a Firefox-based browser. Oasis ships Enhanced Tracking Protection on by default.

Insight for other users: ETP blocks known trackers that follow you across the web: social buttons, cross-site scripts, fingerprinting, cryptomining, and many third-party analytics. It is not a full ad blocker. It targets tracking-related content while trying to keep core site features working.

What you get:

• Privacy: Less cross-site profiling and fewer third-party trackers loading in the background.

• Speed: Fewer tracking scripts can mean faster page loads and less wasted bandwidth.

• Control: Pick a protection level and add site exceptions when a trusted site breaks.

Hands-free voice breaks when the mic hears the assistant talking back. Oasis uses echo guard to reduce that.

Insight for other users: Echo guard adds a short quiet period before recording so your microphone is less likely to pick up the assistant s own voice from your speakers. It matters most in the voice orb loop when replies can be spoken (text-to-speech), not only typed in chat.

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.

Hey Product Hunt community

We ve been getting great questions from early testers and people considering Oasis as their daily browser. One keeps coming up after every iteration, and it s exactly the right question to ask:

You talk about history, bookmarks, and semantic search staying on-device while the assistant runs on cloud models. When onboarding says I can pull passwords over from my old browser where do those actually land? How are they encrypted? And is the vault fully walled off from anything that could train or power the assistant? @ferdi_sigona

The assistant panel should adapt to how you work, not force one layout for every task.

Insight for other users: Oasis lets you switch the assistant between a docked sidebar (attached to the window edge) and a floating overlay on top of the page. The product swaps layout without unloading your session when possible, so your chat and context stay in place.

Agentic browsers are exciting until the assistant closes the wrong tabs. We built a hard stop for irreversible actions.

Insight for other users: When Oasis plans something destructive (for example closing many tabs or deleting data), a confirmation modal blocks the browser until you approve or cancel. Nothing runs until you make an explicit choice.

Most AI browsers live or die in the composer: how fast you can ask the next question, and whether the product nudges you without getting in the way.

Insight for other users: In Oasis, the composer is the text box at the bottom of the assistant. You send follow-up messages in the same thread so context carries forward. When the thread is empty, you get a typewriter-style rotating hint with example prompts so you are not staring at a blank box. After you start chatting, inline suggestion chips can appear under the field. Tap one to send that prompt immediately.

If you use an AI browser all day, you need chat history that is fast, private on device, and easy to pick up where you left off. Here is how Oasis handles that today.

Insight for other users: When you are signed in, your assistant conversations are stored locally in the browser using IndexedDB, keyed to your Kahana user on that profile. You can list past threads, open one to load messages back into the timeline, start a New chat for a fresh session (other threads stay on disk), and delete old threads you no longer need. Saves are debounced so typing feels smooth without hammering storage on every keystroke.