playwright-interactive

To maintain a persistent Playwright browser session for iterative UI debugging, you can use this Skill to keep Playwright handles active across multiple debugging iterations, allowing you to reload or relaunch applications quickly after code changes without losing the established context.

The best way to debug local Electron apps without constant restarts is using a persistent Playwright session through `js_repl`, which maintains browser and Electron interaction handles, facilitating fast iterative debugging and immediate visual feedback after code changes.

Yes, you need to disable sandboxing and enable `js_repl` for initial use to allow Playwright to establish persistent browser and Electron interaction handles for your local web application debugging and QA workflows.

Yes, you can perform both visual and functional QA testing in the same workflow by maintaining Playwright handles across debugging sessions, allowing you to quickly reload applications and immediately see the impact of your code changes.

Hot-reloading works with a persistent Playwright session by keeping the browser context active, so when you make code changes to your local web or Electron app, you can quickly reload the application and immediately see the visual and functional impact without restarting.