Using Iii

<!-- generated by iii-skill-render. DO NOT EDIT (changes here are overwritten on the next render). Edit docs/0-17-0/using-iii/workers-registry.mdx. -->

# Worker Registry


## 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.

{/* TODO: Add a llm-only note here on how an llm can browse the registry once that surface is stable in the skills worker */}

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

## Adding a worker

`iii worker add` accepts three sources. In every case the worker is added to your project's
`config.yaml` and started automatically.

```bash
iii worker add iii-state                # registry name
iii worker add ./workers/my-worker      # local path
iii worker add ghcr.io/org/worker:tag   # Docker or OCI image
```

<Note>
  Registry workers are published with semver versions. For how versions are picked, pinned with
  `@<version>`, updated, and recorded in `iii.lock`, see [Versioning and
  pinning](./workers#versioning-and-pinning) and [Updating a
  worker](./workers#updating-a-worker) on the Workers page.
</Note>

<Note>
  For removing workers and the broader `iii worker` subcommand set (start, stop, restart, sync,
  verify, etc.), see [Workers](./workers).
</Note>

## Artifact types

Each registry worker is published as either a native binary (with per-platform artifacts for macOS,
Linux, and Windows) or as a Docker / OCI compatible image that runs on every supported platform.