@opencode/browse 0.0.3-dev.2 → 0.0.6-dev.18

package/dist/update-st5c8grg.mjs

@@ -0,0 +1,15 @@
+import {
+  updateJson2,
+  formatUpdateNotice2,
+  updateNotice2,
+  createUpdateWatcher2,
+  runUpdateCommand2
+} from "./main-w5sta7hq.mjs";
+import"./main-ha5bnd77.mjs";
+export {
+  createUpdateWatcher2 as createUpdateWatcher,
+  formatUpdateNotice2 as formatUpdateNotice,
+  runUpdateCommand2 as runUpdateCommand,
+  updateJson2 as updateJson,
+  updateNotice2 as updateNotice
+};

package/dist/version-6g6gtnra.mjs

@@ -0,0 +1,8 @@
+import {
+  opencodeBrowserVersion2,
+  opencodeBrowserBuildId2
+} from "./main-ppz7sv9s.mjs";
+export {
+  opencodeBrowserBuildId2 as opencodeBrowserBuildId,
+  opencodeBrowserVersion2 as opencodeBrowserVersion
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@opencode/browse",
-  "version": "0.0.3-dev.2",
+  "version": "0.0.6-dev.18",
   "description": "Browse: connect the extension to opencode, and drive your browser from any agent (CLI, MCP, Playwright).",
   "type": "module",
   "license": "MIT",
@@ -38,13 +38,16 @@
     "ws": "8.22.0"
   },
   "devDependencies": {
+    "@clack/core": "1.5.1",
     "@types/bun": "1.4.0",
     "@types/chrome": "0.3.4",
     "@types/node": "26.6.4",
     "@types/pngjs": "6.0.5",
     "@types/ws": "8.18.2",
     "@typescript/native-preview": "7.0.0-dev.20260707.2",
-    "jsonc-parser": "3.3.1"
+    "jsonc-parser": "3.3.1",
+    "smol-toml": "1.9.1",
+    "yaml": "2.9.1"
   },
   "publishConfig": {
     "access": "public"

package/skills/browse/SKILL.md

@@ -59,22 +59,25 @@ are excluded from Browse's inventory. `page.title()` reads time out
 after five seconds if the page execution context remains unavailable; the read
 timeout does not close or replace the tab.
 
-A bare CLI execute creates a fresh session-owned page and prints the exact
-`--session <id>` continuation command, or you can pass a descriptive session
-name (including an optional emoji, which appears directly on the browser tab
-group). Every later CLI call must pass that id or set
-`OPENCODE_BROWSER_SESSION`; bare execute never guesses from human-shell current
-state.
+A bare CLI execute inside OpenCode defaults to `oc-<opencode-session-id>` (or
+creates a fresh session-owned page outside OpenCode and prints its
+`--session <id>` continuation command). Pass `--rm` for a one-shot session whose
+tabs close as soon as the command finishes, `--timeout-ms <ms>` when a script
+needs longer than the 60s default (paused while `handoff()` waits on the user),
+or pass a descriptive session name (including an optional emoji, which appears
+directly on the browser tab group):
 
 ```bash
 opencode-browser session new "🎙️ elevenlabs"
 opencode-browser execute --session "🎙️ elevenlabs" 'return page.url()'
 opencode-browser execute 'return page.url()'
+opencode-browser execute --rm 'await page.goto("https://example.com"); return await page.title()'
 ```
 
 MCP keeps one implicit process session. Omit `session` for that normal path, or
 call `session_new` and pass an explicit id when one MCP process needs multiple
 sessions.
+Each session stays in the browser selected at creation (the default if omitted); reconnect that browser or start a new session to use another.
 
 Tabs you open live in the background of the user's window, in your session's
 tab group, collapsed at the start of their tab strip, so the user keeps working
@@ -914,12 +917,13 @@ Common diagnoses:
   not cancel the underlying read or trigger page replacement. A cached
   `page.url()` read can still work; retry the page read after the page settles.
   Ordinary missing-locator timeouts do not receive this diagnostic.
-- `connected:false`: run a relay-backed command and allow the extension startup
-  or alarm wake-up to reconnect. A sleeping extension wakes on a 30-second
-  alarm, so the command waits up to 35 seconds. Reload the unpacked extension
-  only if that loop does not recover.
-- Incompatible extension protocol: update either the extension or npm package;
-  exact extension and relay release versions do not need to match.
+- `connected:false`: check `extension.pairingState` and follow `extension.nextStep`.
+  `unpaired` or `refused` means Browse is installed: re-run install to pair it, **not** the store.
+  `paired-offline`: reopen the paired browser profile and enable Browse; its worker wakes every 30 seconds.
+  `not-seen`: the relay hasn't heard from a browser. If Browse is already added, open that browser and
+  rerun install. Otherwise follow install's store or Load unpacked steps.
+- Incompatible extension protocol: follow `extension.nextStep`. For an older unpacked extension after setup,
+  ask the user: “Reload Browse on your browser's extensions page (↻).” Running setup again does not reload older workers.
 - Competing browser/profile connections: the active browser is preserved and
   additional connections are rejected. Use one browser/profile per relay;
   repeatedly creating sessions or resetting tabs does not switch browsers.
@@ -939,12 +943,10 @@ Common diagnoses:
   unique URL substring or explicit index.
 - All targets disappeared: dismissing Chromium's debugging banner detaches every
   tab. Ask the user to click the toolbar button on it again.
-- Extension not connecting, status page says "Not paired" or "didn't pair": the
-  browser needs its own key from the relay. Unpacked installs are paired by
-  `opencode-browser install` (or `bun run setup`); otherwise run
-  `opencode-browser pair` and have the user enter the code (it works once, within
-  10 minutes) under Connection on the status page. `pair --list` shows paired
-  browsers; `pair --revoke <browser>` unpairs one.
+- Extension installed but not paired: re-run `npx @opencode/browse install` to open its pairing link
+  (from a checkout, `bun run setup`). To pair manually, run `npx @opencode/browse pair`
+  (from the checkout root, `node cli/dist/cli.mjs pair`). This starts the relay. Have the user enter
+  the code in Browse's Options and click Connect. The terminal confirms which browser paired.
 - HTTP 401 from the relay: clients need the relay token from the data root
   (`relay-token`); the CLI and MCP server send it, other CDP clients must add
   `Authorization: Bearer <token>` or `?opencodeBrowserToken=<token>`.