Guest vs signed-in
Explain which actions work signed out vs require sign-in (e.g. voice transcription and cloud routing per product rules).
What this is
Guests can try limited assistant flows. Signed-in users get full routing, voice, persisted chat history keyed to your user id, and plan-aware token display.
How to use it
- Use the assistant signed out to read marketing copy or try constrained demos.
- Sign in from the Auth screen when you hit a paywall or “please sign in” message.
- Sign out returns you to auth; local-only artifacts may remain until cleared.
Notes and limits
Exact guest allowances change with product policy; trust in-product messages over static docs.
Related topics
Related Documentation
Active tool indicator
Shows when a browser “tool” action is in progress so users know the assistant is acting on the browser, not only typing text.
Assistant themes
Multiple light and dark themes for the assistant chrome (not only system theme); choice syncs via prefs / bridge.
Busy / streaming state
Visual feedback while the model or tools are working (AssistantBusyBar, streaming into the timeline).
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.