Playwright interactive: persistent js_repl browser sessions for UI debugging
Debug local web or Electron apps with a persistent Playwright js_repl session — short pointer
- What
- Debug local web or Electron apps with a persistent Playwright js_repl session — short pointer
- Cost
- Free
- Needs
- the Codex agent runtime with js_repl enabled (~/.codex/config.toml) and sandboxing disabled (--sandbox danger-full-access) — understand that trade-off before starting; a local web or Electron project to debug; no license declared in the source repo — read it yourself before reusing its content
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — ⚠️ **Security warning** — this skill requires Codex with sandboxing DISABLED (`--sandbox danger-full-access`) and the `js_repl` feature enabled; only use it in a workspace you fully trust, and understand the trade-off before you start. A short pointer to @openai's playwright-interactive workflow: keep one persistent Playwright session alive across iterations to debug local web or Electron apps — write a QA inventory from the requirements and implemented behaviors first, run the bootstrap cell once, keep reusing the same handles for renderer reloads and app relaunches, run functional QA with normal user input plus a separate visual QA pass, capture screenshot evidence for every signed-off claim, and reset the kernel only as a recovery tool. Honest caveats: **no license declared in the repository — license unknown**, so this is a short fiche linking to the source, without reusing its content; built for the Codex agent runtime (`js_repl` in `~/.codex/config.toml`), not generic agents. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the Codex agent runtime with js_repl enabled (~/.codex/config.toml) and sandboxing disabled (--sandbox danger-full-access) — understand that trade-off before starting; a local web or Electron project to debug; no license declared in the source repo — read it yourself before reusing its content Install "Playwright interactive: persistent js_repl browser sessions for UI debugging" for me. Fetch the SKILL.md from the source repository into a temporary folder, review it for anything suspicious, and report in two or three sentences what the playwright-interactive workflow covers (persistent js_repl Playwright session, QA inventory, bootstrap cell, functional plus visual QA, screenshot evidence) so I can follow it in my own Codex workspace. Do not copy the workflow's content into my project — this is a reference lookup only. Repository: https://github.com/openai/skills/blob/main/skills/.curated/playwright-interactive/SKILL.md GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.