Environment
- antigravity-cli 1.1.0 (latest as of 2026-07-08), Linux x86_64
Symptom
On startup agy attempts to download the Playwright driver and fails, so the browser tooling never becomes available:
https://playwright.azureedge.net/builds/driver/playwright-1.57.0-linux.zip → HTTP 404
Root cause
The binary bundles playwright-community/playwright-go v0.5700.x (driver 1.57.0), which fetches the driver via the hardcoded template %s/builds/driver/playwright-%s-%s.zip against the legacy CDN hosts (playwright.azureedge.net, playwright-akamai.azureedge.net, playwright-verizon.azureedge.net — all visible via strings on the binary).
Microsoft has retired driver-zip distribution on all CDN endpoints (verified 2026-07-08):
| URL |
Status |
https://playwright.azureedge.net/builds/driver/playwright-1.57.0-linux.zip |
404 |
https://cdn.playwright.dev/builds/driver/playwright-1.57.0-linux.zip |
404 |
https://cdn.playwright.dev/dbazure/download/playwright/builds/driver/playwright-1.57.0-linux.zip |
307 → 400 (no object at origin) |
microsoft/playwright GitHub release assets |
none |
So every playwright-go release before v0.6100.0 can no longer bootstrap the driver on a fresh machine.
Suggested fix
playwright-go v0.6100.0 (2026-06-26) switched driver acquisition to assembling it from the npm registry (playwright-core tarball) + nodejs.org, dropping the deprecated CDN entirely — see mxschmitt/playwright-go#615. Please bump the bundled playwright-go to >= v0.6100.0 (also rolls the driver to Playwright 1.61).
Workaround until fixed (for other affected users)
Assemble the driver manually from official sources — the same layout the retired zip used — so agy's version check passes and the download is skipped:
V=1.57.0
D=~/.cache/ms-playwright-go/$V
mkdir -p "$D"
# playwright-core tarball extracts to $D/package/
curl -sL "https://registry.npmjs.org/playwright-core/-/playwright-core-$V.tgz" | tar xz -C "$D"
# place any Node.js (>=18) binary at $D/node — reuse the system one,
# or grab one from https://nodejs.org/dist/
cp "$(command -v node)" "$D/node"
"$D/node" "$D/package/cli.js" --version # → Version 1.57.0
"$D/node" "$D/package/cli.js" install chromium
Environment
Symptom
On startup
agyattempts to download the Playwright driver and fails, so the browser tooling never becomes available:Root cause
The binary bundles
playwright-community/playwright-gov0.5700.x (driver 1.57.0), which fetches the driver via the hardcoded template%s/builds/driver/playwright-%s-%s.zipagainst the legacy CDN hosts (playwright.azureedge.net,playwright-akamai.azureedge.net,playwright-verizon.azureedge.net— all visible viastringson the binary).Microsoft has retired driver-zip distribution on all CDN endpoints (verified 2026-07-08):
https://playwright.azureedge.net/builds/driver/playwright-1.57.0-linux.ziphttps://cdn.playwright.dev/builds/driver/playwright-1.57.0-linux.ziphttps://cdn.playwright.dev/dbazure/download/playwright/builds/driver/playwright-1.57.0-linux.zipmicrosoft/playwrightGitHub release assetsSo every playwright-go release before v0.6100.0 can no longer bootstrap the driver on a fresh machine.
Suggested fix
playwright-gov0.6100.0 (2026-06-26) switched driver acquisition to assembling it from the npm registry (playwright-coretarball) + nodejs.org, dropping the deprecated CDN entirely — see mxschmitt/playwright-go#615. Please bump the bundled playwright-go to >= v0.6100.0 (also rolls the driver to Playwright 1.61).Workaround until fixed (for other affected users)
Assemble the driver manually from official sources — the same layout the retired zip used — so agy's version check passes and the download is skipped: