Some work only exists behind a screen. A supplier catalogue with no API. A form that has to be filled in. A dashboard you're already signed in to that offers no export. A comparison that means opening nine tabs and reading all of them.
Cloud Browser gives Okou a live browser window for exactly that work. Available on every plan.
What it's for
- Comparison and collection. Pull details from several pages into one table — pricing, specs, availability — where a search result alone isn't enough.
- Sites with no API. Portals, internal tools, government and supplier sites that were never meant to be automated.
- Filling things in. Web forms, applications, and multi-step flows.
- Signed-in work. Sign in once in the browser window and Okou can keep working inside that session.
Watching and taking over
The browser isn't a black box. Open it whenever you want to see what Okou is doing, guide it, or take the keyboard yourself — sign in on a page you'd rather Okou didn't handle, clear a CAPTCHA, or correct a wrong turn — then hand it back and let the run continue.
The browser opens in the same side panel as artifacts, email drafts, and automations, so it sits beside the conversation rather than replacing it.
It belongs to the conversation
Browser access is scoped to the chat where you enabled it. New chats start with Cloud Browser available, and you can turn it off per chat or point the work at a connected computer instead. That keeps each task's browsing, its messages, and its results together.
A session outlives a single run, so a follow-up in the same chat can pick up the window where the last run left it, including whatever you were signed in to.
Computer use: your desktop instead of a cloud browser
Cloud Browser runs on Okou's machine. Computer use is the other option: connect a desktop of your own and let an agent operate the applications on it — the right choice when the work involves a native application, a VPN-only system, or software that can't run in a browser at all.
Both are available on every plan. Pick per chat: a cloud browser when the work is on the public web, a connected computer when the work is on your machine.
Practical notes
- Slower than an API. When a connector or a managed service covers the same job, it will be faster, cheaper, and more reliable. Reach for the browser when they don't.
- Page content is untrusted. What Okou reads on a page is source material, not instructions. A hostile page can't redirect a run.
- Watch the first one. As with automations, the first run on an unfamiliar site is worth watching end to end before you put it on a schedule.
- Sign-ins are yours. If you sign in inside the browser window, treat that session the way you'd treat a shared screen: fine for the task at hand, worth closing out when the work is done.
What's next
- See Managed web services for search and scraping, which handle most research without a browser.
- See Connectors for the API-backed path.
- See Workflows for capturing a browser procedure once it works.