chrome-cli-bridge 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +34 -16
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -45,7 +45,14 @@ Requires **Node.js ≥ 18**.
45
45
 
46
46
  ### 2 — Load the Chrome extension
47
47
 
48
- The companion extension is what actually acts in the browser.
48
+ The companion extension is what actually acts in the browser. Install it using either method:
49
+
50
+ **Option A — Chrome Web Store (recommended)**
51
+
52
+ Install directly from the store — no Developer mode required:
53
+ [chrome-cli-bridge on the Chrome Web Store](https://chrome.google.com/webstore/detail/chrome-cli-bridge)
54
+
55
+ **Option B — Load from source (for contributors / offline)**
49
56
 
50
57
  1. Download the extension from the [GitHub releases page](https://github.com/nestormata/chrome-bridge/releases)
51
58
  2. Open **chrome://extensions** in Chrome
@@ -230,36 +237,47 @@ await bridge.disconnect();
230
237
 
231
238
  `chrome-cli-bridge` is designed to be a tool layer for AI agents working in the terminal.
232
239
 
240
+ > **📄 `SKILLS.md`** — The repo includes a ready-to-use [`SKILLS.md`](https://github.com/nestormata/chrome-bridge/blob/main/SKILLS.md) file with copy-paste instructions for setting up chrome-cli-bridge with GitHub Copilot CLI, Claude Code, Cursor, Aider, Cline, Continue.dev, and any tool that accepts a system prompt.
241
+
233
242
  ### GitHub Copilot CLI
234
243
 
244
+ Add to `.github/copilot-instructions.md`:
245
+ ```
246
+ You have access to a live Chrome tab via chrome-cli-bridge.
247
+ Use `chrome-bridge <command>` to read the DOM, run JavaScript,
248
+ capture screenshots, navigate, or interact with the page.
249
+ All output is JSON. Relay must be running: chrome-bridge start.
250
+ ```
251
+
252
+ Example session:
235
253
  ```
236
254
  you> read the current page title from my browser
237
255
  copilot> chrome-bridge exec --code "document.title"
238
256
  {"result":"Checkout — My Store"}
239
-
240
- you> get all the product names on the page
241
- copilot> chrome-bridge exec --code "
242
- [...document.querySelectorAll('.product-title')].map(el => el.textContent.trim())
243
- "
244
257
  ```
245
258
 
246
- ### Claude Code / Claude.ai
247
-
248
- Add this to your system prompt or project context:
259
+ ### Claude Code
249
260
 
261
+ Add to `CLAUDE.md` in your project root:
250
262
  ```
251
263
  You have access to a live Chrome tab via chrome-cli-bridge.
252
- Use `chrome-bridge <command>` to read the DOM, run JavaScript,
253
- capture screenshots, navigate, or interact with the page.
254
- All output is JSON.
264
+ Use `chrome-bridge exec --code "<js>"` to read or manipulate the page.
265
+ Use `chrome-bridge navigate` then `chrome-bridge wait` before reading content.
266
+ All output is JSON. Relay must be running: chrome-bridge start.
255
267
  ```
256
268
 
257
- Then Claude can autonomously scrape, test, or automate flows:
269
+ ### Cursor
258
270
 
271
+ Add to `.cursorrules`:
259
272
  ```
260
- claude> I'll check the current state of the checkout form.
261
- $ chrome-bridge snapshot
262
- $ chrome-bridge exec --code "document.querySelector('#cart-total').textContent"
273
+ You can interact with a live Chrome tab using chrome-bridge commands.
274
+ All output is JSON. Relay must be running: chrome-bridge start.
275
+ ```
276
+
277
+ ### Aider
278
+
279
+ ```sh
280
+ aider --read SKILLS.md
263
281
  ```
264
282
 
265
283
  ### Shell script automation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "chrome-cli-bridge",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Connect CLI tools and AI agents to a live Chrome tab via WebSocket bridge",
5
5
  "type": "module",
6
6
  "main": "src/index.js",