Releases: browser-use/browsercode
v0.1.5
v0.1.4
v0.1.3
Patch on v0.1.2. Adds: webfetch routes through fetch-use when BROWSER_USE_API_KEY is set, giving Chrome TLS fingerprint + residential proxy + session cookies; opt out via experimental.fetch_use: false in opencode.json (#49). browser_execute now takes a required description field that surfaces as the TUI title (#51). Fixes: Way 2 docs + threaded timeoutMs through the DevToolsActivePort poll (#48); laminar drains OTel processors before process.exit() so final agent spans aren't dropped (#50). Skills slimmed to BROWSER.md + cloud-browser.md — the inherited interaction-skills/ set is gone pending data-driven re-introduction (#52). No data-dir wipe needed.
v0.1.2
Patch on v0.1.1. Adds: browser_execute automatically attaches every Page.captureScreenshot result to the next assistant turn as an image part — model sees the screenshot natively as vision input, no decode/save/read dance from inside the snippet (#47). Same channel read and webfetch use for image files.
Eval harnesses: when BCODE_SCREENSHOT_DIR=<path> is set, the same hook also writes each screenshot to disk for offline judge consumption.
No data-dir wipe needed.
v0.1.1
v0.1.0 — TS harness port
Breaking: TS harness port. v0.1.0 has no uv requirement and is fully incompatible with v0.0.x state.
The browser harness moved from a Python-via-uv-run subprocess to in-process TypeScript. browser_execute now takes JS, not Python. Reusable code lives per-project at <projectRoot>/.bcode/agent-workspace/ as plain .ts files; the agent imports them with await import("/abs/path?t=" + Date.now()) (no auto-loaded helpers file). git clone && cd && bcode shares the agent's scripts with the project.
browser_execute is now the only browser tool. The agent owns the connection — it calls session.connect(...) from inside a snippet for local Chrome (via chrome://inspect or a debug-port launch) and for Browser Use cloud browsers (via fetch against the BU API). See {{SKILLS_DIR}}/BROWSER.md and {{SKILLS_DIR}}/cloud-browser.md for the patterns.
Before upgrading: rm -rf ~/.local/share/bcode/ ~/.cache/bcode/. No migration path.
Cloud browsers require BROWSER_USE_API_KEY in the environment (get one at https://browser-use.com).
Gains: no uv install, single-process, faster cold starts, instant cancellation on yield-points, cleaner TUI streaming, native Windows path support (no AF_UNIX sun_path budget hacks).
v0.0.10
Automated build for v0.0.10.
v0.0.9
Automated build for v0.0.9.
v0.0.8
Automated build for v0.0.8.
v0.0.7
Automated build for v0.0.7.