docs: add tested Browser Use setup inside containers - #372
Open
MagMueller wants to merge 1 commit into
Open
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.
Add a Browser Use guide and one navigation entry. The coding agent uses Chrome inside its Container Use environment instead of a host desktop browser.
The setup explicitly installs uv: browser-use install calls uvx, which a pip-only setup does not provide. It then starts headless Chrome inside the container and points the CLI at its local CDP endpoint with BU_CDP_URL.
Validation against main 2e43e62:
Only docs/browser-use.mdx and one docs/docs.json navigation line change. No runtime, default image, or secret handling changes. The no-sandbox flag is limited to Chrome inside the isolated container, not the host. Both test containers were removed after execution.