seek://map/dsh-tool-control-chrome
dsh-tool-control-chrome
#browser #chrome #automation
TL;DR
Brings the agent into the browser you already use: an installed MV3 extension and a loopback-only Bridge drive your existing logged-in Chrome or Edge — per its README, 43 browser_* tools, lazy-loaded by default, with side-effecting operations never replayed automatically.
Browser control that starts from the profile you actually use: through an installed MV3 extension and a loopback-only Bridge, it works inside your existing logged-in Chrome or Edge. Role and name targets read Chromium's accessibility tree first, with a bounded DOM fallback; tab and document fences reject stale observations after navigation, and side-effecting operations are never replayed automatically — the logged-in-profile counterpart to the map's Playwright-driven browser entry.
Facts
- install
- dsh plugin --profile web add @lyd123qw2008/dsh-tool-control-chrome
- license
- MIT
- note
- MV3 扩展需手动加载（开发者模式 Load unpacked）；Bridge 仅监听回环地址，不是远程控制通道。
Key points
- Drives your existing Chrome or Edge through an installed MV3 extension and a loopback-only Bridge; per its README, it does not read browser profile files or cookies
- Per its README, the current Agent receives all 43 browser_* tools once the Skill loads; under default lazyTools only the Skill metadata is present at assembly time
- Role/name/label semantic targets resolve Chromium AX-first and fail closed on ambiguity; side-effecting operations are never replayed automatically
- Human diagnostics live in the /chrome commands (status, connect, doctor), independent of the model-facing tools
FAQ
Does it read my login credentials?
No — its README states plainly that it does not read browser profile files or cookies: it operates the browser you already have through the installed MV3 extension, and the login state stays inside the real browser.
How is it different from dsh-browser-control, the Playwright entry on this map?
dsh-browser-control wires Playwright's MCP server into DSH and drives a visible Chrome; this project uses its own MV3 extension plus a loopback Bridge to control an existing logged-in Chrome or Edge, and lazy-loads its tool schemas to keep the model-facing context small.
What does setup take?
Install the DSH plugin into the web profile, then install pi-control-chrome and load its extension/ directory once via developer mode at chrome://extensions; the Bridge listens on loopback only and is not a remote-control transport.
Official references