Docker

The official Clisbot Docker image runs the daemon and serves the bundled browser UI from the same HTTP origin. It is meant for servers, dev boxes, NAS devices, homelab hosts, and other places where you want Clisbot running without the desktop app.

Docker images follow the stable Clisbot release cadence. ghcr.io/longbkit/clisbot:latest points at the latest stable release, not an arbitrary main build.

docker run -d --name clisbot \
  -p 6868:6868 \
  -e CLISBOT_PASSWORD=change-me \
  -v "$PWD/clisbot-home:/home/clisbot" \
  -v "$PWD:/workspace" \
  ghcr.io/longbkit/clisbot:latest

Then open:

http://localhost:6868

If you set CLISBOT_PASSWORD, use that same password when adding the direct daemon connection in the web UI, mobile app, or CLI.

What the image includes

The image:

installs the Clisbot daemon, CLI, Hub and channel packages
serves the bundled web UI
listens on 0.0.0.0:6868 inside the container
stores daemon state under /home/clisbot/.clisbot
runs the daemon and launched agents as the non-root clisbot user

The image does not bundle agent CLIs such as Claude Code, Codex, OpenCode, Copilot, or Pi. Add the agents you use with a small child image.

Host-side CLI commands select the container explicitly, for example clisbot project ls --host 127.0.0.1:6868. Without an endpoint selector the CLI looks for a local home’s supervisor. Container environment settings are deployment overrides; worker restart preserves them. Your container manager owns full supervisor replacement.

Service modes

One image supports three values of CLISBOT_RUN_MODE:

Mode	Services	Default ports
`daemon` (default)	Daemon and the shared web UI	`6868`
`hub`	Hub backend only	`6870`
`all`	Daemon, shared web UI and Hub backend	`6868`, `6870`

To run everything together, generate a credential encryption key once, store it with your deployment secrets, and reuse it across restarts:

export CLISBOT_HUB_CREDENTIAL_MASTER_KEY="$(openssl rand -base64 32)"
docker run -d --name clisbot --stop-timeout 40 \
  -e CLISBOT_RUN_MODE=all \
  -e CLISBOT_HUB_CREDENTIAL_MASTER_KEY \
  -e CLISBOT_PASSWORD=change-me \
  -p 6868:6868 \
  -v "$PWD/clisbot-home:/home/clisbot" \
  -v "$PWD:/workspace" \
  ghcr.io/longbkit/clisbot:latest

Open http://localhost:6868. Hub management is integrated into the Clisbot app; 6870 has no separate dashboard. In all mode the app forwards Hub APIs to the backend, so publishing 6870 is optional. Starting both services does not automatically enroll the daemon into Hub; use the app's Hub connection flow.

For a public deployment, set CLISBOT_HUB_APP_URL to the shared HTTPS app origin and configure the reverse proxy below. With a separate Hub container, set the daemon's CLISBOT_HUB_PROXY_URL to its reachable backend origin. Without that setting, daemon mode does not enable the Hub proxy.

Persist /home/clisbot in every mode. Hub uses .clisbot-hub under that directory for embedded storage; DATABASE_URL selects PostgreSQL. Healthchecks cover all selected services. In all mode, a service failure stops the container; allow 40 seconds for graceful shutdown.

Docker Compose

services:
  clisbot:
    image: ghcr.io/longbkit/clisbot:latest
    container_name: clisbot
    restart: unless-stopped
    ports:
      - "6868:6868"
    environment:
      CLISBOT_PASSWORD: "change-me"
      # CLISBOT_HOSTNAMES: "clisbot.example.com,.lan"
    volumes:
      - ./clisbot-home:/home/clisbot
      - ./workspace:/workspace

Start it:

docker compose up -d

Install agent CLIs

Create a child image for the providers you want available:

FROM ghcr.io/longbkit/clisbot:latest

USER root
RUN npm install -g @openai/codex @anthropic-ai/claude-code opencode-ai

Build it:

docker build -t clisbot-with-agents .

Then use image: clisbot-with-agents in Compose.

Leave the child image user as root. The base entrypoint uses root only for first-run mounted-volume setup, then drops the daemon and launched agents to the non-root clisbot user.

You can authenticate agents either by passing provider environment variables or by running the provider login flow inside the container:

docker exec -it --user clisbot clisbot codex
docker exec -it --user clisbot clisbot claude

Agent credentials persist in /home/clisbot.

Volumes

Mount two paths for most deployments:

Mount	Purpose
`/home/clisbot`	Clisbot state plus agent config and credentials such as `.codex`, `.claude`
`/workspace`	Code that Clisbot and launched agents can read and write

On Linux, the built-in clisbot user is uid/gid 1000:1000. Make mounted directories writable by that user, or run the container with Docker's --user / Compose user: option.

Reverse proxy

Forward normal HTTP traffic and WebSocket upgrades to the container.

Caddy:

clisbot.example.com {
  reverse_proxy 127.0.0.1:6868
}

Nginx:

server {
    listen 443 ssl;
    server_name clisbot.example.com;

    location / {
        proxy_pass http://127.0.0.1:6868;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

If you reach Clisbot by DNS name, allow that host:

environment:
  CLISBOT_HOSTNAMES: "clisbot.example.com,.lan"

IPs and localhost are allowed by default.

Security

Set CLISBOT_PASSWORD for any published port or network-reachable deployment. Use HTTPS at your reverse proxy for browser access outside localhost.

The static web UI is public on the daemon origin. The daemon API and WebSocket are protected by password auth when configured.

Agents can access whatever you mount into /workspace and whatever credentials you place in /home/clisbot. Keep those mounts scoped to what the agents should be able to use.

See Security for the full daemon trust model.

Troubleshooting

The UI loads but cannot connect: if CLISBOT_PASSWORD is set, add a direct connection with the same password.
403 Host not allowed: set CLISBOT_HOSTNAMES to the DNS names you use.
Provider not available: install that agent CLI in a child image or make sure the binary is on PATH.
Permission errors in /workspace: make the mounted directory writable by uid/gid 1000:1000, or run the container as the host uid/gid.
Logs: run docker logs clisbot, or inspect /home/clisbot/.clisbot/daemon.log inside the container.

#Docker

#What the image includes

#Service modes

#Docker Compose

#Install agent CLIs

#Volumes

#Reverse proxy

#Security

#Troubleshooting