Bug: Bytebot UI fails to start - Missing proxy target configuration

[horstenegger]

Bug Description

Bytebot UI container fails to start with the error: [HPM] Missing "target" option. This appear>

Environment

• Docker Image: ghcr.io/bytebot-ai/bytebot-ui:edge
• Deployment Method: Docker Compose
• Host OS: Debian Linux
• Network: Tailscale VPN (private network)

Steps to Reproduce

1. Use the following docker-compose.yml configuration:

bytebot-ui:
  image: ghcr.io/bytebot-ai/bytebot-ui:edge
  container_name: bytebot-ui
  restart: unless-stopped
  ports:
    - "9992:9992"
  environment:
    - API_BASE_URL=http://bytebot-agent:9991
    - PORT=9992
    - AGENT_URL=http://bytebot-agent:9991
    - BACKEND_URL=http://bytebot-agent:9991
    - PROXY_URL=http://bytebot-agent:9991
  networks:
    - bytebot_network
  depends_on:
    - bytebot-agent

2. Run: docker compose up -d
3. Check logs: docker logs bytebot-ui

Error Message

> bytebot-ui@0.1.0 start
> npm run build --prefix ../shared && tsx server.ts

> @bytebot/shared@0.0.1 build
> tsc -p tsconfig.json
Server failed to start: Error: [HPM] Missing "target" option. Example: {target: "http://www.exam>
    at <unknown> (server.ts:33:45)

What I Tried

• ✅ Added various proxy-related environment variables (PROXY_TARGET, HTTP_PROXY_TARGET)
• ✅ Provided API keys via .env file
• ✅ Tried different network configurations (bridge, host)
• ✅ Verified bytebot-agent service is running and accessible
• ✅ Attempted multiple restarts and rebuilds

Expected Behavior

Bytebot UI should start successfully and be accessible on port 9992.

Current Behavior

Container fails to start immediately due to missing proxy target configuration.

Additional Context

• The bytebot-agent service runs without issues
• Other services (n8n, Skyvern) work fine in the same environment