Migrate Cursor browse plugin to the browse CLI; remove functions

[justinemach]

What

Per Ziray — slight update + new release for the Cursor plugin.

1. Repoint onto the live browse CLI. The plugin pinned the deprecated @browserbasehq/browse-cli@^0.1.4 (npm: "now published as 'browse'… please migrate"). Swapped to browse@^0.8.4 and regenerated package-lock.json. The binary still resolves at node_modules/.bin/browse, so src/cli.ts and src/mcp-server.ts are functionally unchanged.
2. Remove the functions plugin — dropped plugins/functions/, its .cursor-plugin/marketplace.json entry, and the README row.
3. Stale-reference cleanup — browse-cli → browse in source comments + one error string.
4. Version bumps — browse plugin 2.0.0 → 2.1.0, marketplace 1.0.0 → 1.1.0.

Additive / non-breaking

MCP tools (browser_navigate, browser_click, …) are untouched, so existing Cursor installs keep working. This only updates the engine underneath + removes functions.

Validation

• node scripts/validate-template.mjs → passes
• package-lock.json regenerated; 0 remaining refs to the old package
• All manifest JSON parses

Release

After merge: tag v2.1.0 to trigger release.yml (build → prune dev deps → validate → tarball).

Notes for review

• ⚠️ Removing functions is subtractive — anyone who installed the Cursor functions plugin loses it on update. Ziray approved; flagging for release notes.
• Did not expand the MCP tool set to cover newer browse surface (sessions, network, tabs, cloud) — kept this a version bump. Can follow up if we want tool parity.

🤖 Generated with Claude Code

---

Note

Medium Risk
Swapping the automation engine and pulling a much larger dependency tree could affect install size and runtime behavior; removing the functions plugin is a breaking change for anyone who relied on it.

Overview
Migrates the Cursor marketplace to the current browse package and drops the separate cloud-functions plugin.

The browse plugin dependency moves from deprecated @browserbasehq/browse-cli to browse@^0.8.4 (package.json / lockfile). The browser CLI and MCP server still invoke node_modules/.bin/browse; only comments and install error text now say browse instead of browse-cli. Browse plugin is 2.1.0; marketplace metadata is 1.1.0.

The functions plugin is removed entirely (plugins/functions/, marketplace entry, README table row). The marketplace now ships only browse.

MCP tool surface is unchanged in this PR; lockfile growth reflects the new browse dependency tree (e.g. Stagehand / AI-related packages).

^{Reviewed by Cursor Bugbot for commit ca4ab57. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ca4ab57. Configure here.}

[cursor]

Lockfile uses private registry URLs

High Severity

Regenerated package-lock.json records many resolved tarball URLs on socket-firewall.tail929132.ts.net, including the browse dependency itself, instead of the public npm registry. npm ci in plugins/browse (including release npm ci) fetches those exact URLs, so installs fail anywhere that host is unreachable.

Additional Locations (1)

• plugins/browse/package-lock.json#L27-L28

 

^{Reviewed by Cursor Bugbot for commit ca4ab57. Configure here.}