A cloud browser runs its browser engine and session on a remote server. The user or agent controls it over a network connection while page loading, scripts, cookies and browser state are handled in the hosted environment. This differs from a local extension that controls a browser on the user's own device.
For artificial intelligence workflows, a cloud browser can continue operating when the user's computer is unavailable. Its usefulness depends on reliable session persistence, authentication controls, site compatibility, security and clear limits on what the remote agent may do.
Acronyms and aliases
remote browser synonymhosted browser variant
Related terms
Frequently asked questions
How is a cloud browser different from a local browser extension?
A cloud browser runs remotely and can continue without the user's device, while a local extension normally requires the local browser and computer to remain available.
Can a cloud browser keep a user signed in?
It can retain an authenticated session when designed to do so, but credentials and session data must be protected with strict access and lifecycle controls.
