kareenosdocs

Cloud Browser

Open in Kareenos

A Chrome hosted for you (or on your own server) that stays logged in and works for agents while you are away — start it with one click, watch or take over in the live view.

On this page

What a Cloud Browser is

A Cloud Browser is a Chrome that Kareenos (or your own company's server) keeps running for you, with the Kareenos extension already connected to one of your projects. Your agents use it exactly like your own browser — but it keeps working while your laptop is closed, and it is the only browser agents can use when you talk to them over WhatsApp, Telegram, SMS or voice.

You never type a password to make it work: being logged into Kareenos is enough. The only thing you type is your login to third-party sites (LinkedIn, Gmail, a customer portal) — once, inside the live view, exactly as on your own computer. Those sessions stay in the Cloud Browser's profile afterwards.

Start, pause, resume, delete

Open Connect Extension (or the cloud chip in the Agent Runner), pick the project and click Start. Within a minute the status shows Running and the live view can be opened. Pause frees the compute but keeps everything that makes the browser yours; Resume brings the same browser back. Idle browsers pause by themselves after the time set in the project's settings. Delete destroys the browser and permanently wipes its profile and every website session in it.

Watching and taking over

The live view streams the browser into Kareenos. You watch the agent work; when a page needs you (a login, a 2FA code, a CAPTCHA, a judgment call), click Take control, do it, then Hand back. While you hold control the agent waits — it will tell you so in the chat.

How agents choose a browser

Each project decides under K Projects → Edit → Cloud Browser: Auto (your own Chrome when it is connected, otherwise the Cloud Browser), Cloud Browser always, or Own computer only. From messaging channels only the Cloud Browser is ever used. In the Agent Runner the cloud chip lets you pin one run to the Cloud Browser regardless.

Your data and sessions

The profile — cookies and logged-in sessions — lives in the Cloud Browser only. While paused it is stored encrypted with a key that is deleted the moment you delete the browser, so nothing can be recovered afterwards. The live view can be opened only from your own Kareenos login; no password is ever stored or asked for.

Hosting it yourself

Companies can run the K-Desktop runtime on their own servers (Settings → K-Desktop Hosts). Browsers then run inside their network, profiles never leave it, and everything still works from Kareenos exactly as in the cloud. The runtime dials out to Kareenos; nothing on the server listens.

Troubleshooting

  • "Cloud Browser is not enabled for this project" — turn it on in the project's settings.
  • Start fails with "no node has free capacity" — the cloud pool is full, retry in a minute; self-hosted accounts must have a node online.
  • An agent answers "resuming — retry" — the paused browser is waking up; ask again in ~20 seconds.
  • The live view says the ticket expired — reopen it from Kareenos; the link is single-use and lives 60 seconds.