Router and usage metadata
Assistant routing calls can consume tokens; usage may affect plan limits—point users to the token bar and account docs.
What this is
Before or alongside the main reply, Oasis may run routing steps that also consume tokens. Those counts roll into the same usage surfaces as chat tokens so your daily bar stays accurate.
How to use it
- Watch the token usage strip in the composer/header after long sessions.
- If you approach your plan cap, shorten prompts or disable voice-heavy loops.
- Router usage is expected for complex asks; simple chit-chat uses less.
Notes and limits
Exact weighting of router vs chat tokens is billing-side; trust the bar and account page.
Related topics
Related Documentation
Performance and resource usage
Is Oasis too heavy? How CPU, memory, disk, and network are used—for browsing, the assistant, and optional on-device features.
Training and bonus tokens
How Oasis training works, whether anonymous training leaves the device, privacy-first trainable browser, personalized vs anonymous modes, and daily bonus tokens.
Import data from other browsers
How Oasis imports bookmarks, passwords, history, extensions, and autofill from Chrome, Edge, Safari, Brave, and more—and where that data lives relative to the cloud assistant.
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.