Chromium WebEngine vs BrowserWindow

🌐 Browser Automation • javascript • v1 •

Understanding the difference between Electron's core UI window (BrowserWindow) and the isolated tabs in the Browser Farm (BrowserView) is crucial for building secure and scalable Flowork apps.

Building The Farm

A common point of confusion is how Flowork manages the browser windows it automates versus the window the user is actually looking at.

The Shell: BrowserWindow

There is exactly one primary BrowserWindow. This is the user interface. It runs Vue, reads the FloworkData/ directory via the preload bridge, and displays the App Store.

The Farm: BrowserView

A BrowserView is an embedded Chromium renderer.

When an AI agent says "open twitter.com and log in," it does not launch an entirely new application window. Inside the primary Electron process, Flowork spawns a BrowserView.

This view acts as an isolated, headless (or optionally visible) tab.

1. Security Constraints: The view has no IPC integration with the Go Engine. If the AI navigated to a malicious website, that script is completely trapped inside the Chromium sandbox with zero knowledge of Flowork OS. 2. Stealth Constraints: The view is injected with the stealth-preload.js configuration. It fakes its fingerprint, altering WebGL noise and claiming a different user-agent.

INDEXED KEYWORDS:
electron webengine browserwindow browserview sandboxing