MCP ExplorerExplorer

Drox Dynamics

@DroxDynamicson a year ago
2 MIT
FreeCommunity
AI Systems
#agent#agent-framework#assistant#chatgpt#chatgpt-app#chatgpt-operator#claude#computer-use#gca#gpt#gpt-4o#langchain#llms#mcp#model-context-protocol#openai
Meet Drox Dynamics, the AI-powered browser that takes care of tasks for you. No more endless clicks, tell it what you need, and it gets it done.

Overview

What is Drox Dynamics

Drox-Dynamics is an AI-powered browser designed to automate tasks for users. It simplifies web interactions by allowing users to specify their needs, eliminating the need for repetitive clicking.

Use cases

Use cases for Drox-Dynamics include automating data entry on websites, conducting research by gathering information from multiple sources, and managing online accounts without the hassle of repeated logins.

How to use

To use Drox-Dynamics, clone the repository from GitHub, set up a Python environment, and follow the quickstart guide. The user interface is built on Gradio, making it easy to interact with the browser agent.

Key features

Key features of Drox-Dynamics include expanded support for various Large Language Models (LLMs), custom browser support for seamless authentication, persistent browser sessions for maintaining context, and a user-friendly interface for browser-related functionalities.

Where to use

Drox-Dynamics can be used in various fields such as web development, automated testing, customer support, and any domain requiring efficient web interaction and task automation.

Content

Drox Dynamics

Discord
Documentation
WebHiveOS

This project builds upon the foundation of the Drox Dynamics, which is designed to make websites accessible for AI agents.

We sincerely appreciate Simon Walker valuable contribution to this project.

Drox Dynamics UI: It is built on Gradio and supports most browser-related functionalities. This user-friendly UI facilitates seamless interaction with the browser agent.

Expanded LLM Support: We’ve integrated support for various Large Language Models (LLMs), including Google, OpenAI, Azure OpenAI, Anthropic, DeepSeek, and Ollama. Additionally, we plan to expand support for even more models.

Custom Browser Support: With our tool, you can use your own browser, eliminating the need to re-login to websites or handle authentication issues. Additionally, this feature supports high-definition screen recording.

Persistent Browser Sessions: You have the option to keep the browser window open between AI tasks, enabling you to view the full history and state of AI interactions.

Installation Guide

Prerequisites

  • Python 3.11 or higher
  • Git (for cloning the repository)

Option 1: Local Installation

Read the quickstart guide or follow the steps below to get started.

Step 1: Clone the Repository

git clone https://github.com/IgorKhrupin/Drox-Dynamics.git
cd Drox-Dynamics

Step 2: Set Up Python Environment

We recommend using uv for managing the Python environment.

Using uv (recommended):

uv venv --python 3.11

Activate the virtual environment:

  • Windows (Command Prompt):
.venv\Scripts\activate
  • Windows (PowerShell):
.\.venv\Scripts\Activate.ps1
  • macOS/Linux:
source .venv/bin/activate

Step 3: Install Dependencies

Install Python packages:

uv pip install -r requirements.txt

Install Playwright:

playwright install

Step 4: Configure Environment

  1. Create a copy of the example environment file:
  • Windows (Command Prompt):
copy .env.example .env
  • macOS/Linux/Windows (PowerShell):
cp .env.example .env
  1. Open .env in your preferred text editor and add your API keys and other settings

Option 2: Docker Installation

Prerequisites

Installation Steps

  1. Clone the repository:
git clone https://github.com/IgorKhrupin/Drox-Dynamics.git
cd Drox-Dynamics
  1. Create and configure environment file:
  • Windows (Command Prompt):
copy .env.example .env
  • macOS/Linux/Windows (PowerShell):
cp .env.example .env

Edit .env with your preferred text editor and add your API keys

  1. Run with Docker:
# Build and start the container with default settings (browser closes after AI tasks)
docker compose up --build
# Or run with persistent browser (browser stays open between AI tasks)
CHROME_PERSISTENT_SESSION=true docker compose up --build
  1. Access the Application:

Usage

Local Setup

  1. Start the Drox Dynamics UI:
    Once the installation steps are complete, launch the application using the following command:
    python droxdx.py --ip 127.0.0.1 --port 7788
    
  2. UI options:
    • --ip: Specifies the IP address to bind the UI to. Default is 127.0.0.1.
    • --port: Defines the port to bind the UI to. Default is 7788.
    • --theme: Sets the theme for the user interface. Default is Ocean.
      • Default: A balanced design with a standard layout.
      • Soft: A muted, gentle color scheme for a soothing viewing experience.
      • Monochrome: A grayscale theme with minimal color for clarity and focus.
      • Glass: A modern, semi-transparent design for a sleek appearance.
      • Origin: A retro-inspired theme for a nostalgic touch.
      • Citrus: A lively, citrus-toned palette featuring bright and fresh colors.
      • Ocean (default): A calming, ocean-themed interface for a tranquil effect.
    • --dark-mode: Activates dark mode for the user interface.
  3. Access the UI: Open your web browser and go to http://127.0.0.1:7788.
  4. Using Your Own Browser (Optional):
    • Set CHROME_PATH to the executable path of your browser and CHROME_USER_DATA to the user data directory of your browser. Leave CHROME_USER_DATA empty to use local user data.
      • Windows
         CHROME_PATH="C:\Program Files\Google\Chrome\Application\chrome.exe"
         CHROME_USER_DATA="C:\Users\YourUsername\AppData\Local\Google\Chrome\User Data"
        

        Note: Replace YourUsername with your actual Windows username.

      • Mac
         CHROME_PATH="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
         CHROME_USER_DATA="/Users/YourUsername/Library/Application Support/Google/Chrome"
        
    • Close all Chrome windows.
    • Open the UI in a non-Chrome browser, such as Firefox or Edge. This is necessary since the persistent browser context will use Chrome data while running the agent.
    • Enable the “Use Own Browser” option in the Browser Settings.
  5. Keep Browser Open (Optional):
    • Set CHROME_PERSISTENT_SESSION=true in the .env file.

Docker Setup

  1. Environment Variables:

    • All configuration is managed through the .env file.
    • Available environment variables:
      # LLM API Keys
      OPENAI_API_KEY=your_key_here
      ANTHROPIC_API_KEY=your_key_here
      GOOGLE_API_KEY=your_key_here
      
      # Browser Settings
      CHROME_PERSISTENT_SESSION=true   # Set to true to keep the browser open between AI tasks
      RESOLUTION=1920x1080x24         # Custom resolution format: WIDTHxHEIGHTxDEPTH
      RESOLUTION_WIDTH=1920           # Custom width in pixels
      RESOLUTION_HEIGHT=1080          # Custom height in pixels
      
      # VNC Settings
      VNC_PASSWORD=your_vnc_password  # Optional, defaults to "vncpassword"
      
  2. Platform Support:

    • Supports both AMD64 and ARM64 architectures.
    • For ARM64 systems (e.g., Apple Silicon Macs), the container will automatically use the appropriate image.
  3. Browser Persistence Modes:

    • Default Mode (CHROME_PERSISTENT_SESSION=false):

      • Browser opens and closes with each AI task.
      • Provides a clean state for each interaction.
      • Uses fewer system resources.
    • Persistent Mode (CHROME_PERSISTENT_SESSION=true):

      • Keeps the browser open between AI tasks.
      • Retains history and state.
      • Enables viewing previous AI interactions.
      • Can be set in the .env file or as an environment variable when starting the container.
  4. Viewing Browser Interactions:

    • Open the noVNC viewer at http://localhost:6080/vnc.html.
    • Enter the VNC password (default: “vncpassword” or the value set in VNC_PASSWORD).
    • Direct VNC access is available on port 5900 (mapped to container port 5901).
    • This allows you to monitor all browser interactions in real-time.
  5. Container Management:

    # Start with persistent browser
    CHROME_PERSISTENT_SESSION=true docker compose up -d
    
    # Start with default mode (browser closes after tasks)
    docker compose up -d
    
    # View logs
    docker compose logs -f
    
    # Stop the container
    docker compose down
    

Tools

No tools

Comments

Recommend MCP Servers

View All MCP Servers