smooth-operator-mcp 2.4.7 → 2.4.9

package/docs/mcp-server.md

@@ -143,44 +143,6 @@ application token, Host/Origin allowlists, or request-size limit. Allowed host
 and origin values are hostnames without a scheme; browser preflight requests
 are answered only after the same Host and Origin checks.
 
-### ChatGPT and OpenAI connections
-
-For private developer-mode use, the safest OpenAI-compatible route is Secure
-MCP Tunnel. It keeps this server on the local machine and forwards requests
-over an outbound connection; it can launch this server over stdio, so no public
-HTTP listener or public browser profile is required.
-
-Create a tunnel in OpenAI Platform, install the separately distributed
-`tunnel-client`, and run a profile like this (replace the placeholders with
-your tunnel identity and local executable):
-
-```sh
-export CONTROL_PLANE_API_KEY="sk-..."
-
-tunnel-client init \
-  --sample sample_mcp_stdio_local \
-  --profile smooth-operator \
-  --tunnel-id tunnel_... \
-  --mcp-command "smooth-operator --transport stdio"
-
-tunnel-client doctor --profile smooth-operator --explain
-tunnel-client run --profile smooth-operator
-```
-
-Then enable Developer mode in ChatGPT, create a developer-mode app, choose
-`Tunnel`, and select the associated tunnel. Tunnel and ChatGPT workspace
-permissions are separate; the tunnel must be associated with the target
-workspace. This path is for private testing and use, not public plugin
-submission.
-
-For public distribution, deploy a stable HTTPS `/mcp` endpoint and put an
-OAuth 2.1-compatible identity provider in front of authenticated tools. The
-local bearer token is intended for this server's controlled HTTP mode; it is
-not a substitute for a public OAuth authorization server. See the official
-[OpenAI MCP quickstart](https://developers.openai.com/plugins/build/app-quickstart),
-[authentication guide](https://developers.openai.com/plugins/build/auth), and
-[Secure MCP Tunnel guide](https://developers.openai.com/api/docs/guides/secure-mcp-tunnels).
-
 ## Browser lifecycle
 
 The server manages one headed, persistent private agent-Chrome session by
@@ -207,8 +169,10 @@ SmoothOperator process using the same private profile is rejected by the profile
 `SMOOTH_OPERATOR_BROWSER_AUTO_LAUNCH` is retained for backward compatibility but is
 ignored in managed mode.
 
-Browser actions share a bounded operation queue and deadline. Browser startup
-uses one in-flight connection promise, so concurrent callers wait for the same
+Browser actions share a bounded operation queue and deadline. Independent
+read-only observations may run concurrently; navigation, mutation, snapshot,
+and session-control operations remain exclusive. Browser startup uses one
+in-flight connection promise, so concurrent callers wait for the same
 reattach/launch attempt instead of starting duplicate processes. Newly
 auto-attached top-level targets are held at the CDP boundary until the
 navigation policy guard is installed; targets whose attachment ownership

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "smooth-operator-mcp",
-  "version": "2.4.7",
+  "version": "2.4.9",
   "type": "module",
   "packageManager": "npm@12.0.2",
   "description": "A lightweight, production-grade MCP server for secure browser automation.",
@@ -34,12 +34,9 @@
     "dead-code": "knip --include files,exports,dependencies,unlisted --no-progress",
     "mcp:stdio": "npm run start -- --transport stdio",
     "mcp:http": "npm run start -- --transport http",
-    "benchmark:mcp": "node scripts/benchmark-mcp.mjs",
-    "benchmark:mcp:live": "node scripts/benchmark-mcp.mjs --live",
-    "benchmark:mcp:dist": "node scripts/benchmark-mcp.mjs --dist",
     "package:smoke": "npm run build && node scripts/verify-package.mjs",
     "package:smoke:install": "npm run build && node scripts/verify-package.mjs --install",
-    "release:smoke": "npm run package:smoke:install && npm run benchmark:mcp:dist",
+    "release:smoke": "npm run package:smoke:install",
     "prepack": "npm run build",
     "prepare": "npm run build"
   },