mirror of https://github.com/garrytan/gstack.git
3c2adf81f0
On macOS, Chromium (via Playwright) inherits the system HTTP/S proxy by default. When the user runs a local VPN/proxy app (Shadowrocket, ClashX, Surge, etc.) that does TLS interception, Chromium's HTTPS handshake breaks with SSL error 1 / net_error -100, and every goto fails with ERR_ABORTED. The renderer then crashes and kills the browse server, triggering the familiar '[browse] Starting server...' restart loop. curl is unaffected because curl ignores the system proxy by default, so curl-based health checks continue to pass while browse is broken — making this failure mode especially confusing. Opt-in: set BROWSE_NO_PROXY=1 in the environment and browse will pass '--proxy-server=direct://' to Chromium at launch, bypassing the system proxy entirely. Default behavior unchanged (still inherits system proxy) so corporate proxy users are not affected. Repro: # With Shadowrocket running in HTTP-proxy mode on macOS: browse goto https://example.com # ERR_ABORTED / Timeout 15000ms BROWSE_NO_PROXY=1 browse goto https://example.com # 200 OK |
||
|---|---|---|
| .. | ||
| bin | ||
| scripts | ||
| src | ||
| test | ||
| PLAN-snapshot-dropdown-interactive.md | ||
| SKILL.md | ||
| SKILL.md.tmpl | ||