playwright-interactive

You can keep a persistent Playwright QA session by enabling js_repl, installing Playwright, and starting Codex with sandbox settings configured, which maintains stable handles across web and Electron contexts without restarting.

Yes, you can debug local Electron windows without restarting handles by using a persistent Playwright QA session. This approach supports cross-workspace usage and repeated verification across both web contexts and native Electron windows for iterative workflows.

You need to enable js_repl and configure appropriate sandbox settings in your Codex workspace before starting. These prerequisites ensure the persistent Playwright session can install correctly and maintain stable handles across local web or Electron apps.

Yes, the persistent Playwright approach works for both local web renderers and native Electron windows. It provides structured session reuse across both contexts, allowing you to perform iterative functional and visual QA without losing handle state.

Playwright sessions restart and lose handles when not configured for persistence. By enabling js_repl and launching Codex with proper sandbox settings, you can maintain a persistent session that eliminates friction and keeps handles alive across iterations.