From 05cd30482af0090af178f9f1e664560f8bb47881 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 2 Jul 2026 18:30:13 +0000 Subject: [PATCH] Release browse@0.9.2 --- .changeset/cli-named-contexts.md | 5 ----- .changeset/curvy-mangos-attend.md | 9 --------- .changeset/honor-forwarded-daemon-api-key.md | 5 ----- .changeset/remove-browse-refs.md | 5 ----- packages/cli/CHANGELOG.md | 16 ++++++++++++++++ packages/cli/package.json | 2 +- 6 files changed, 17 insertions(+), 25 deletions(-) delete mode 100644 .changeset/cli-named-contexts.md delete mode 100644 .changeset/curvy-mangos-attend.md delete mode 100644 .changeset/honor-forwarded-daemon-api-key.md delete mode 100644 .changeset/remove-browse-refs.md diff --git a/.changeset/cli-named-contexts.md b/.changeset/cli-named-contexts.md deleted file mode 100644 index 25796bbd5..000000000 --- a/.changeset/cli-named-contexts.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"browse": patch ---- - -Add named contexts to the CLI so you can reuse a Browserbase context by a memorable name instead of its ID. `browse cloud contexts create --name ` saves a local name→ID alias (stored at `(XDG_CONFIG_HOME||~/.config)/browserbase/contexts.json`, honoring `BROWSERBASE_CONFIG_DIR`), `browse cloud contexts add ` names a context you already have, `browse cloud contexts list` shows your saved names, and any place that accepts a context ID — `contexts get|update|delete` and `sessions create --context-id` — now also accepts a saved name. Deleting a context prunes its local alias, and a typo'd name fails with a "did you mean?" hint instead of a cryptic API error. The map is purely client-side: it stores the same IDs the API already returns, and a missing or corrupt file degrades to "no saved contexts" rather than erroring. diff --git a/.changeset/curvy-mangos-attend.md b/.changeset/curvy-mangos-attend.md deleted file mode 100644 index 7b751a6d3..000000000 --- a/.changeset/curvy-mangos-attend.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"browse": patch ---- - -Add `--verified` and `--proxies` to remote driver sessions so `browse open --remote --verified --proxies` opens a Verified and/or proxied Browserbase session in one command — no more create-then-attach with `--cdp`. - -- The flags are valid only with `--remote` (they are never implied, since that would silently switch to billed cloud sessions) and are sticky for the session's lifetime like `--headed`/`--headless`: a re-open requesting different settings fails with the usual stop-and-reopen error. -- Because the session is created through the normal remote path (not a raw `--cdp` attach), it keeps its Browserbase identity and the `browse_cli` attribution tag. `browse status` and `browse doctor` now surface the Browserbase session ID, the dashboard URL, the live-view (debug) URL, and the verified/proxies state. -- `--verified` requires a Browserbase Scale plan. diff --git a/.changeset/honor-forwarded-daemon-api-key.md b/.changeset/honor-forwarded-daemon-api-key.md deleted file mode 100644 index 766446be2..000000000 --- a/.changeset/honor-forwarded-daemon-api-key.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"browse": patch ---- - -Honor `BROWSERBASE_API_KEY` passed to an already-running driver daemon. Previously, if the first remote command started the daemon without a key, a later `BROWSERBASE_API_KEY=… browse open --remote` (or an exported key in a new shell) kept failing with "Missing BROWSERBASE_API_KEY" because the detached daemon captured `process.env` once at spawn time and never saw the new key. The client now forwards the caller's key over the (localhost, owner-only) driver socket with every command, and the daemon threads it straight into the Stagehand constructor when it creates the session — so an inline or exported key works without a manual `browse stop` and restart. The forwarded key is never written back into the daemon's `process.env`; its only home is the live session. Already-initialized warm sessions are untouched; the forwarded key only takes effect at session init. The local-only (CDP-only) build forwards nothing and remains free of any API-key code path. diff --git a/.changeset/remove-browse-refs.md b/.changeset/remove-browse-refs.md deleted file mode 100644 index 03425549b..000000000 --- a/.changeset/remove-browse-refs.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"browse": patch ---- - -Remove the `browse refs` command. It only re-printed the `xpathMap`/`urlMap` cached from the last `browse snapshot` — which `browse snapshot` already returns — so it was redundant, and it returned stale maps if the page had changed since that snapshot. diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index 48c10d263..4cbf6bd8c 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -1,5 +1,21 @@ # browse +## 0.9.2 + +### Patch Changes + +- [#2284](https://github.com/browserbase/stagehand/pull/2284) [`70b72d3`](https://github.com/browserbase/stagehand/commit/70b72d36907254fb3719ea5f520d37d362a11319) Thanks [@shrey150](https://github.com/shrey150)! - Add named contexts to the CLI so you can reuse a Browserbase context by a memorable name instead of its ID. `browse cloud contexts create --name ` saves a local name→ID alias (stored at `(XDG_CONFIG_HOME||~/.config)/browserbase/contexts.json`, honoring `BROWSERBASE_CONFIG_DIR`), `browse cloud contexts add ` names a context you already have, `browse cloud contexts list` shows your saved names, and any place that accepts a context ID — `contexts get|update|delete` and `sessions create --context-id` — now also accepts a saved name. Deleting a context prunes its local alias, and a typo'd name fails with a "did you mean?" hint instead of a cryptic API error. The map is purely client-side: it stores the same IDs the API already returns, and a missing or corrupt file degrades to "no saved contexts" rather than erroring. + +- [#2282](https://github.com/browserbase/stagehand/pull/2282) [`b8132f6`](https://github.com/browserbase/stagehand/commit/b8132f6a3350ba5682f6ead07d72f86d34286b16) Thanks [@shrey150](https://github.com/shrey150)! - Add `--verified` and `--proxies` to remote driver sessions so `browse open --remote --verified --proxies` opens a Verified and/or proxied Browserbase session in one command — no more create-then-attach with `--cdp`. + + - The flags are valid only with `--remote` (they are never implied, since that would silently switch to billed cloud sessions) and are sticky for the session's lifetime like `--headed`/`--headless`: a re-open requesting different settings fails with the usual stop-and-reopen error. + - Because the session is created through the normal remote path (not a raw `--cdp` attach), it keeps its Browserbase identity and the `browse_cli` attribution tag. `browse status` and `browse doctor` now surface the Browserbase session ID, the dashboard URL, the live-view (debug) URL, and the verified/proxies state. + - `--verified` requires a Browserbase Scale plan. + +- [#2280](https://github.com/browserbase/stagehand/pull/2280) [`39d7638`](https://github.com/browserbase/stagehand/commit/39d7638022b742f9d24776b6dc5d70a992aaeabf) Thanks [@shrey150](https://github.com/shrey150)! - Honor `BROWSERBASE_API_KEY` passed to an already-running driver daemon. Previously, if the first remote command started the daemon without a key, a later `BROWSERBASE_API_KEY=… browse open --remote` (or an exported key in a new shell) kept failing with "Missing BROWSERBASE_API_KEY" because the detached daemon captured `process.env` once at spawn time and never saw the new key. The client now forwards the caller's key over the (localhost, owner-only) driver socket with every command, and the daemon threads it straight into the Stagehand constructor when it creates the session — so an inline or exported key works without a manual `browse stop` and restart. The forwarded key is never written back into the daemon's `process.env`; its only home is the live session. Already-initialized warm sessions are untouched; the forwarded key only takes effect at session init. The local-only (CDP-only) build forwards nothing and remains free of any API-key code path. + +- [#2297](https://github.com/browserbase/stagehand/pull/2297) [`c18ab34`](https://github.com/browserbase/stagehand/commit/c18ab345e00451237ebd2bcf3567a76bbf1e52a3) Thanks [@shrey150](https://github.com/shrey150)! - Remove the `browse refs` command. It only re-printed the `xpathMap`/`urlMap` cached from the last `browse snapshot` — which `browse snapshot` already returns — so it was redundant, and it returned stale maps if the page had changed since that snapshot. + ## 0.9.1 ### Patch Changes diff --git a/packages/cli/package.json b/packages/cli/package.json index 32f572273..c49660019 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "browse", - "version": "0.9.1", + "version": "0.9.2", "description": "Unified Browserbase CLI for browser automation and cloud APIs.", "type": "module", "private": false,