playwright-interactive

To keep Playwright handles valid during iterative debugging, use a persistent session that maintains browser, context, page, and electronApp bindings across steps. This prevents the loss of references when running repeated tests without restarting your toolchain.

Your Playwright session disconnects because standard runtime instances terminate between commands, losing handle ownership. Bootstrapping a persistent session at project startup ensures bindings remain alive, preventing restart overhead and disconnection during UI changes.

Yes, you can debug local Electron apps with a persistent Playwright session. The session retains the electronApp and appWindow handles, allowing QA engineers to repeatedly run tests and capture visual evidence across iterations without restarting.

Yes, you need to enable js_repl to use a persistent Playwright session. Enabling js_repl allows the runtime to execute JavaScript bindings continuously, which is required to maintain page and context handles throughout your debugging workflow.

The best way to recover Playwright handles when ownership changes is to run a bootstrap command in your project directory. This refreshes the persistent session and safely restores valid bindings for your web and Electron app debugging.

A limitation of using a persistent Playwright session is that it requires explicit setup via js_repl and a bootstrap at project startup. If session ownership changes during QA, handles may invalidate unless manually refreshed through the recovery bootstrap.