comisai/comis repository overview

⁠Comis

Comis is an open-source security-first runtime for AI agents that learn and act across sessions.

This image runs the Comis daemon, gateway, agents, scheduler, memory, and messaging adapters in one container. Learned guidance can influence what an agent proposes, but it cannot grant permission. Capabilities, credential scope, tool policy, and configured limits remain in the runtime.

• Source: https://github.com/comisai/comis⁠
• Docs: https://docs.comis.ai⁠
• License: Apache-2.0

⁠Supported architectures

linux/amd64 · linux/arm64

⁠Variants

⁠Tag strategy

Every release pushes the following tags automatically:

For repeatable deployments, replace the moving latest tag with an immutable release tag such as comisai/comis:X.Y.Z-slim.

⁠Quick start

docker pull comisai/comis:latest-slim

docker run -d \
  --name comis \
  --restart unless-stopped \
  -p 127.0.0.1:4766:4766 \
  -v comis-data:/home/comis/.comis \
  -e ANTHROPIC_API_KEY="$ANTHROPIC_API_KEY" \
  comisai/comis:latest-slim

The --restart unless-stopped policy lets Docker relaunch the daemon after gateway.restart or a configuration write triggers a graceful restart. Secret writes through env_set are live-applied and do not trigger a restart.

Verify:

curl http://127.0.0.1:4766/health

This example is for initial evaluation. Pin an immutable release tag, configure gateway authentication, and review the threat model⁠ before exposing the service beyond localhost.

⁠Docker Compose

services:
  comis-daemon:
    image: comisai/comis:latest-slim
    init: true
    restart: unless-stopped
    ports:
      - "127.0.0.1:4766:4766"
    volumes:
      - comis-data:/home/comis/.comis
    environment:
      - ANTHROPIC_API_KEY=${ANTHROPIC_API_KEY}
      - OPENAI_API_KEY=${OPENAI_API_KEY:-}
      - TELEGRAM_BOT_TOKEN=${TELEGRAM_BOT_TOKEN:-}
      - DISCORD_BOT_TOKEN=${DISCORD_BOT_TOKEN:-}
      - SLACK_BOT_TOKEN=${SLACK_BOT_TOKEN:-}
      - COMIS_GATEWAY_HOST=0.0.0.0
      - COMIS_GATEWAY_PORT=4766

volumes:
  comis-data:

With the default encrypted storage mode, the daemon generates SECRETS_MASTER_KEY in the mounted data directory's .env on first boot. Back up that file, and do not add an empty SECRETS_MASTER_KEY entry to the container environment: it would override the generated value and prevent the encrypted store from opening.

A full docker-compose.yml (with the optional comis-web dashboard and comis-cli profiles, plus a host-bind variant) ships in the GitHub repo⁠.

⁠Configuration

⁠Ports

⁠Volumes

⁠Common environment variables

Secrets are auto-redacted in Comis logs (3 levels deep) — but never log them yourself.

⁠Browser runtime (optional)

Browser dependencies are disabled in the standard image. Build arguments enable the runtime needed by browser tools:

Build an image with the browser runtime you require:

# Headless Chrome
docker build \
  --build-arg COMIS_WITH_BROWSER=1 \
  -t comisai/comis:browser .

# Headed Chrome through Xvfb
docker build \
  --build-arg COMIS_WITH_XVFB=1 \
  -t comisai/comis:xvfb .

# Alternative Chromium distribution
docker build \
  --build-arg COMIS_WITH_CLOAKBROWSER=1 \
  -t comisai/comis:cloakbrowser .

When browser.start runs, Comis discovers the installed browser, launches it with a local CDP endpoint, and connects Playwright. Xvfb starts before the daemon when the image was built with COMIS_WITH_XVFB=1; the entrypoint verifies its local X11 socket and stops the container if the display cannot start. Xvfb runs as the container's comis user and does not use a host X server. Browser automation remains subject to each site's terms and access controls.

⁠Installer-built image (alternative path)

The repo also ships Dockerfile.install. It packs the local workspace and runs the non-interactive, non-root package-install path of install.sh inside Ubuntu 24.04. It exercises package installation and selected browser-provisioning branches, but deliberately skips interactive setup, initialization, service registration, service start, dedicated-user creation, and the public-registry download path. It is an installer validation image, not a host-parity deployment image:

docker build -f Dockerfile.install \
  --build-arg COMIS_WITH_CLOAKBROWSER=1 \
  --build-arg COMIS_WITH_XVFB=1 \
  -t comis-installed:cloak-xvfb .

The main Dockerfile is the primary multi-stage image path. Dockerfile.install exists to validate the managed-host installer in a container.

⁠Security

• Runs as non-root user comis (UID/GID 1000)
• dumb-init as PID 1 for proper signal handling
• Built-in HEALTHCHECK against /health
• Multi-stage build — Comis TypeScript source and development dependencies are removed from the runtime image
• Pino auto-redacts credentials (apiKey, token, password, secret, authorization, botToken, privateKey, cookie, webhookSecret)

⁠Companion images

• comisai/comis-web⁠ — web dashboard SPA (served by Nginx, optional)

⁠Links

• Documentation: https://docs.comis.ai⁠
• Install with Docker: https://docs.comis.ai/installation/install-docker⁠
• Docker operations guide: https://docs.comis.ai/operations/docker⁠
• Issues: https://github.com/comisai/comis/issues⁠
• Releases: https://github.com/comisai/comis/releases⁠