feat: enable Chrome extension Browser Use on Linux#36
Draft
cau1k wants to merge 35 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #33.
What
The adjacent installer config remains only as the same standalone-install fallback used by the Darwin host. Desktop-managed installs use registry-v2.
Validation
npm test— 126 Node tests + 57 Rust testscargo clippy --locked --manifest-path native/chrome-extension-host/Cargo.toml --all-targets -- -D warningsnpm run release:prod— built26.707.31123-launcher.351.2.27203.26575— Chrome spawned the host, opened the side panel, launched app-server, and completedping,getInfo, tab create/list/attach, CDP navigation, and runtime evaluation through the actual extension bridgeCurrent delivery target: Linux x86-64 with Google Chrome/compatible Chromium native messaging. Computer Use remains out of scope.