@comecaramelos/dsh-chrome-mcp 1.0.0 → 2.0.0

package/README.md

@@ -1,59 +1,64 @@
 # @comecaramelos/dsh-chrome-mcp
 
-Connects DSH to [Chrome DevTools MCP](https://github.com/ChromeDevTools/chrome-devtools-mcp), including Windows Chrome from WSL.
+Connects DeepSeek Harness to [Chrome DevTools MCP](https://github.com/ChromeDevTools/chrome-devtools-mcp)
+so the agent can drive a Chrome browser — a local one, or the Windows Chrome when dsh runs
+in WSL.
 
-## Install
+It is a **component** of the MCP connections bundle: it adds the `chrome` connection type
+(and `chrome-windows` on WSL) to `@comecaramelos/dsh-mcp-manager`, which owns the
+connection list, the on/off switch and the live status.
+
+## Requirements
 
-[Google Chrome](https://www.google.com/chrome/) must be installed: the MCP server does not download it.
+- dsh `^0.2.0` (0.2.0 and 0.2.1), on Linux, WSL or Windows.
+- [Google Chrome](https://www.google.com/chrome/) installed — the MCP server does not
+  download it.
+
+## Install
 
 ```sh
-dsh plugin --profile web add @comecaramelos/dsh-chrome-mcp
+dsh plugin --profile web add @comecaramelos/dsh-mcp-manager-bundle
 ```
 
-The plugin includes `--no-usage-statistics` and `--no-performance-crux` by default. Use the executable picker to select a browser found on your host.
+Coming from the standalone 1.x bundle (dsh 0.1)? Remove it first: it inserts the same
+`mcp-chrome` row and does not load on dsh 0.2. Your old settings are kept — the
+connections card offers to create the matching connection.
 
-## Windows Chrome from WSL
+## Use it
 
-Requirements:
+1. Plugins → MCP connections → **MCP connections** → *Add connection*, kind
+   **Chrome MCP**.
+2. Pick the Chrome executable (the picker lists the browsers found on this machine) and
+   add extra flags if you need them.
+3. Turn it on. Chrome itself only opens on the first tool call that needs a page.
 
-The user only needs to add the following line to `.wslconfig`:
-```
-networkingMode=mirrored
-```
-The required Chrome flags are managed by the **Flags WSL** button.
+The component's own page (Plugins → MCP connections → **Chrome MCP**) keeps the
+executables and default flags every connection starts from, and a *Reduce log output*
+switch that keeps the server's stderr out of the dsh console.
 
-A windows executable activates the connect-mode bridge. The executable selector displays `connect mode` instead of probing a local executable.
+The MCP server is the `chrome-devtools-mcp` version this package pins, run by dsh's own
+Node — no `npx` and no download on every start. Flags, isolated profiles and when the
+card stops checking the executable: [docs/knowledge/flags.md](docs/knowledge/flags.md).
 
-The bridge uses the first available port and gets a dedicated profile (`.chrome-<port>`).
+### Native Windows
 
-## Manual installation
+Nothing extra: the server starts `chrome.exe` itself, as on Linux. The card never runs
+`chrome.exe --version` (on Windows that opens a browser window); it reads the version
+from the install folder.
 
-Replace `/path/to/dsh-chrome-mcp` with your local checkout:
+### Windows Chrome from WSL
 
-```sh
-mkdir -p ~/.dsh/profiles/web/node_modules/@comecaramelos
-ln -s /path/to/dsh-chrome-mcp ~/.dsh/profiles/web/node_modules/@comecaramelos/dsh-chrome-mcp
-```
+Add `networkingMode=mirrored` to `%USERPROFILE%\.wslconfig` and run `wsl --shutdown`.
+Then pick the Windows Chrome in the executable picker and press **Prelaunch Windows
+Chrome**: it starts the Windows browser on a free debugging port and the connection
+attaches to it. Details: [docs/knowledge/wsl.md](docs/knowledge/wsl.md).
 
-Add the dependency and bundle to `~/.dsh/profiles/web/package.json`, preserving existing entries:
-
-```json
-{
-  "dependencies": {
-    "@comecaramelos/dsh-chrome-mcp": "link:/path/to/dsh-chrome-mcp"
-  },
-  "dsh": {
-    "profile": {
-      "bundles": [
-        "@deepseek-ai/dsh-base",
-        "@deepseek-ai/dsh-web-app",
-        "@comecaramelos/dsh-chrome-mcp"
-      ]
-    }
-  }
-}
-```
+## From a checkout
+
+Use the manager's `node scripts/link-profile.mjs [profile]` with this checkout next to
+`dsh-mcp-manager`: it links the manager, the bundle and this component into the profile.
+To build and test this package: `npm install`, `npm run build`, `npm test`.
 
 ---
 
-[Contributing](CONTRIBUTING.md) · [License](LICENSE.md)
+[Contributing](CONTRIBUTING.md) · [AGENTS.md](AGENTS.md) (for coding agents) · [License](LICENSE.md)