@btraut/browser-bridge 0.1.1 → 0.3.0

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 (9) hide show
  1. package/CHANGELOG.md +29 -0
  2. package/README.md +45 -17
  3. package/dist/api.js +126 -1
  4. package/dist/api.js.map +2 -2
  5. package/dist/index.js +635 -22
  6. package/dist/index.js.map +4 -4
  7. package/package.json +4 -2
  8. package/skills/browser-bridge/SKILL.md +9 -10
  9. package/skills/browser-bridge/skill.json +4 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@btraut/browser-bridge",
3
- "version": "0.1.1",
3
+ "version": "0.3.0",
4
4
  "license": "MIT",
5
5
  "engines": {
6
6
  "node": ">=20"
@@ -15,7 +15,8 @@
15
15
  "extension",
16
16
  "skills",
17
17
  "README.md",
18
- "LICENSE"
18
+ "LICENSE",
19
+ "CHANGELOG.md"
19
20
  ],
20
21
  "bin": {
21
22
  "browser-bridge": "dist/index.js"
@@ -25,6 +26,7 @@
25
26
  "postpack": "node ./scripts/postpack.mjs"
26
27
  },
27
28
  "dependencies": {
29
+ "@inquirer/prompts": "^8.2.0",
28
30
  "@modelcontextprotocol/sdk": "^1.26.0",
29
31
  "@mozilla/readability": "^0.6.0",
30
32
  "commander": "^14.0.3",
package/skills/browser-bridge/SKILL.md CHANGED
@@ -1,15 +1,12 @@
1
1
  ---
2
2
  name: browser-bridge
3
3
  description: >
4
- Local Chrome control via Browser Bridge (CLI + optional MCP). Use when the
5
- task needs real browser interaction, reliable DOM inspection, or screenshots.
4
+ Local Chrome control via Browser Bridge (CLI + optional MCP). Use when the task needs real browser interaction, reliable DOM inspection, or screenshots.
6
5
  ---
7
6
 
8
7
  # Browser Bridge (CLI + MCP)
9
8
 
10
- Browser Bridge drives and inspects a real local Chrome instance. You can use it
11
- either via the CLI (works everywhere) or via MCP (optional, for MCP-capable
12
- clients).
9
+ Browser Bridge drives and inspects a real local Chrome instance. You can use it either via the CLI (works everywhere) or via MCP (optional, for MCP-capable clients).
13
10
 
14
11
  ## Prerequisites
15
12
 
@@ -38,7 +35,7 @@ browser-bridge session create
38
35
  browser-bridge drive navigate --session-id <id> --url https://example.com
39
36
  browser-bridge drive wait-for --session-id <id> --kind url_matches --value example.com
40
37
 
41
- browser-bridge inspect dom-snapshot --session-id <id> --format ax --interactive --compact
38
+ browser-bridge inspect dom-snapshot --session-id <id> --format ax --interactive --compact --max-nodes 2000
42
39
  browser-bridge artifacts screenshot --session-id <id> --full-page --format png
43
40
 
44
41
  browser-bridge diagnostics doctor --session-id <id>
@@ -47,6 +44,10 @@ browser-bridge open-artifacts --session-id <id>
47
44
  browser-bridge session close --session-id <id>
48
45
  ```
49
46
 
47
+ Notes:
48
+
49
+ - `--max-nodes` only applies to `--format ax` snapshots. For `--format html`, the snapshot succeeds and the flag is ignored with a warning.
50
+
50
51
  Element targeting:
51
52
 
52
53
  - Find elements to get stable refs (like `@e1`):
@@ -73,11 +74,9 @@ If your agent client supports MCP, configure it to launch:
73
74
  browser-bridge mcp
74
75
  ```
75
76
 
76
- The MCP server runs over stdio. MCP clients usually launch it automatically;
77
- you only run it manually for debugging.
77
+ The MCP server runs over stdio. MCP clients usually launch it automatically; you only run it manually for debugging.
78
78
 
79
- Note: MCP still requires `browser-bridge` to be on PATH, since the client
80
- invokes `browser-bridge mcp`.
79
+ Note: MCP still requires `browser-bridge` to be on PATH, since the client invokes `browser-bridge mcp`.
81
80
 
82
81
  ## Tool Groups (MCP)
83
82
 
package/skills/browser-bridge/skill.json ADDED
@@ -0,0 +1,4 @@
1
+ {
2
+ "name": "browser-bridge",
3
+ "version": "0.3.0"
4
+ }