What's going on?
On Windows every CLI session opens an empty console window next to the browser. I expected only the browser window.
`playwright-cli -s=mysession open https://example.com`
The window stays until the session is closed, and there is one per session name rather than one per command, so it looks like the daemon rather than the individual calls.
cli-client/session.ts spawns the daemon detached without windowsHide: true. node.exe is console-subsystem, so Windows hands it a console; on Linux detached is just setsid and nothing shows. Same in cli-client/program.ts and backend/devtools.ts.
There is history on this flag, but on a different spawn: processLauncher.ts got windowsHide in #38776 and it was reverted in #39994 because it also hid the Inspector and UI mode. That cannot happen here, since these spawns only start background daemons and none of them is a window a user is meant to see.
Happy to send a PR. Windows 11, Node 24, Chrome channel.
Version
@playwright/cli 0.1.18
What's going on?
On Windows every CLI session opens an empty console window next to the browser. I expected only the browser window.
The window stays until the session is closed, and there is one per session name rather than one per command, so it looks like the daemon rather than the individual calls.
cli-client/session.tsspawns the daemon detached withoutwindowsHide: true. node.exe is console-subsystem, so Windows hands it a console; on Linuxdetachedis just setsid and nothing shows. Same incli-client/program.tsandbackend/devtools.ts.There is history on this flag, but on a different spawn:
processLauncher.tsgotwindowsHidein #38776 and it was reverted in #39994 because it also hid the Inspector and UI mode. That cannot happen here, since these spawns only start background daemons and none of them is a window a user is meant to see.Happy to send a PR. Windows 11, Node 24, Chrome channel.
Version
@playwright/cli 0.1.18