# playwright-cli v0.1.19 - Product: playwright-cli (https://whatsnew.fyi/product/playwright-cli) - Vendor: playwright-cli - Date: 2026-09-01 - Version: v0.1.19 - Original notes: https://github.com/microsoft/playwright-cli/releases/tag/v0.1.19 - Permalink: https://whatsnew.fyi/product/playwright-cli/releases/v0.1.19 What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'. --- - **added** — Add recording-start and recording-stop commands to record actions performed manually in the browser and return them as Playwright code - **fixed** — Cache the update check result so commands no longer pay a network round-trip to the npm registry on every invocation - **fixed** — Honor NO_UPDATE_NOTIFIER and CI environment variables in the installed-skill check and run at most once a day - **fixed** — Do not parse negative positional arguments as flags - **fixed** — Prevent the session daemon from opening a console window on Windows - **fixed** — Fix daemon socket path truncation on long workspace paths that left sessions stuck with EADDRINUSE - **fixed** — Add .playwright-cli/ to .gitignore when running install --skills since traces there can contain credentials - **fixed** — Correct the hint printed after attach to show -s instead of --s - **fixed** — Return the original screenshot bytes instead of silently downscaling them to model-specific limits - **fixed** — Drop the cached browser backend after close with a shared browser context so subsequent commands no longer fail - **fixed** — Allow tracing to be restarted after a failed tracing-stop instead of permanently producing broken archives - **fixed** — Infer the default codegen language from the environment - **fixed** — Do not clobber the chromiumSandbox setting from the config file - **fixed** — Honor --user-data-dir in extension mode - **fixed** — Do not treat orphaned browser preferences entries as an installed extension - **fixed** — Prevent state-save and state-load from hanging when the state contains IndexedDB and a page on that origin is open ##### What's New ###### New Commands - **`recording-start` / `recording-stop`** — Record actions that the user performs manually in the browser and return them as Playwright code. Useful when the user wants to demonstrate a flow instead of describing it ([#42359](https://github.com/microsoft/playwright/pull/42359)) ##### Bug Fixes - The update check result is cached again, so commands no longer pay a network round-trip to the npm registry on every invocation ([#454](https://github.com/microsoft/playwright-cli/pull/454)) - The installed-skill check honors `NO_UPDATE_NOTIFIER` / `CI` and runs at most once a day ([#447](https://github.com/microsoft/playwright-cli/pull/447)) - Negative positional arguments (e.g. `mousewheel` scroll-up deltas) are no longer parsed as flags ([#42333](https://github.com/microsoft/playwright/pull/42333)) - The session daemon no longer opens a console window on Windows ([#42155](https://github.com/microsoft/playwright/pull/42155)) - Long workspace paths no longer truncate the daemon socket path, which left sessions stuck with `EADDRINUSE` ([#42185](https://github.com/microsoft/playwright/pull/42185)) - `install --skills` adds `.playwright-cli/` to `.gitignore`, since traces there can contain credentials ([#42318](https://github.com/microsoft/playwright/pull/42318)) - The hint printed after `attach` shows `-s` instead of `--s` ([#42138](https://github.com/microsoft/playwright/pull/42138)) - `screenshot` returns the original screenshot bytes instead of silently downscaling them to model-specific limits ([#42406](https://github.com/microsoft/playwright/pull/42406)) - Drop the cached browser backend after `close` with a shared browser context, so subsequent commands no longer fail ([#42365](https://github.com/microsoft/playwright/pull/42365)) - Tracing can be restarted after a failed `tracing-stop` instead of permanently producing broken archives ([#42425](https://github.com/microsoft/playwright/pull/42425)) - The default codegen language is inferred from the environment ([#42150](https://github.com/microsoft/playwright/pull/42150)) - Do not clobber the `chromiumSandbox` setting from the config file ([#42288](https://github.com/microsoft/playwright/pull/42288)) - Honor `--user-data-dir` in extension mode ([#42190](https://github.com/microsoft/playwright/pull/42190)) - Do not treat orphaned browser preferences entries as an installed extension ([#42224](https://github.com/microsoft/playwright/pull/42224)) - `state-save` / `state-load` no longer hang when the state contains IndexedDB and a page on that origin is open ([#42260](https://github.com/microsoft/playwright/pull/42260))