---
next_cursor: eyJzY29yZSI6MCwic2VxIjo5MjEsInNpbmNlIjpudWxsLCJ0b29sIjoiYnJvd3NlIiwidiI6MX0
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=browse&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo5MjEsInNpbmNlIjpudWxsLCJ0b29sIjoiYnJvd3NlIiwidiI6MX0
items: 10
---
# sincecutoff.com changes: browse

## browse driver daemon adds open, status, and stop commands (browse, 2026-05-15)
Published 2026-10-16
- slug: browse-driver-daemon-adds-open-status-and-stop-commands-3c15201f03d7
- score: 0.94

How to use it:

If you need to open or manage the browse driver daemon, use its top-level `open`, `status`, and `stop` commands. The official documentation for browse 0.6.0 did not surface, so the runnable command forms and their parameters could not be verified.

- why_it_matters: Open and manage a browser driver daemon for repository browser work.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#060>
- gotchas: "Version: 0.6.0"; "This is described as the initial daemon foundation."

## browse skills add installs site-specific skills (browse, 2026-05-15)
Published 2026-10-16
- slug: browse-skills-add-installs-site-specific-skills-63431b1f02cf
- score: 0.92

How to use it:

When repository work involves a site-specific skill, run `browse skills add <domain>/<task>` to install it. The 0.6.0 release note documents the command but not its arguments; the invocation is not confirmed in docs at that version.

- why_it_matters: Install a site-specific skill for repository work involving that site.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#060>
- gotchas: "Version: 0.6.0"

## browse skills install installs the bundled CLI skill (browse, 2026-05-15)
Published 2026-10-16
- slug: browse-skills-install-installs-the-bundled-cli-skill-656badaf09e3
- score: 0.93

How to use it:

When using Browse in a repository workflow, run `browse skills install` to install the bundled Browse CLI skill.

Examples:

```
browse skills install
```

- why_it_matters: Install the bundled Browse CLI skill when using Browse in a repository workflow.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#060>, <https://github.com/browserbase/stagehand/releases>, <https://github.com/team2027/browserbase-skills/blob/main/skills/browserbase-cli/SKILL.md>
- gotchas: "Version: 0.6.0"; "Prerequisite: The Browse CLI must be installed; the official Browserbase CLI skill documents installation with `npm install -g browse`."; "The installed skill is the bundled Browse CLI skill."

## browse skills list and find discover the Browse.sh catalog (browse, 2026-05-17)
Published 2026-10-16
- slug: browse-skills-list-and-find-discover-the-browse-sh-catalog-478c1a32d2ff
- score: 0.95

How to use it:

When you need to discover skills in the Browse.sh catalog, use `browse skills list` to list them or `browse skills find` to search. The version 0.7.0 release note confirms both commands; official docs do not provide their arguments or options.

- why_it_matters: Find or list skills available in the Browse.sh catalog while working on a repository.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#070>
- gotchas: "Version: 0.7.0"

## browse cloud fetch supports raw and schema-based JSON output formats (browse, 2026-05-21)
Published 2026-10-16
- slug: browse-cloud-fetch-supports-raw-and-schema-based-json-output-formats-99949b623261
- score: 0.93

How to use it:

When fetching a page for a coding workflow, run `browse cloud fetch <url>` for Markdown, or choose `--format raw` or `--format json --schema <schema>` for other output formats.

Examples:

```
browse cloud fetch <url>
```

```
browse cloud fetch <url> --format raw
```

```
browse cloud fetch <url> --format json --schema <schema>
```

- why_it_matters: Fetch content through the Browse CLI in a format suitable for processing in a coding workflow.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#080>, <https://app.unpkg.com/browse%400.8.3/files/README.md>, <https://app.unpkg.com/browse%400.9.2/files/skills/browse/SKILL.md>
- gotchas: "Version: 0.8.0"; "<url> (required): Page URL to fetch."; "--format raw: Return the original response body."; "--format json: Use structured JSON extraction; pair with `--schema <schema>`."; "--schema <schema>: Schema for structured extraction; documented with `--format json`."; "Prerequisite: Install the CLI with `npm install -g browse`."; "Prerequisite: Cloud API commands require `BROWSERBASE_API_KEY`."; "Docs conflict: The parameter and format details were found in browse 0.9.2 documentation, newer than the card's 0.8.0 version; 0.8.3 README only confirms the command and Markdown default."

## browse managed local sessions accept Chrome launch argument flags (browse, 2026-06-17)
Published 2026-10-16
- slug: browse-managed-local-sessions-accept-chrome-launch-argument-flags-96d412732017
- score: 0.90

How to use it:

When using a managed local browser session, pass Chrome launch arguments with `--chrome-arg <flag>`, remove selected defaults with `--ignore-default-chrome-arg <flag>`, or disable Chrome defaults with `--no-default-chrome-args`.

Examples:

```
browse open <url> --local --chrome-arg <flag>
```

```
browse open <url> --local --ignore-default-chrome-arg <flag>
```

```
browse open <url> --local --no-default-chrome-args
```

- why_it_matters: When configuring a managed local browser session, control which Chrome launch arguments browse uses.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#085>, <https://github.com/browserbase/stagehand/blob/9971a7b3d8ecca255b4548cfb9128657c053cca7/packages/cli/src/commands/open.ts>, <https://github.com/browserbase/stagehand/blob/9971a7b3d8ecca255b4548cfb9128657c053cca7/packages/cli/CHANGELOG.md#085>
- gotchas: "Version: 0.8.5"; "<url> (required): URL to open."; "--local: Select a local browser session; required for this task."; "--chrome-arg <flag>: Repeatable; appends a Chrome launch argument on top of defaults."; "--ignore-default-chrome-arg <flag>: Repeatable; removes a selected default Chrome launch argument."; "--no-default-chrome-args: Launches without Chrome defaults."; "The flags apply to managed local browser sessions."; "`--chrome-arg <flag>` appends arguments on top of Chrome's defaults."; "`--ignore-default-chrome-arg <flag>` drops specific default arguments."; "`--no-default-chrome-args` launches without any of Chrome's defaults."

## browse screenshot saves a file by default (browse, 2026-06-25)
Published 2026-10-16
- slug: browse-screenshot-saves-a-file-by-default-e6cf5c406139
- score: 0.97

How to use it:

When capturing a page screenshot with the v0.9.0 `browse` CLI, run `browse screenshot` to save it in the current directory; pass `--base64` to retain the legacy base64 JSON stdout output. The official docs found do not document this changed CLI behavior, so usage and flag details are not_found.

- why_it_matters: Capture a screenshot while debugging or reviewing a page with the browse CLI.
- before: Bare `browse screenshot` invocations printed `{ "base64": "..." }` to stdout. Scripts that parsed that output can pass `--base64` to retain the contract.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#090>
- gotchas: "Version: 0.9.0"; "`--base64` is mutually exclusive with `--path`."; "Bare invocations save in the current directory, using a collision counter instead of overwriting."

## browse open remote sessions accepts --verified and --proxies (browse, 2026-07-02)
Published 2026-10-16
- slug: browse-open-remote-sessions-accepts-verified-and-proxies-75f430a4af32
- score: 0.98

How to use it:

When opening a remote Browserbase session with verification or proxies, run `browse open <url> --remote --verified --proxies`; `--verified` requires a Browserbase Scale plan. Keep those settings the same when reopening the session, and use `browse status` or `browse doctor` to inspect session details.

Examples:

```
browse open <url> --remote --verified --proxies
```

- why_it_matters: Open a URL in a remote Browserbase session configured for verification or proxies.
- before: Create a remote session separately, then attach with `--cdp`.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#092>, <https://github.com/browserbase/stagehand/blob/browse@0.9.2/packages/cli/CHANGELOG.md>
- gotchas: "Version: 0.9.2"; "<url> (required): URL to open."; "--remote (required): Selects the remote session mode; `--verified` and `--proxies` are valid only with this flag."; "--verified: Enables Browserbase Verified; requires a Scale plan. Must be used with `--remote`."; "--proxies: Enables Browserbase proxies. Must be used with `--remote`."; "Prerequisite: A Browserbase Scale plan is required for `--verified`."; "`--verified` and `--proxies` are valid only with `--remote` and are never implied."; "`--verified` requires a Browserbase Scale plan."; "The verified/proxies settings are sticky for the session lifetime; requesting different settings on reopen fails with the usual stop-and-reopen error."

## browse functions secrets attach links a project secret by ID (browse, 2026-09-23)
Published 2026-10-16
- slug: browse-functions-secrets-attach-links-a-project-secret-by-id-3d81448726e6
- score: 0.90

How to use it:

When an existing project secret needs to be available to a published function, run `browse functions secrets attach` with the function ID and secret ID.

Examples:

```
browse functions secrets attach <functionId> <secretId>
```

- why_it_matters: Attach an existing project secret to a function that needs it.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#0110>, <https://github.com/browserbase/sdk-functions-node>
- gotchas: "Version: 0.11.0"; "<functionId> (required): ID of the function to attach the secret to; the docs say to use the ID from `builtFunctions[].id` in the publish output."; "<secretId> (required): ID of the existing secret to attach. The docs show the argument but do not further define it."; "Prerequisite: The project secret must already exist; the README shows creating it with `browse cloud secrets create BROWSERBASE_API_KEY --env BROWSERBASE_API_KEY`."; "Prerequisite: Publish the function first; the README describes attaching the secret to the published function and identifies its ID in the publish output."; "The project secret must already exist; attachment is by function ID."

## browse functions secrets detach removes an attachment while retaining the secret (browse, 2026-09-23)
Published 2026-10-16
- slug: browse-functions-secrets-detach-removes-an-attachment-while-retaining-the-secret-b845b33d34fb
- score: 0.98

How to use it:

When a function secret attachment should be removed while preserving the project secret, run `browse functions secrets detach`; the official docs found do not specify its arguments.

- why_it_matters: Remove a secret attachment from a function while keeping the project secret available.
- sources: <https://github.com/browserbase/stagehand/blob/main/packages/cli/CHANGELOG.md#0110>
- gotchas: "Version: 0.11.0"; "Detaching removes the attachment; it does not delete the project secret."

Next: https://sincecutoff.com/v1/changes.md?tool=browse&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo5MjEsInNpbmNlIjpudWxsLCJ0b29sIjoiYnJvd3NlIiwidiI6MX0
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->