Aurora-Lucas/dsh-chrome-browser ↗★ 0
@local/dsh-chrome-browser
Model-facing Google Chrome tool: drives the installed Chrome over the DevTools protocol so front-end work can navigate, screenshot, inspect, and interact without per-call shell approval. 允许模型免去逐次Shell授权直接进行网页导航、截图和交互，适合前端及自动化任务。
Install
$
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:Aurora-Lucas/dsh-chrome-browserREADME
Read the full README ↗Configuration
The bundle patch sets these; apply merges them over its own defaults and validates them.
| Key | Default | Meaning |
|---|---|---|
chromePath | '' (auto-detect) | Chrome executable. |
headless | true | Run without a window. |
noSandbox | true | Pass --no-sandbox (required when the Host runs as root). |
defaultWidth / defaultHeight | 1280 / 900 | Default viewport. |
maxOutputChars | 100000 | Default cap for dom/text/eval output. |
navigationTimeoutMs | 30000 | Navigation and wait_for budget. |
artifactDir | '' (system temp) | Where screenshots and PDFs go when no path is given. |
How Chrome is located
The tool schema has no path parameter: the model never needs to know where the browser lives.
resolveChromePath resolves in this order and fails with an actionable message naming the config key
when nothing matches:
- the row's
chromePathconfig; - the
DSH_CHROME_PATHenvironment variable; - a probe list —
/usr/bin/google-chrome,google-chrome-stable,google-chrome-beta,/usr/bin/chromium,chromium-browser,/opt/google/chrome/chrome,/snap/bin/chromium, plus the usual macOS and Windows locations.
For an unusual installation, set DSH_CHROME_PATH for the Host or edit the row's chromePath — no
code change is needed.