Attach to a tenant runtime
Associate browser state and artifacts with the tenant and managed runtime that owns the work.
Browser Sidecar
How do I use a browser sidecar for an AI agent?
Use Browser Sidecar as the server-side browser runtime for a managed AI agent by connecting its browser-enabled state, profile, session artifacts, and configuration to the tenant runtime. In Bewize, Browser Sidecar is the implemented isolation layer behind Wize Browser and managed web agents, while Hermes Hub provides the surrounding control plane.
A sidecar operating model
Keep the browser component close enough to the managed agent for useful work, but explicit enough to review its boundary and artifacts.
Expose controlled browser work
Use Wize Browser as the web-work surface for page context and reviewed browser actions.
Inspect the boundary
Review profiles, configuration, storage links, credentials, policies, and evidence as separate operational concerns.
Browser Sidecar FAQ
What does Browser Sidecar implement?
It implements a server-side browser isolation layer with tenant-scoped runtime state, browser profiles, configuration, and artifacts for managed web agents.
Is Browser Sidecar a standalone product browser?
No. It is the server-side browser boundary used with Wize Browser and managed agents.
Who governs the agent using the sidecar?
Hermes Hub manages the tenant runtime, policies, credentials, storage, schedules, and operational evidence around the browser work.
Discuss Browser Sidecar operations
Map the browser runtime, tenant boundary, managed agent, and review evidence for your web-work use case.
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.