bookmark-bridge 0.1.2 → 2.0.2

package/README.md

@@ -13,7 +13,8 @@ and relays through it, so several sessions share one browser.
 
 ## Install
 
-Two pieces: this server, and the Chrome extension that dials into it.
+The default package uses the existing WebSocket connection. For the opt-in
+Native Messaging release, see [Native Messaging](#native-messaging).
 
 **1. Register the server with your MCP client.** It downloads itself on first
 run, so you do not need Rust. macOS, Linux and Windows.
@@ -80,8 +81,9 @@ Do not build from source; the npx package fetches a prebuilt binary.
 Your client starts and stops it for you. Nothing to leave running. `git` must be
 on PATH — the snapshots are a real git repository.
 
-**2. Install the extension.** From the Chrome Web Store, or load `extension/`
-at `chrome://extensions` with developer mode on.
+**2. Install the extension.** Get [Bridgey from the Chrome Web Store](https://chromewebstore.google.com/detail/ekokljgbbianihlpahackkfdendobngd)
+and leave its mode set to **Legacy (WebSocket)**. For the unpacked legacy
+extension, use `extension/` from the `v0.1.2` tag.
 
 That is all of it. The extension's popup goes green once the two find each other.
 
@@ -93,7 +95,9 @@ touch a bookmark, and when you open its popup. If an agent reports that the
 extension is not connected, clicking the toolbar icon reconnects it.
 
 <details>
-<summary>From source instead</summary>
+<summary>Build the legacy server from source</summary>
+
+Use the `v0.1.2` tag for the legacy server.
 
 ```sh
 cd mcp && cargo build --release
@@ -112,6 +116,42 @@ extension's storage. `BOOKMARK_BRIDGE_PORT` changes the port.
 
 </details>
 
+## Native Messaging
+
+The v2 server is available on the npm `native` channel. The standard
+`bookmark-bridge` command still installs the legacy server.
+
+1. In your MCP client, change the command arguments from `-y bookmark-bridge`
+   to `-y bookmark-bridge@native`, then restart its MCP connection. With Claude
+   Code, the command for a new entry is
+   `claude mcp add bookmark-bridge -- npx -y bookmark-bridge@native`.
+2. Open Bridgey's popup and choose **Native Messaging**. Approve Chrome's
+   permission prompt. If setup fails, the extension stays in Legacy mode.
+3. Run `bridge_status` from your MCP client to confirm the connection.
+
+The Native npm package contains the prebuilt servers and their checksums.
+The first server startup installs the native host in a user data directory
+outside the npm cache and registers it with Chrome. Chrome launches that host
+when the extension connects. The host and the MCP process communicate over an
+authenticated loopback connection. Keep `git` on the MCP client's PATH. The
+server remembers its absolute path so the Chrome-launched host can use it.
+
+Bridgey serves one Native Messaging browser profile at a time. Each profile's
+v2 snapshots live under `native-v2/<profileId>` inside the existing history
+state directory. Legacy snapshots remain available in Legacy mode.
+
+To switch back, choose **Legacy (WebSocket)** in the popup, restore the MCP
+command arguments to `-y bookmark-bridge`, and restart its MCP connection.
+Restarting Chrome or reconnecting the popup refreshes the browser connection.
+Restart the MCP connection after updating the server to refresh its tool list.
+
+For an unpacked development extension, build the v2 binary and run
+`bookmark-bridge register-native <extension-id>` with that binary before
+selecting Native Messaging. It remembers the ID alongside the published one.
+On macOS and Linux, set `BOOKMARK_BRIDGE_CHROME_USER_DATA_DIR` to the absolute
+user data directory when registering for a Chrome test profile outside the
+default location.
+
 ## Safety model
 
 Three mechanisms, in the order they engage.
@@ -156,20 +196,16 @@ Read these before trusting the output.
 
 ## Tests
 
-`cd mcp && cargo test` runs the real binary against a fake extension: a
-WebSocket client holding an in-memory tree. The destructive paths are covered
-without a browser, including restoring a deleted subtree under new ids, refusing
-to mutate when no snapshot can be taken, and two sessions sharing one extension
-through the peer relay.
-
-Two release-blocking defects came out of writing these, both invisible on a
-machine that had already been set up once.
+`cd mcp && cargo test --locked` exercises the MCP server against a fake browser
+extension with an in-memory tree. The test harness uses temporary state and
+does not read your real Chrome bookmarks.
 
 ## Tools
 
 | | |
 | --- | --- |
 | `bookmarks_tree` `_search` `_children` | read |
+| `bookmarks_find_duplicates` | groups identical URLs and lists each bookmark's ID, title and parent folder ID; pass `folderId` to scan a folder and its descendants |
 | `bookmarks_update` `_move` `_create` `_remove` `_removeTree` | single change, each accepts `expect` |
 | `bookmarks_batch` | up to 200 changes at once, per-item `expect` |
 | `history_log` `_restore` `_drift` | snapshots, rollback, what changed since the agent last ran |
@@ -177,11 +213,10 @@ machine that had already been set up once.
 
 ## Privacy
 
-The extension holds `bookmarks` and `storage`. It connects only to
-`127.0.0.1` and turns away handshakes carrying an `http(s)` origin, so a web page
-cannot reach it. Nothing goes anywhere else. The token stops a page; it does not
-stop another process on this machine, which can read the token file just as
-easily.
+The extension holds `bookmarks` and `storage`. Native Messaging also requires
+an optional permission and uses Chrome's extension allowlist. Legacy mode uses
+`127.0.0.1` and rejects handshakes carrying a web origin. Both transports keep
+bookmark data on this computer.
 
 ## License
 

package/bin/bookmark-bridge.mjs

@@ -1,14 +1,11 @@
 #!/usr/bin/env node
-// Fetches the prebuilt server for this platform on first run, then hands over to
-// it. An MCP client launches this over stdio, so nothing may be written to
+// Verifies and unpacks the bundled server, then hands over to it.
+// An MCP client launches this over stdio, so nothing may be written to
 // stdout that is not protocol: progress goes to stderr.
 import {spawn} from 'node:child_process';
 import {createHash} from 'node:crypto';
-import {createWriteStream} from 'node:fs';
 import {chmod, mkdir, mkdtemp, readFile, rename, rm, stat} from 'node:fs/promises';
-import {tmpdir} from 'node:os';
 import {dirname, join} from 'node:path';
-import {pipeline} from 'node:stream/promises';
 import {fileURLToPath} from 'node:url';
 
 const here = dirname(fileURLToPath(import.meta.url));
@@ -36,7 +33,7 @@ if (!target) {
   die(`no prebuilt server for ${key}. Build from source: https://github.com/${REPO}`);
 }
 
-// Cached per version, so upgrading the package fetches a matching server rather
+// Cached per version, so upgrading the package unpacks a matching server rather
 // than silently reusing an old one.
 const cacheDir = join(here, '..', '.bin', pkg.version);
 const binary = join(cacheDir, `bookmark-bridge${EXE}`);
@@ -45,50 +42,31 @@ async function exists(path) {
   try { await stat(path); return true; } catch { return false; }
 }
 
-async function fetchOrDie(url, what) {
-  const res = await fetch(url, {redirect: 'follow'});
-  if (!res.ok) die(`could not download ${what} (HTTP ${res.status})\n  ${url}`);
-  return res;
-}
-
 async function install() {
-  const tag = `v${pkg.version}`;
+  const assets = join(here, '..', 'release-assets');
   const name = `bookmark-bridge-${target}.tar.gz`;
-  const base = `https://github.com/${REPO}/releases/download/${tag}`;
-
-  process.stderr.write(`bookmark-bridge: fetching ${tag} for ${key}\n`);
-  const sums = (await (await fetchOrDie(`${base}/SHA256SUMS`, 'checksums')).text());
-  const line = sums.split('\n').find((l) => l.trim().endsWith(name));
-  if (!line) die(`no checksum published for ${name} in ${tag}`);
-  const expected = line.trim().split(/\s+/)[0];
-
-  const staging = await mkdtemp(join(tmpdir(), 'bookmark-bridge-'));
-  const archive = join(staging, name);
+  const sums = await readFile(join(assets, 'SHA256SUMS'), 'utf8');
+  const expected = sums.split('\n').map(line => line.trim().split(/\s+/))
+    .find(([, file]) => file === name)?.[0];
+  if (!expected) throw new Error(`no checksum bundled for ${name}`);
+  const archive = join(assets, name);
+  const actual = createHash('sha256').update(await readFile(archive)).digest('hex');
+  if (actual !== expected) throw new Error(`checksum mismatch for ${name}`);
+
+  await mkdir(dirname(cacheDir), {recursive: true});
+  const staging = await mkdtemp(join(dirname(cacheDir), '.install-'));
   try {
-    await pipeline(
-      (await fetchOrDie(`${base}/${name}`, 'the server')).body,
-      createWriteStream(archive),
-    );
-
-    // Never run a binary that does not match what the release published.
-    const actual = createHash('sha256').update(await readFile(archive)).digest('hex');
-    if (actual !== expected) {
-      die(`checksum mismatch for ${name}\n  expected ${expected}\n  got      ${actual}`);
-    }
-
     await new Promise((resolve, reject) => {
       const tar = spawn('tar', ['-xzf', archive, '-C', staging], {stdio: 'inherit'});
       tar.on('error', reject);
       tar.on('exit', (code) => code === 0 ? resolve() : reject(new Error(`tar exited ${code}`)));
     });
 
-    await mkdir(dirname(cacheDir), {recursive: true});
-    // Rename is atomic, so two clients starting at once cannot see a half-written
-    // directory.
-    await rm(cacheDir, {recursive: true, force: true});
-    await rename(join(staging, `bookmark-bridge-${target}`), cacheDir);
-    // Windows has no execute bit; the archive already carries it elsewhere.
-    if (process.platform !== 'win32') await chmod(binary, 0o755);
+    const unpacked = join(staging, `bookmark-bridge-${target}`);
+    if (process.platform !== 'win32') await chmod(join(unpacked, `bookmark-bridge${EXE}`), 0o755);
+    // Publish the whole directory. Another client may already have installed it.
+    try { await rename(unpacked, cacheDir); }
+    catch (e) { if (!(await exists(binary))) throw e; }
   } finally {
     await rm(staging, {recursive: true, force: true});
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bookmark-bridge",
-  "version": "0.1.2",
+  "version": "2.0.2",
   "description": "Chrome bookmarks as MCP tools, with every change recorded in git so it can be rolled back",
   "license": "MIT",
   "repository": {
@@ -13,8 +13,15 @@
   },
   "files": [
     "bin/",
+    "release-assets/",
     "README.md"
   ],
+  "scripts": {
+    "prepublishOnly": "node -e \"if (process.env.npm_config_tag !== 'native' || !require('fs').existsSync('release-assets/SHA256SUMS')) { console.error('Publish the bundled release with npm publish --tag native.'); process.exit(1); }\""
+  },
+  "publishConfig": {
+    "tag": "native"
+  },
   "engines": {
     "node": ">=18"
   },

package/release-assets/SHA256SUMS

@@ -0,0 +1,5 @@
+af0dc501199feb693a68cc1d433499e67a633f495fbce1e6f43c5e165f6b99a3  bookmark-bridge-aarch64-apple-darwin.tar.gz
+35968f8114af290d81638e97d5482c23457b0b72c5a6004eabec78a3739a13c8  bookmark-bridge-aarch64-unknown-linux-gnu.tar.gz
+67fae0592491c25bbb8caca61630dd4213d26fe83e09e2f03bf75a130c70efd6  bookmark-bridge-x86_64-apple-darwin.tar.gz
+d443279e1a1380f442b69df9c86072d40bb5980d550aba8050e6c84aa3fcf184  bookmark-bridge-x86_64-pc-windows-msvc.tar.gz
+3cc3b1480fd7fb6a39d7407d48bf528debe1216791bade50f1e95cfd5dd237b9  bookmark-bridge-x86_64-unknown-linux-gnu.tar.gz