Describe the bug
On Windows, every call to npx hyperframes render causes a visible CMD/console
window to flash open and close for each shot rendered. When rendering a batch
(e.g. 78 shots), 78 console windows open sequentially, making the machine
completely unusable during the render. This happens even when HyperFrames is
called from a GUI application with no terminal involved, confirming the window
is being created inside HyperFrames itself.
Link to reproduction
Not applicable — this bug reproduces on every Windows machine with any render call, including a blank project created with: npx hyperframes init repro --non-interactive --example blank npx hyperframes render ./repro --format png No custom code is needed to trigger it. The console window appears on all Windows installs regardless of project content.
Steps to reproduce
- On Windows 11, run: npx hyperframes init repro --non-interactive --example blank
- Run: npx hyperframes render ./repro --format png
- Observe a CMD/console window flash open and close during render
- Run a batch of renders (multiple shots) — one console window opens per shot
Expected behavior
No console window should appear. Chrome headless should run silently in the background.
Actual behavior
A console window opens for every shot rendered, showing the path:
C:\Users<username>.cache\hyperframes\chrome\chrome-headless-shell\win64-152.0.7977.30\chrome-headless-shell-win64\chrome-headless-shell.exe
Suppressing the window from the calling side (Python subprocess CREATE_NO_WINDOW +
STARTUPINFO) has no effect because the window is opened by chrome-headless-shell.exe
which is spawned inside HyperFrames' own Node.js code.
Suspected fix: add windowsHide: true to the Node.js child_process.spawn() call
that launches chrome-headless-shell.exe.
Environment
hyperframes doctor
✓ Version 0.8.10 (latest)
✓ Node.js v22.19.0 (win32 x64)
✓ CPU 16 cores · AMD Ryzen 7 6800H with Radeon Graphics @ 3194MHz
✓ Memory 13.7 GB total · 3.0 GB available
✓ Chrome cache: C:\Users\Sulav Raj Thapa\.cache\hyperframes\chrome\chrome-headless-shell\win64-152.0.7977.30\chrome-headless-shell-win64\chrome-headless-shell.exe
✓ FFmpeg N-120424-g03b9180fe3-20250731
✓ Node environment non-TTY
Additional context
No response
Describe the bug
On Windows, every call to
npx hyperframes rendercauses a visible CMD/consolewindow to flash open and close for each shot rendered. When rendering a batch
(e.g. 78 shots), 78 console windows open sequentially, making the machine
completely unusable during the render. This happens even when HyperFrames is
called from a GUI application with no terminal involved, confirming the window
is being created inside HyperFrames itself.
Link to reproduction
Not applicable — this bug reproduces on every Windows machine with any render call, including a blank project created with: npx hyperframes init repro --non-interactive --example blank npx hyperframes render ./repro --format png No custom code is needed to trigger it. The console window appears on all Windows installs regardless of project content.
Steps to reproduce
Expected behavior
No console window should appear. Chrome headless should run silently in the background.
Actual behavior
A console window opens for every shot rendered, showing the path:
C:\Users<username>.cache\hyperframes\chrome\chrome-headless-shell\win64-152.0.7977.30\chrome-headless-shell-win64\chrome-headless-shell.exe
Suppressing the window from the calling side (Python subprocess CREATE_NO_WINDOW +
STARTUPINFO) has no effect because the window is opened by chrome-headless-shell.exe
which is spawned inside HyperFrames' own Node.js code.
Suspected fix: add
windowsHide: trueto the Node.js child_process.spawn() callthat launches chrome-headless-shell.exe.
Environment
Additional context
No response