Why you’d use it
The browser is Zo’s universal fallback. Most of the time, Zo has a faster, cleaner way to do what you’re asking, and you should reach for those first when they exist. The browser is for everything else: services that don’t have an integration, don’t ship a CLI, don’t expose an API, and just live behind a sign-in page on the open web. That’s the long tail of the web. Niche SaaS, internal tools, customer portals, partner dashboards, vendor admin panels, anywhere you’d normally open a tab and do it yourself. What the browser unlocks for Zo:
If you find yourself copy-pasting from a logged-in tab into Zo, that’s the moment to give Zo the browser instead.
When to use it
The browser is heavier than Zo’s other ways of reaching the web. It loads a real page, runs JavaScript, and uses your session, so it’s worth it only when nothing lighter will do. The rough hierarchy:
A good rule of thumb: if you could share the URL with someone who isn’t signed in and they’d see the same thing, use a web tool. If a service has its own integration or CLI, use that. The browser is the answer when you’d otherwise just open the tab yourself.