Skip to content

docs(skills): verify — prescribe the stable Chromium alias instead of the versioned path #7375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-zhuang merged 1 commit into from
Sep 2, 2026
Merged

docs(skills): verify — prescribe the stable Chromium alias instead of the versioned path #7375

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions .claude/skills/verify/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,13 +24,15 @@ their hardcoded defaults — that IS the offline path, not an error.
## Driving it headlessly

The chrome-devtools MCP may lack a Chrome binary in remote sessions. Use the
repo's own Playwright instead — the pre-installed executable is at
`/opt/pw-browsers/chromium-1194/chrome-linux/chrome` (probe with
`find /opt/pw-browsers -name chrome` if the version moved):
repo's own Playwright instead — the pre-installed executable is the stable
alias `/opt/pw-browsers/chromium`. ⛔ Never copy the versioned
`chromium-NNNN/chrome-linux/chrome` spelling out of a probe: the alias is what
survives an image bump, and a dead versioned path reads as "no browser here"
when the browser is in fact present.

```js
import { chromium } from '@playwright/test';
const browser = await chromium.launch({ executablePath: '<probed path>' });
const browser = await chromium.launch({ executablePath: '/opt/pw-browsers/chromium' });
```

Gotcha: a driver script must live **inside** the repo (e.g.
Expand Down