---
name: bijection-browser-use
description: "Evaluate and integrate the Browser Use component with Bijection."
---

# Browser Use

A Bijection component for Browser Use Cloud - automate browser tasks with AI agents

- Package: @bijectionhq/browser-use
- Category: AI & Agents
- Status: Preview
- License: MIT
- Bijection source (repository access required): https://github.com/bijectionhq/browser-use/tree/8e37a347fe67379f6160844dd79b0f63ef87e7b2
- Upstream: https://github.com/Cheggin/browser-use-convex-component/tree/14bba13a1a7f7d22dad82369e8aec2600032f2ce
- Documentation: https://docs.bijection.com/components/using
- Directory: https://bijection.com/components/browser-use

## Get the source

Bijection repository access is required. Request access at https://bijection.com/contact.

```sh
git clone https://github.com/bijectionhq/browser-use.git
cd browser-use
git checkout 8e37a347fe67379f6160844dd79b0f63ef87e7b2
```

## Before using this component

Read the package README at the recorded revision for setup, dependencies, and API examples. Upstream documentation describes the original package and may differ from the Bijection adaptation. This is a source candidate for evaluation. Catalog inclusion does not establish npm availability or runtime qualification. Check compatibility with your SDK and deployment before adoption. External providers run their own compute.

## Integration workflow

1. Read the source README and package manifest at the recorded revision.
2. Confirm the required SDK, dependency availability, and runtime compatibility.
3. Follow the component's documented setup and configuration. Never invent an npm install command from a catalog package name.
4. Keep credentials in the project's existing secret store.
5. Follow the project's execution rules for verification and report what was actually checked.

## Original upstream skill

The following guidance describes browser-use-convex-component. Its installation commands and APIs refer to the upstream package. Evaluate compatibility with the Bijection source separately.


# Browser Use Convex Component

## Instructions

This component integrates Browser Use Cloud's AI-powered browser automation API with Convex's reactive database. It provides persistent task tracking, session management, and browser profile storage while enabling real-time queries on automation status. Developers get a full-stack solution for browser automation with reactive subscriptions to task progress and results.

### Installation

```bash
npm install browser-use-convex-component
```

## Use cases

- **Web scraping workflows** where you need to track long-running scraping tasks and reactively update your UI as data is collected
- **E2E testing automation** that requires persistent browser sessions across multiple test runs with profile-based authentication
- **User onboarding automation** where you guide users through complex web flows and need to monitor completion status in real-time
- **Content management tasks** like bulk social media posting or form submissions that benefit from visual element highlighting and structured output
- **Competitive analysis tools** that automate data collection from multiple domains with proxy rotation and session persistence

## How it works

The component wraps the Browser Use Cloud API in Convex actions while storing all task, session, and profile data in your Convex database. You initialize the `BrowserUse` client with your component's API surface, then call methods like `createTask()` to start browser automation jobs that persist their status locally.

Tasks support comprehensive configuration including AI model selection, structured JSON output schemas, domain restrictions, and custom secrets injection. The component provides both actions for API calls (like `fetchTaskStatus()`) and queries for reactive data access (like `listTasks()` and `getTaskSteps()`), enabling real-time UI updates as automation progresses.

Session and profile management enables persistent browser states across automation runs. Sessions can use proxy rotation and country-specific routing, while profiles store authentication cookies and browser preferences. All data flows through Convex's reactive system, so your frontend automatically updates when task status changes or new automation results arrive.

## When NOT to use

- When a simpler built-in solution exists for your specific use case
- If you are not using Convex as your backend
- When the functionality provided by Browser Use Convex Component is not needed

## Resources

- [npm package](https://www.npmjs.com/package/browser-use-convex-component)
- [GitHub repository](https://github.com/Cheggin/browser-use-convex-component)
- [Live demo](https://cloud.browser-use.com/)
- [Convex Components Directory](https://www.convex.dev/components/browser-use)
- [Convex documentation](https://docs.convex.dev)