Setting the file. One moment.
Subchapter 20.5
references/doctor-browser.mdMarkdown3 KBView on GitHub
Environment diagnosis and bundled-Chrome management. Run these first when a render or preview fails.
Runs independent checks and reports each as ok/warn/fail:
render --dockerRun doctor first when:
render fails with a Chrome or FFmpeg error.preview opens but the composition fails to load.Common issues:
brew install ffmpeg (macOS) or your package manager.npx hyperframes browser ensure.--workers, or use --quality draft.workspace-write) block Chromium’s Mach port bootstrap
(MachPortRendezvous; openai/codex#21292), so every Chrome — bundled, system, or
headless shell — dies at startup. This is a host-level block, not a HyperFrames or
Chrome install problem: compile checks and audio still pass, only rendering is
unavailable. State the blocker and deliver the checked composition; render outside the
sandbox or via render --docker / cloud rendering where available. Do not build a
substitute rasterizer (magick/PIL/SVG frame pipelines) — on a blocked-browser host
the deliverable IS the checked composition plus this blocker note, and rendering is
handed to --docker, cloud, or the user. Write your final summary the moment the
blocker is identified, BEFORE any optional fallback work: a later session failure must
not erase the report of work already done.npx hyperframes browser ensure # find or download the pinned Chrome
npx hyperframes browser path # print the browser executable path (for scripting)
npx hyperframes browser clear # remove the cached Chrome downloadManage the Chrome build HyperFrames uses for rendering. The pinned version exists because pixel output drifts across Chrome versions — using the bundled build keeps rendered output reproducible across machines.
Use path to embed the binary in scripts: $(npx hyperframes browser path).