browser-pilot-cli 0.4.0 → 0.5.1

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.
@@ -0,0 +1,30 @@
1
+ # Browser Pilot 0.5.1
2
+
3
+ Browser Pilot 0.5.1 makes disconnected-browser recovery explicit and prevents
4
+ Agents from creating repeated Chrome authorization prompts when remote
5
+ debugging is not ready.
6
+
7
+ ## Deliberate connection flow
8
+
9
+ - `bp status` and `bp browsers` remain passive setup checks and never request
10
+ Chrome authorization.
11
+ - Disconnected browser commands preserve the selected browser candidate's
12
+ structured remediation, including `start_browser`,
13
+ `enable_remote_debugging`, and `restart_remote_debugging`.
14
+ - `bp status` reports the same actionable setup message instead of always
15
+ suggesting another connection attempt.
16
+ - Human CLI output labels structured recovery guidance as an action, while
17
+ JSON output keeps the stable `code`, `retryable`, and `remediation` contract.
18
+ - Target commands now share the same connection requirement and return
19
+ `browser_disconnected` instead of exposing an internal not-connected error.
20
+
21
+ ## Agent guidance
22
+
23
+ - The Browser Pilot skill checks status first, inspects browser candidates only
24
+ when disconnected, and follows the returned remediation before connecting.
25
+ - Agents must warn the user about Chrome's possible Allow dialog before the
26
+ shell call, then issue exactly one explicit `bp connect --browser <id>`.
27
+ - Connection timeouts, interruptions, and authorization failures require state
28
+ inspection; they never authorize a blind or concurrent connect loop.
29
+ - Multiple ready browser candidates are selected explicitly rather than by an
30
+ ambiguous default.
package/package.json CHANGED
@@ -1,13 +1,12 @@
1
1
  {
2
2
  "name": "browser-pilot-cli",
3
- "version": "0.4.0",
3
+ "version": "0.5.1",
4
4
  "description": "CLI tool to control your browser via Chrome DevTools Protocol",
5
5
  "repository": "https://github.com/relixiaobo/browser-pilot",
6
6
  "type": "module",
7
7
  "bin": {
8
8
  "bp": "dist/cli.js",
9
- "browser-pilot": "dist/cli.js",
10
- "browser-pilot-conformance": "scripts/run-stdio-conformance.mjs"
9
+ "browser-pilot": "dist/cli.js"
11
10
  },
12
11
  "scripts": {
13
12
  "build": "tsup",
@@ -26,8 +25,6 @@
26
25
  "test:unit": "tsup && node --test tests/*.test.mjs",
27
26
  "test:capabilities": "tsup && node --test tests/browser-capability-fixtures.test.mjs",
28
27
  "test:protocol": "tsup && node --test tests/protocol.test.mjs",
29
- "test:stdio-conformance": "tsup && node scripts/run-isolated-stdio-conformance.mjs",
30
- "test:host-acceptance": "tsup && node scripts/run-isolated-host-integration-acceptance.mjs",
31
28
  "test:distribution": "tsup && node scripts/verify-npm-distribution.mjs",
32
29
  "test:canary": "tsup && node scripts/run-real-site-canaries.mjs",
33
30
  "test:canary:strict": "tsup && node scripts/run-real-site-canaries.mjs --strict",
@@ -41,10 +38,7 @@
41
38
  "dist/cli.js",
42
39
  "dist/daemon.js",
43
40
  "dist/managed-target-janitor.js",
44
- "scripts/run-stdio-conformance.mjs",
45
41
  "docs/architecture/browser-pilot-platform-spec.md",
46
- "docs/integration/stdio-bridge.md",
47
- "docs/integration/stdio-conformance.md",
48
42
  "docs/plans/browser-capability-evolution.md",
49
43
  "docs/plans/profile-context-routing.md",
50
44
  "docs/plans/v0.3.0-stabilization.md",