playwright-interactive

To maintain a persistent Playwright session, enable js_repl in Codex config and run with sandbox settings permitting browser automation. This reuses handles, contexts, and pages across iterations for local web and Electron debugging.

Yes, you can reuse browser contexts and windows when debugging Electron apps. The session preserves these handles across runs and reloads, enabling deterministic QA workflows without restarting tooling or losing state.

The best way to speed up iterative UI debugging is using a persistent Playwright session. It eliminates the need to restart tooling by reusing handles and contexts across runs, enabling fast and deterministic QA cycles.

Yes, persistent Playwright debugging requires specific sandbox settings. You must run with sandbox configurations that explicitly permit browser automation during debugging alongside enabling js_repl in Codex config.

You lose browser handles because standard Playwright sessions are stateless upon restart. Using a persistent session resolves this by maintaining handles, contexts, and windows across iterations, preventing state loss during QA checks.

You need a persistent Playwright session for web and Electron targets when performing fast iterative UI debugging. It is required for deterministic replays and workflows that must reuse handles without losing state across runs.