issues installing on openclaw due to HeadlessExperimental.beginFrame #294

...the code already has a built-in escape hatch: PRODUCER_FORCE_SCREENSHOT=true forces screenshot mode and bypasses the broken HeadlessExperimental.beginFrame path. Let me verify and create a patched wrapper.


Now I understand the full picture. Let me test that PRODUCER_FORCE_SCREENSHOT=true forces screenshot mode:


Confirmed — Chromium 147 doesn't support HeadlessExperimental.beginFrame. The fix is to force screenshot mode. I can do this cleanly with an env var, but the proper patch is to change the default so it auto-detects correctly.


It works with PRODUCER_FORCE_SCREENSHOT=true. Now let me make that the permanent default for this server.


Now I need to make forceScreenshot: true the default for this server. Let me find where the config is stored:


PRODUCER_FORCE_SCREENSHOT=true works. Now I'll make it the permanent default so every render uses screenshot mode:


Clean render with screenshot capture. Let me add a note to the skill so this server-specific override is documented for future sessions:


Now let me add a note to the hyperframes skill:


Now update the CLI skill to document the screenshot-mode note:


All good. Here's what was done:

Installation

• npx skills add heygen-com/hyperframes pulled all 5 hyperframes skills into ~/.openclaw/workspace/.agents/skills/
• npm install -g hyperframes installed the CLI globally (needed for the hyperframes binary and bundled engine code)

Patch applied
The capture engine defaults to forceScreenshot: false, which on Linux ARM64 with a system Chromium tries to use HeadlessExperimental.beginFrame — a protocol removed in Chromium 147. One line in the bundled engine was patched:
// BEFORE (in DEFAULT_CONFIG2):
forceScreenshot: envBool("PRODUCER_FORCE_SCREENSHOT", false),

// AFTER:
forceScreenshot: envBool("PRODUCER_FORCE_SCREENSHOT", true),
This makes screenshot capture the default on this machine. The PRODUCER_FORCE_SCREENSHOT env var still works as an override if needed....