BeatBrowser 1.4.1

BeatBrowser 1.4.1

The npm package and matching extension downloads now include the current Agent setup and optional remote access tooling.

What changed

• Correct the Agent directory and workspace guides to match the npm release, including WorkBuddy setup. This patch changes documentation and version metadata only; runtime behavior matches 1.4.0.

• Include an opt-in remote adapter for compatible cloud agents: dedicated credentials, expiry/revocation, authenticated HTTP/MCP/WebSocket and a user-managed tunnel. Local mode remains the default; installation opens no remote listener.

• Detect WorkBuddy's current ~/.workbuddy/mcp.json path while preserving existing servers.

• Package the English/Chinese local/cloud guides, Agent directory and updated comparison visuals.

• Retain background TaskSpaces, identity-based recovery and cleanup from 1.3.2. The Chrome extension version matches the CLI; this release adds no new extension permissions.

Install or update

npm install --global @beatapi/beat-browser@1.4.1
beat-browser install --dry-run
beat-browser install
beat-browser extension

Finish active operations, reload the existing extension from the printed folder, restart the bridge and reconnect agents. Keep extension storage to retain task records. Inspect recovered pages before continuing. BeatGEO users should update the bundled dependency through BeatGEO instead of installing a second copy.

Validation and limits

Release checks cover unit tests, remote authentication and isolated mock-extension runtime, package contents, clean installation and MCP discovery. Remote tooling remains an opt-in preview: these checks do not certify each cloud client, public tunnel or signed-in website workflow. The extension behavior is unchanged apart from version metadata; no new real-browser acceptance is claimed by this release.

GitHub ZIP and CLI tarball downloads carry SHA-256 checksums. npm publication and GitHub assets are verified independently. This is an unpacked extension release, not a Chrome Web Store listing.

BeatBrowser 1.4.0

BeatBrowser 1.4.0

The npm package and matching extension downloads now include the current Agent setup and optional remote access tooling.

What changed

• Include an opt-in remote adapter for compatible cloud agents: dedicated credentials, expiry/revocation, authenticated HTTP/MCP/WebSocket and a user-managed tunnel. Local mode remains the default; installation opens no remote listener.
• Detect WorkBuddy's current ~/.workbuddy/mcp.json path while preserving existing servers.
• Package the English/Chinese local/cloud guides, Agent directory and updated comparison visuals.
• Retain background TaskSpaces, identity-based recovery and cleanup from 1.3.2. The Chrome extension version matches the CLI; this release adds no new extension permissions.

Install or update

npm install --global @beatapi/beat-browser@1.4.0
beat-browser install --dry-run
beat-browser install
beat-browser extension

Finish active operations, reload the existing extension from the printed folder, restart the bridge and reconnect agents. Keep extension storage to retain task records. Inspect recovered pages before continuing. BeatGEO users should update the bundled dependency through BeatGEO instead of installing a second copy.

Validation and limits

Release checks cover unit tests, remote authentication and isolated mock-extension runtime, package contents, clean installation and MCP discovery. Remote tooling remains an opt-in preview: these checks do not certify each cloud client, public tunnel or signed-in website workflow. The extension behavior is unchanged apart from version metadata; no new real-browser acceptance is claimed by this release.

GitHub ZIP and CLI tarball downloads carry SHA-256 checksums. npm publication and GitHub assets are verified independently. This is an unpacked extension release, not a Chrome Web Store listing.

BeatBrowser 1.3.2

BeatBrowser 1.3.2

Tasks stay in the extension workspace without adding Chrome tab groups.

What changed

• Neither ordinary agent pages nor background TaskSpaces create native tab groups. View, take over, continue, stop and clear tasks from the popup or sidebar.
• Reload recovery uses Chrome page identities plus URL fingerprints. A full browser restart preserves task records and progress; explicitly reconnect pages before continuing. Matching URLs alone never transfer control.
• Existing v1 task groups migrate conservatively and are ungrouped after their page identity is saved. Renamed groups, moved pages and user-associated pages remain protected.
• Cleanup ungroups recognized legacy pages before closing them. Page-list failures offer Retry or an extension reload hint; empty inventories hide the unused close button.

Install or update

npm install --global @beatapi/beat-browser@1.3.2
beat-browser install --dry-run
beat-browser install
beat-browser extension

Load the printed extension folder, or extract the matching GitHub extension ZIP into a permanent directory. Finish active operations, reload the existing extension, restart the bridge and reconnect agents. Keep extension storage to retain task records. Inspect recovered pages before continuing.

The release includes matching extension ZIP and CLI tarball downloads, with SHA-256 checksums. npm publication and GitHub assets are verified separately.

Validation and limits

Unit tests, clean package installation, isolated real Chromium task/UI checks and extension-reload/browser-restart recovery checks cover this release. Full browser restart intentionally requires explicit page reassociation. These checks do not establish macOS native focus behavior or every agent client's compatibility. Previously saved, already closed Chrome groups may need removal in Chrome itself.

BeatBrowser 1.3.1

BeatBrowser 1.3.1

Your everyday Chrome, now a workspace for AI agents.

What changed

• Background TaskSpaces in your existing signed-in Chrome profile, with named pages, progress, takeover, pause, resume and stop. MCP, CLI and the JavaScript SDK share one local bridge.
• Task recovery across extension reloads and browser restarts. Unfinished tasks restore paused; missing pages can be explicitly reassociated. No uncertain input is replayed.
• Single-task cleanup, batch cleanup and a Browser pages inventory for associated tabs, including retained legacy pages. User-associated, handed-over and moved pages are protected.
• A compact Chinese/English workspace, refreshed BeatAPI styling and local fonts. Language preferences stay on your device.
• Current-window focus checks, disconnected-page diagnostics, bounded screenshot failures and request evidence.
• Updated installation guides, project cover and package documentation. Matching CLI and extension downloads are attached below.

Install or update

npm install --global @beatapi/beat-browser@1.3.1
beat-browser install --dry-run
beat-browser install
beat-browser extension

Version 1.3.1 is available on npm and GitHub. The matching beat-browser-cli.tgz archive is also attached to this release for direct installation.

Load the printed extension folder, or extract beat-browser-extension.zip into a permanent directory and load that folder in Chrome. Load only one copy per profile. The ZIP is the extension, not the local MCP server. SHA-256 files accompany both downloads.

For an update, finish active operations, reload the existing extension, restart the local bridge and reconnect Agent clients. Keep local extension storage so task records survive. Inspect recovered pages before continuing. Run beat-browser doctor --json; readiness requires both ok and extensionOnline.

Verification and limits

The release workflow runs unit tests, syntax/security checks, clean package installation and extension packaging. Isolated real Chromium fixtures cover task recovery and workspace controls; they do not certify every Agent client or macOS foreground-focus behavior.

Task windows share the selected profile's logins. Native windows or website popups can still gain focus; minimized headed screenshots remain limited. This is an unpacked Chrome extension, not a Chrome Web Store listing. Normal mode needs no BeatBrowser account or key. Optional Fast JEV requires a BeatAPI key and explicit consent.

Installation · Workspace acceptance · Task recovery · Privacy

BeatBrowser 1.2.2

BeatBrowser 1.2.2

Your Chrome. Your choice of agent.

• Direct Chrome extension ZIP and matching local CLI downloads from GitHub, including a stable latest-download URL and SHA-256 checksums.
• Clear instructions for ZIP extraction, Chrome's Load unpacked control, local MCP setup and updates.
• Extension archives include the MIT license and privacy notice; the public manifest key is removed from the archive.
• Matching CLI/extension versions, archive regression checks and npm 10/11/12 package-check compatibility.
• Updated BeatBrowser brand mark and X draft playbooks that hand the final Reply click to the user.

Install

Download beat-browser-extension.zip below and extract it into a permanent folder. Open chrome://extensions, enable Developer mode and choose Load unpacked. Select the extracted folder containing manifest.json.

The extension alone is not enough. Install the matching local CLI/MCP server:

npm install --global https://github.com/BeatAPI/beat-browser/releases/download/v1.2.2/beat-browser-cli.tgz
beat-browser install --dry-run
beat-browser install

The CLI download has a separate CLI-SHA256SUMS.txt checksum. npm registry publication is a separate step; the GitHub CLI download works even while that publication is pending. You can also install from the matching source tag:

git clone --branch v1.2.2 https://github.com/BeatAPI/beat-browser.git
cd beat-browser
npm ci
node src/cli.js install --dry-run
node src/cli.js install

Load only one copy of the extension, restart your MCP client and run beat-browser doctor --json (or node src/cli.js doctor --json from source). Setup is ready when ok and extensionOnline are true.

Check the ZIP against SHA256SUMS.txt if desired. This is an unpacked extension download, not a Chrome Web Store listing. Normal mode needs no BeatBrowser account or key; Fast JEV is optional and requires a BeatAPI key and explicit cloud consent. Connect trusted agents; tool results reach your chosen agent/provider.

For updates, keep a permanent extension folder, replace its files with the matching release, reload it in Chrome and restart your agent.