domains / families / agent-tooling / electron-drive

electron-drive

separate

Launch the project's Electron app on a scratch profile and drive it: click, type, screenshot, run renderer or main-process code, read logs. Use to verify UI changes end to end.

When to use

• Use when you need to verify a UI change in the running Electron app.
• Use when reproducing a renderer or startup bug, or a failure that only
• Use when checking first-run, onboarding or settings screens.
• Use when exercising a feature end to end, including IPC through the preload
• Do not use it for web apps without Electron, or for multi-window flows (see

When not to use

• **One window.** Commands act on the first window that is not DevTools, and
• **One app at a time** per project. `start` refuses while one is running.
• **Windows:** run it as `node scripts/drive.mjs`. The process-tree kill that
• Requires `electron` and `playwright-core` 1.49+ in the project, and Node.js
• It does not replace the project's own test suite or a human check of

Skill page

Source