Tenant browser profile
Keep profile paths and browser session state represented inside the tenant runtime environment.
Browser isolation
How do I isolate browser sessions for AI agents?
Isolate browser sessions for AI agents by assigning browser profiles, runtime state, and artifacts to the tenant boundary that owns the agent. In Bewize, Browser Sidecar is the implemented server-side boundary for Wize Browser and managed agents; it does not by itself promise universal security or compliance.
The isolation boundary to inspect
A useful review follows browser state from the managed agent to its tenant runtime.
Scoped artifacts
Treat authentication artifacts, storage, and workspace links as tenant-scoped runtime evidence.
Managed control plane
Connect browser work to Hermes Hub identity, policy, credentials, and operational review.
Browser-session isolation FAQ
What should be isolated for an AI-agent browser session?
Review the browser profile, runtime state, authentication artifacts, storage, and workspace links associated with the tenant runtime.
Is Wize Browser a standalone browser?
No. Wize Browser is a Chrome MV3 extension plus an isolated server browser component called Browser Sidecar.
Does isolation guarantee compliance?
No. Browser Sidecar provides a named tenant runtime boundary; compliance and security conclusions require the buyer’s own review.
Review browser boundaries
Map browser profiles, credentials, artifacts, and review controls to your tenant operating model.
Architecture conversation
Tell us what your team needs to control
Share your deployment boundary, number of agents, work surfaces, and governance requirements. We will reply by email to arrange a focused technical discussion.
Email the Bewize teamThis opens your email application. Read our Privacy Policy.