Iii Engine Config

This is your infrastructure-as-code for the iii engine runtime. You're editing iii-config.yaml to wire up workers (HTTP, queue, state, cron, streams), swap storage adapters between file-based dev setups and Redis/RabbitMQ for production, and configure ports, RBAC listeners, and queue retry behavior. It covers the full surface: which workers to enable, how they connect (typically WebSocket on 49134), environment variable expansion with defaults, and the lockfile workflow for reproducible managed worker installs. Reach for this when you're deploying an engine, tuning concurrency and backoff per queue, or setting up observability and security policies. The examples lean heavily on adapter swapping and real port numbers, which is helpful if you're moving from local dev to a real deployment.

skills.sh installs: 4.9K
GitHub stars: 18.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add iii-hq/iii --skill iii-engine-config --agent claude-code

Installs into .claude/skills of the current project.

Files

Engine Config

iii has two engine configuration modes. Do not mix them.

Managed Compose engine

The presence of engine: means that Compose owns the engine process. Engine worker values are direct mappings; there is no nested config: field.

namespace: orders
engine:
  url: ws://127.0.0.1:49134
  registration_namespace_grace_ms: 5000
  workers:
    configuration:
      adapter:
        name: fs
        config:
          directory: ./config
    iii-worker-manager:
      host: 127.0.0.1
      port: 49134
    iii-http-functions: {}
    iii-stream:
      host: 127.0.0.1
      port: 3112
  sandbox:
    adapter: sandbox-libkrun
containers: {}

Start it with:

iii compose --namespace orders-daemon --up --file worker-compose.yaml

SKILL.md on GitHub

Details

Repository: github.com/iii-hq/iii
Category: Backend & APIs
First seen: Jun 3, 2026