smooth-operator-mcp 3.0.6 → 3.1.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.
package/README.md CHANGED
@@ -31,7 +31,10 @@ The wizard asks exactly 3 focused questions: browser profile ownership, browser
31
31
 
32
32
  Requires Node 22.23.2+ and an installed Chromium-based browser. Profile at `~/.smooth-operator/browser` — sign in once.
33
33
 
34
- Verify: `smooth-operator --help` and `server_health` / `browser_doctor` appear after restart.
34
+ Verify: `smooth-operator --help` and `server_health` / `browser_doctor` appear after restart. `server_health` reports `ok` when the runtime is ready, `degraded` when browser recovery is required or its managed profile lease is not held, and `shutting_down` during teardown; an idle lazy browser is healthy.
35
+
36
+ For a local release check, run `npm run verify`; it covers lint, type safety,
37
+ tests, dead-code analysis, and the package smoke test.
35
38
 
36
39
  ## What it does
37
40
 
@@ -57,7 +60,7 @@ Talk to your harness normally. It can call `browser_navigate` → `browser_snaps
57
60
 
58
61
  Browser identity remains native, page JavaScript is available by default, and
59
62
  behavioral timing is off for fast deterministic input. Set the explicit
60
- environment flags to change those choices. See `docs/STEALTH-GUIDE.md` for
63
+ environment flags to change those choices. See the [browser compatibility guide](docs/STEALTH-GUIDE.md) for
61
64
  details and responsible use.
62
65
 
63
66
  For the fastest supported operation, keep behavioral timing off with
@@ -80,6 +83,10 @@ evaluation remains an explicit page capability.
80
83
  - Reliable — private profiles, stale-reference recovery, reconnect handling, and structured errors
81
84
  - Flexible — stdio by default, Streamable HTTP when you need it, plus connect and disabled modes
82
85
 
86
+ For HTTP deployments, the configured MCP path also has a bounded readiness
87
+ endpoint at `<path>/healthz` (normally `/mcp/healthz`), subject to the same
88
+ HTTP authentication policy as the MCP endpoint.
89
+
83
90
  ## Benchmarks
84
91
 
85
92
  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)