Oasis Browser Composer and Follow-ups
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.
How to use it:
Type a request and press Enter (or use the send control).
Click a chip when you want a one-tap follow-up.
Use Up arrow in the field to recall previous commands when that shortcut is enabled in your build.
A deliberate limit: Chips may fade out after several sends so the UI stays calm. You can always type anything manually.
Doc: https://kahana.co/docs/composer-and-follow-ups
Related: https://kahana.co/docs/chat-timeline | https://kahana.co/docs/insert-capabilities-overview | https://kahana.co/docs/voice-orb-hands-free
Questions we would love your take on:
Suggestion chips
Do one-tap chips speed you up, or do they feel like clutter after the first few messages?Empty state
Does the typewriter example prompt help you get started, or would you prefer a static placeholder or no animation at all?Follow-ups vs new chat
When do you start a new chat instead of a follow-up in the same thread? What signal should Oasis give you?Keyboard power users
Is Up arrow to recall prior commands enough? What else belongs in the composer (slash commands, @ tab, insert from page)?For the Oasis team
After a few sends, did chips disappearing feel right, or did you want them to stay visible longer?
Tell us what your ideal composer looks like. We are tuning this actively.
Replies