Oasis Browser
An assistant that reads the room (your tabs)
Work moved into the browser; the assistant should meet you there, not in a disconnected chat bubble that pretends every page is the same blank slate.
The panel is deliberately boring in the good way: a timeline you can skim, a composer that stays put, busy states when a tool is actually running, and read-aloud plus feedback on the latest reply when you want the answer in your ears, or want to thumbs-down a miss without breaking flow.
For how the conversation timeline behaves in the product, see the Chat timeline article in the documentation library.
The skills gallery is a tasting menu, not a contract. Search and filters show how we think about discoverability; your catalog, labels, and guardrails will follow what ships in your build and what your admins allow.
If a command would do something sensitive in the browser, confirmations (covered on their own page) are the other half of the story: speed when it is safe, friction when it is not.
Looping demo (illustrative UI, not a full skills catalog)
Independent review
“Semantic history search is the feature I find most compelling. Instead of searching your history with exact keywords, you can ask in plain language and the assistant searches by meaning rather than exact text match.”
From Your Tech Compass review of Oasis Browser assistant capabilities
In the documentation
Short reference articles that mirror how these capabilities show up in Oasis—timelines, prefs, and product behavior—not marketing fluff.
- guidesChat timelineConversation view with Markdown rendering for assistant replies (including legacy delimiter fallbacks where needed).Read article →
- guidesComposer and follow-upsText area for messages, inline suggestion chips, rotating example prompts (typewriter empty state), and “send follow-up” behavior.Read article →
- guidesBusy / streaming stateVisual feedback while the model or tools are working (AssistantBusyBar, streaming into the timeline).Read article →
- guidesChat history (IndexedDB)Conversations are stored per user in the browser (IndexedDB): list, open, start new chat, delete past threads, with debounced save.Read article →
- guidesInsert capabilities overviewAction to paste the structured “What Oasis can do in this build” Markdown (sections for web search, Q&A, summarize, tabs, groups, split view, memory/history, support links).Read article →
- guidesActive tool indicatorShows when a browser “tool” action is in progress so users know the assistant is acting on the browser, not only typing text.Read article →
Explore more Oasis capabilities
Deep dives on Oasis Browser and Oasis Enterprise: assistant, voice, governance, onboarding paths, and more.
10 capabilities