Local Docker Deployment

When you select Local Docker in the TUI target picker, the TUI builds the Docker image, starts both admin and runtime containers via docker compose, and connects automatically. The container lifecycle is tied to the TUI process – both containers stop when you exit.

How It Works

1. Launch the TUI with ./scripts/run-tui.sh (see Quickstart)
2. Select “Local Docker” from the target picker
3. The TUI builds the image and starts both containers via docker compose up -d
4. Once the admin health check passes, you land in the TUI dashboard

The TUI handles the full build-deploy-healthcheck cycle and streams build output in real time.

What Gets Built

The Dockerfile uses a two-stage build:

Bundled Tools

The image includes everything the agent needs to operate:

• GitHub Copilot CLI (@github/copilot) – the agent engine
• GitHub CLI (gh) – authentication
• Azure CLI (az) – infrastructure provisioning and bot registration
• Cloudflare tunnel (cloudflared) – automatic public endpoint for webhooks
• Playwright MCP + Chromium – headless browser for web-based skills
• Python runtime – the Polyclaw server, agent, and all backend services
• React dashboard – embedded frontend static assets

Ports

Persistent Data

The TUI creates two Docker named volumes that persist across restarts:

Because these are named Docker volumes, your data survives even when the containers are stopped and recreated on the next TUI launch.

Container Entrypoint

Each container runs the same entrypoint script, which branches on POLYCLAW_MODE:

1. Sets HOME based on container mode: /admin-home (admin container) or /runtime-home (runtime container)
2. Cleans stale Copilot CLI runtime cache (keeps only the matching version)
3. Loads environment variables from the shared persisted .env file
4. Resolves any @kv: Key Vault secret references (if configured)
5. Authenticates the runtime container’s Azure identity (service principal or managed identity)
6. Starts the server: polyclaw-admin --admin-only (admin) or polyclaw-admin --runtime-only (runtime)

What Happens on Exit

When you exit the TUI (Ctrl+C or /quit), both containers are stopped via docker compose down. The named volumes are preserved, so the next launch picks up where you left off – same configuration, same auth state, same data.

Integrations Deployed Automatically

These services start automatically inside the container without any manual configuration:

All other integrations (voice, Key Vault, sandbox, additional MCP servers) are optional and configured through the Setup Wizard or the Web Dashboard after deployment.