> ## Documentation Index
> Fetch the complete documentation index at: https://iii.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Worker Registry

> A central repository of iii workers.

## Browsing the registry

The iii Worker Registry at [workers.iii.dev](https://workers.iii.dev/) is the index of installable
workers. Each worker page lists the functions and trigger types it provides, its configuration
schema, supported platforms, and agent skills. Use that information to locate a worker that fulfills
a capability your project needs.

Workers can also be found on Docker and OCI-compatible registries.

## Adding a worker

`compose::add` accepts a registry name (optionally pinned with `@version`) or a local project path.
It writes the resolved worker and dependency graph to `worker-compose.yaml`, then restarts the
project. Its settings are managed through the [configuration worker](./configuration).

```bash theme={"theme":{"light":"catppuccin-latte","dark":"dark-plus"}}
iii trigger -n dev compose::add worker=state
iii trigger -n dev compose::add worker=state@0.22.2
iii trigger -n dev compose::add worker=./workers/my_worker
```

<Note>
  Replace `dev` with the running Compose daemon's namespace. For project lifecycle, status, updates,
  and removal by editing the file, see [Workers](./workers) and [Compose](./compose).
</Note>

## Artifact types

Compose currently runs registry workers published as native binaries or bundles. Engine-kind roots
are rejected because the engine already supplies them; image workers require an OCI runtime and are
not yet supported by Compose.