D26. The full app supplies the browser for agents and tests (10 Oct 2026)

Users with the full app must not need to install Chrome or Edge to work themselves or with an agent. Default CLI/MCP rendering, layout checks, LMS tests and object gates use isolated workers of the app’s Electron executable. Standalone core installations retain the external browser launcher; external compatibility engines remain explicitly selectable. The editor and its project sessions never run test scripts.

Keep Playwright for pages, frames, interactions, initialization scripts and CDP. Adapt Electron window creation and context lifetime, using one temporary worker process per context to isolate storage, unload feature flags and stuck renderers. Record the actual engine/version, and separate object baselines by engine and OS. The same installed executable starts workers with the editor closed; the packaged CLI configures it directly, and the installed app registers it for standalone core discovery.

Electron 44.6.0’s macOS app archive omits libvulkan.dylib, which Chromium 151+ needs for SwiftShader. Packaging and development preparation obtain the exact matching library from Electron’s ChromeDriver archive, verified against the release’s SHA-256 checksums, and install it into the framework before signing. Its Electron/Chromium notices ship with the app. This adds no new npm runtime dependency and requires no download on users’ computers. Do not borrow libraries from installed Chrome or silently substitute GPU rendering for software visual tests.