Skip to content

2.1.13 Frontend Browser Use

av edited this page Sep 27, 2025 · 1 revision

Browser Use

Browser Use Web UI is a web interface for the Browser Use library that makes websites accessible for AI agents. It provides a user-friendly interface to control and interact with AI agents that can navigate and interact with web pages.

Configuration

Environment Variables

  • HARBOR_BROWSERUSE_HOST_PORT - Port to expose the web interface on (default: 34501)
  • HARBOR_BROWSERUSE_IMAGE - Docker image to use (default: browseruse/web-ui)
  • HARBOR_BROWSERUSE_VERSION - Image version to use (default: latest)
  • HARBOR_BROWSERUSE_OPEN_URL - URL to open when using harbor open browseruse
  • HARBOR_BROWSERUSE_API_KEY - Optional API key for authentication
  • HARBOR_BROWSERUSE_ANTHROPIC_API_KEY - Anthropic API key for Claude integration

Volumes

  • ./browseruse/data - Persistent data storage for sessions and configurations
  • ./browseruse/logs - Application logs

Usage

Starting the Service

harbor up browseruse

Accessing the Service

harbor open browseruse
harbor url browseruse

The web interface will be available at http://localhost:34501 by default.

Configuration

The service can be configured through environment variables in the ./browseruse/override.env file or by setting the corresponding HARBOR_BROWSERUSE_* variables in your profile.

Integration

Browser Use can integrate with various AI backends available in Harbor:

  • Claude (Anthropic) - Configure with HARBOR_BROWSERUSE_ANTHROPIC_API_KEY
  • OpenAI-compatible APIs - Can be configured to work with local LLM backends
  • Other AI providers supported by the Browser Use library

Troubleshooting

Service Won't Start

  1. Check if the port is available:

    harbor logs browseruse
  2. Verify environment variables are properly set:

    harbor env browseruse

Can't Access Web Interface

  1. Ensure the service is running:

    harbor ps
  2. Check if the port is correctly mapped:

    harbor url browseruse

AI Agent Issues

  1. Verify API keys are properly configured
  2. Check that the target AI backend is accessible
  3. Review logs for authentication or connection errors

Additional Resources

Clone this wiki locally