smooth-operator-mcp 2.4.10 → 2.4.11

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.
package/.env.example CHANGED
@@ -5,7 +5,7 @@ SMOOTH_OPERATOR_DATA_DIR=~/.smooth-operator
5
5
  # ~/.smooth-operator/config.json is loaded automatically when this is unset.
6
6
  # SMOOTH_OPERATOR_CONFIG=~/.smooth-operator/config.json
7
7
 
8
- # Managed agent Chrome is the zero-setup default. It discovers Google Chrome,
8
+ # Managed browser mode is the zero-setup default. It discovers a Chromium-based browser,
9
9
  # then creates one private persistent profile under SMOOTH_OPERATOR_DATA_DIR.
10
10
  SMOOTH_OPERATOR_BROWSER_MODE=managed
11
11
  # For an advanced DevTools connection, use mode=connect and set this endpoint.
package/README.md CHANGED
@@ -29,7 +29,7 @@ npm install -g github:Gitshop77/Smooth-Operator && smooth-operator install openc
29
29
 
30
30
  The wizard asks 7 focused questions covering browser mode, executable, headless operation, domain policy, page JavaScript, and the data directory. Run `smooth-operator install` with no harness to pick one interactively (TTY only; piped/CI runs print usage and exit). `--yes` applies the recommended defaults, so give it a target: `smooth-operator install opencode --yes`. Personal Chrome mode launches a dedicated debugging profile on `9222` and derives `browserUrl` automatically.
31
31
 
32
- Requires Node 22.23.2+ and Chrome. Profile at `~/.smooth-operator/browser` — sign in once.
32
+ Requires Node 22.23.2+ and an installed Chromium-based browser. Profile at `~/.smooth-operator/browser` — sign in once.
33
33
 
34
34
  Verify: `smooth-operator --help` and `server_health` / `browser_doctor` appear after restart.
35
35
 
@@ -48,7 +48,7 @@ Talk to your harness normally. It can call `browser_navigate` → `browser_snaps
48
48
 
49
49
  ## Why
50
50
 
51
- - Zero setup — managed, headed, persistent Chrome by default
51
+ - Zero setup — managed, headed, persistent browser by default
52
52
  - Secure by default — domain and file policy, bounded outputs, redaction, and JavaScript disabled unless explicitly enabled
53
53
  - Reliable — private profiles, stale-reference recovery, reconnect handling, and structured errors
54
54
  - Flexible — stdio by default, Streamable HTTP when you need it, plus connect and disabled modes
@@ -57,7 +57,7 @@ Talk to your harness normally. It can call `browser_navigate` → `browser_snaps
57
57
 
58
58
  Compared with [Browser Use MCP](https://github.com/browser-use/browser-use) · [![Browser Use GitHub stars](https://img.shields.io/github/stars/browser-use/browser-use?style=social)](https://github.com/browser-use/browser-use)
59
59
 
60
- (Date Of Testing -Wednesday 26 August 2026-)
60
+ Tested: 26 August 2026
61
61
 
62
62
  | Benchmark | Metric | SmoothOperator | Browser Use MCP |
63
63
  | --- | --- | ---: | ---: |
@@ -74,3 +74,8 @@ Compared with [Browser Use MCP](https://github.com/browser-use/browser-use) · [
74
74
  | MiniWoB++ | MCP errors | **0** | 29 |
75
75
  | MiniWoB++ | Transport errors | **0** | **0** |
76
76
  | MiniWoB++ | Timeouts | **0** | **0** |
77
+ | Browser Use benchmark | Muse Spark 1.2 · score | **64% · 100 tasks** | 12% · 60 tasks |
78
+
79
+ *Task counts and scoring rules differ; comparison is directional.*
80
+
81
+ [View the Browser Use benchmark](https://github.com/browser-use/benchmark)