The Remote Browser

Sessions

Open Browser under the Build group and start a new session. The live browser is embedded right in the page — type a URL and use it as you would any browser.

Sessions are private to you by default. They can be shared with the workspace so a teammate can drive the same browser, which is genuinely useful for walking someone through a process.

They cost money per minute while open, and they are reaped automatically after thirty minutes idle. Close a session when you are done rather than leaving it running — this is the single practical habit that keeps the feature cheap.

The browser runs on a connected Scrappy account, so connect Scrappy under Settings → Integrations first, with an API key carrying the browser scopes.

Saved logins

Here is the part worth reading carefully, because it is the security model.

You sign in to the site yourself, in the session, exactly as you normally would. The agent never sees or types your password.

Then you choose 'Save this login' and name it. What gets stored is not a password — it is the signed-in session, encrypted on the browser provider's side, usable only by you.

From then on, the agent can start sessions that are already signed in and work on your behalf on that site. That is the capability: it lets the agent operate a system that has no API without you ever handing it a credential.

Why a saved-login session cannot be shared

A session started from one of your saved logins can never be shared with the workspace.

The reason is direct: anyone you shared it with would be signed in as you. Not 'able to see what you see' — actually operating that site with your identity. There is no version of that which is safe to offer as a convenience toggle, so it is refused rather than warned about.

This is worth knowing so the restriction reads as protection rather than as a limitation. If you need a colleague to work on that site, they save their own login.

Revocation

Deleting a saved login revokes the stored session. That is the revocation path, and it cannot be undone.

Do it when you no longer need the agent working on that site, when you change your password there, or when anything about your account there changes.

And note the asymmetry with a normal credential: you cannot rotate a saved session, only delete and re-create it. So the maintenance shape is 'delete and sign in again' rather than 'update the password'.

Letting the agent use it

The remote browser is off for the agent by default. An admin turns on 'Remote browser' under Settings → AI Agent.

It is off because sessions spend real money per minute on your provider account — the same opt-in rule that governs every credit-spending feature in Kavanah.

Once on, ask the agent to do something on that site and it starts from your saved login. As with everything else, verify the outcome rather than the report the first few times.

And keep an eye on session lifetime. The single failure mode that costs money here is a session that was started and never closed, which the automatic reaping bounds but does not eliminate.