Tenant browser profile
Browser profile paths are represented in tenant runtime environment and artifacts.
Browser Sidecar
Isolate browser work for managed AI agents
Browser Sidecar is the implemented server-side browser isolation component of Wize Browser. Current evidence is Hermes Hub tenant browser state, Camofox/runtime browser configuration, and browser artifacts scoped to a tenant boundary; public assistant workflows and process mining remain directional.
What is Browser Sidecar?
Browser Sidecar gives Wize Browser and managed agents a tenant-scoped browser runtime instead of a shared unmanaged browser profile. Hermes Hub proof shows browser-enabled tenant runtime metadata, Camofox URL, browser profile paths, browser auth artifacts, and storage/workspace links scoped under tenant runtime boundaries.
Camofox/runtime browser state
The proofed runtime metadata includes Camofox URL and browser-enabled state.
Tenant isolation
Browser state, workspace, storage root, and runtime artifacts stay tied to the selected tenant.
Operational outcome
Browser agents can be operated with a concrete tenant boundary instead of a shared, unmanaged browser profile.
Directional: Chrome extension and workflow assistant
The public user-facing Chrome extension and process-mining/browser-workflow assistant remain directional. They should be described as target UX until implementation evidence exists.
Browser assistance direction
Assistance stays visible and reviewed.
Employee browserPage contextAI browser assistantVisible actionReviewAutomation candidate
AI browser assistant
Target UX: page-aware help while an employee works in their own browser.
AI browser automation
Automation should be promoted only after repeated work is understood and reviewed.
AI web agent
Browser agents inherit tenant sidecar boundaries when running under Hermes Hub.
Process-mining boundary
Workflow discovery and automation suggestions stay directional until there is source-backed implementation evidence.
Operational outcome
Browser work can move from isolated runtime proof toward visible employee assistance without overstating what is already shipped.
Discuss browser agent boundaries
Map tenant browser isolation, runtime browser state, and future browser-assistance workflows.
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.