<!-- This is an auto-generated description by cubic. -->
## Summary by cubic
Adds a simple browser-use install CLI command to install Chromium +
system deps in one step. Updates docs to use the new command, and fixes
the basic search example and an AGENTS.MD merge conflict.
- **New Features**
- Added install subcommand to browser_use CLI that runs Playwright’s
Chromium install with deps and can run before other CLI dependencies
load.
- **Docs**
- Replaced Playwright install instructions with uvx browser-use install
in README, Quickstart, and vibetest example.
- Added Mac/Linux and Windows tabs for virtualenv activation in
AGENTS.MD.
<!-- End of auto-generated description by cubic. -->
Auto-generated PR for: eval on pr
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> Add a CI workflow to trigger and report PR evaluation runs via an
external API for authorized authors.
>
> - **CI/GitHub Actions**:
> - **New workflow** `/.github/workflows/eval-on-pr.yml` to auto-trigger
PR evaluation on `pull_request` (`opened`, `synchronize`, `reopened`).
> - Runs only for authors with `OWNER`/`MEMBER`/`COLLABORATOR`
association.
> - Calls external eval API via `curl` using `secrets.EVAL_PLATFORM_URL`
and `secrets.EVAL_PLATFORM_KEY`; passes `commitSha`, `prNumber`,
`branchName`, `githubRepo`, and `testCase` (from `vars.EVAL_TEST_CASE`
defaulting to `InteractionTasks_v6`).
> - Parses response with `jq` to determine success; posts a PR comment
via `actions/github-script@v7` indicating start or failure.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c23137f21e. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
- Add branchName parameter to API call
- This allows the UI to show the actual PR branch instead of 'main'
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Hi Team
I am one of the maintainers of
[OpenLIT](https://github.com/openlit/openlit). Adding an integration doc
for OpenLIT. Would prefer to have refactored the Observability doc but
did not want to do it without taking input from the team.
DO let me know what would be the best way to do this, A seperate doc for
each observability tool or mention in the same main observability
documentation
<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Added an OpenLIT monitoring guide for OpenTelemetry-native tracing in
Browser Use, covering setup, usage, configuration, self-hosted
deployment, and integrations. Updated docs.json to include the new page
in the Monitoring section.
<!-- End of auto-generated description by cubic. -->
Magnus Müller