Skip to content

v0.0.2 — un-versioned harness cache + F7 phone-home/branding cut

Pre-release
Pre-release

Choose a tag to compare

@Alezander9 Alezander9 released this 27 Apr 02:04
· 2053 commits to main since this release
27d1d0a

v0.0.2 — Linux x64 prerelease

Second internal-testing build. Picks up two PRs since v0.0.1:

  • #11 (C8) — un-versioned harness cache. Harness is now extracted to ~/.cache/bcode/harness/ (no version subdir). On every launch the binary walks the embed map and overwrites baseline files (daemon.py, admin.py, skill .md files, pyproject.toml, etc.) — except helpers.py, which is preserved if it already exists. Net effect: agent edits to helpers.py survive every binary upgrade automatically; new curated skills + daemon fixes still land on upgrade.
  • #12 (F7) — phone-home and branding triage. XDG dirs ~/.config/opencode/~/.config/bcode/ (and data + state); opencode.dbbcode.db; project-level .opencode/.bcode/ and opencode.jsonbcode.json; 38 $schema URLs → bcode.sh; LLM provider attribution headers (HTTP-Referer, X-Title, X-Source, X-Cerebras-3rd-Party-Integration) → bcode.sh/bcode; MCP OAuth client_uribcode.sh; default system prompts rewritten to identify as BrowserCode while acknowledging OpenCode lineage; uninstall + TUI keybind + tip text. No XDG migration logicbcode reads the new paths only. Anyone who tested v0.0.1 will see fresh state under bcode/ and the legacy opencode/ dirs are not touched.
  • CRITICAL safety fix in #12. Upstream's auto-upgrade-on-launch was wired to query opencode-ai's npm/brew/scoop/choco/curl registries — on a bcode binary it would have silently replaced the binary with opencode on first launch. Disabled via BCODE_UPGRADE_DISABLED flag. Auto-upgrade is a no-op; manual bcode upgrade returns a friendly "download from GitHub Releases" error.

Install (Linux x64)

# raw binary
curl -L -o bcode https://github.com/browser-use/browsercode/releases/download/v0.0.2/bcode-linux-x64
chmod +x bcode
./bcode --version

# or tarball
curl -L -o bcode.tar.gz https://github.com/browser-use/browsercode/releases/download/v0.0.2/bcode-linux-x64.tar.gz
tar xzf bcode.tar.gz
./bcode --version

Prereqs

  • Linux x64.
  • uv on PATH — required for browser_execute (the harness builds its venv on first call).
  • A Chromium-based browser running with remote debugging on, OR BU_CDP_WS=ws://... set explicitly. For headless on the same box: chrome-headless-shell --no-sandbox --headless --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-prof about:blank.
  • An LLM API key configured (e.g. ANTHROPIC_API_KEY, set via bcode auth login or bcode.json).

Verified

End-to-end on a fresh-state Sprite (no ~/.config/bcode/, no ~/.cache/bcode/):

  • bcode --version0.0.2.
  • First bcode run creates ~/.config/bcode/, ~/.local/share/bcode/bcode.db, ~/.cache/bcode/harness/ cleanly.
  • Harness extracts (104 files), uv builds the venv, browser_execute drives headless Chrome over CDP, goto_url("https://example.com") + page_info() returns Example Domain.
  • bcode upgrade <target> detects unknown install method and short-circuits to the friendly bcode error (does not install opencode).
  • /doc{title:"bcode",description:"bcode api"}. /<title>BrowserCode</title>.

Assets

  • bcode-linux-x64 — 141 MB raw ELF. sha256: 6829963e3534ef641ad3a5e1aa51fcdbde7e5858e1b30d42c83d9f64d907c7b9.
  • bcode-linux-x64.tar.gz — 50 MB gzipped. sha256: 471e79bdaff750d6f48965468ddba743939aabc4080f0250056f795912ed40de.

Built from 27d1d0a09 with OPENCODE_VERSION=0.0.2 OPENCODE_CHANNEL=latest.

What's still deferred

  • Other platforms (linux-arm64, darwin-x64/arm64, win32-x64). C1 ticket: GitHub Actions cross-platform builds.
  • One-line installer at bcode.sh/install. C4 + A1 (domain registration). Discussion thread queued.
  • bcode github subcommand wiring — points at OpenCode's GitHub App, not yet rewired. Whole feature.
  • OpenCode-as-a-provider upsell dialogs — only shown if user picks OpenCode as their LLM provider. Pending product call on whether to keep OpenCode as a usable provider option.
  • A6 — deny-list daemon.py/admin.py edits at the agent's edit tool layer (the un-versioned cache puts them at a stable path now).
  • Phase BFetchUse.Service (cloud-gated capability lift).