Skip to content

fix(browse): respect GSTACK_CHROMIUM_PATH in headless mode#1035

Open
mvanhorn wants to merge 1 commit intogarrytan:mainfrom
mvanhorn:fix/906-chromium-path-headless
Open

fix(browse): respect GSTACK_CHROMIUM_PATH in headless mode#1035
mvanhorn wants to merge 1 commit intogarrytan:mainfrom
mvanhorn:fix/906-chromium-path-headless

Conversation

@mvanhorn
Copy link
Copy Markdown
Contributor

Summary

GSTACK_CHROMIUM_PATH is only respected in launchHeaded() (browser-manager.ts:270) but not in launch() (browser-manager.ts:183). Skills like /qa use headless mode by default, so setting GSTACK_CHROMIUM_PATH has no effect when the bundled chromium_headless_shell fails on NixOS and other non-FHS distros.

Changes

Read GSTACK_CHROMIUM_PATH in launch() and pass it as executablePath to chromium.launch(), matching the existing pattern in launchHeaded().

browse/src/browser-manager.ts: 3 lines added.

Testing

bun test passes (665 pass across skill validation and gen-skill-docs). The change mirrors the existing env var handling in launchHeaded() at line 270.

Fixes #906

This contribution was developed with AI assistance (Claude Code).

GSTACK_CHROMIUM_PATH was only read in launchHeaded() but not in
launch(). Skills like /qa that use headless mode ignored the env var,
breaking browse on NixOS and other non-FHS distros where the bundled
chromium_headless_shell binary fails.

Read the env var in launch() the same way launchHeaded() does and
pass it as executablePath to chromium.launch().

Fixes garrytan#906
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

browse: GSTACK_CHROMIUM_PATH ignored in headless mode

1 participant