How to

Connect an instance to the registry

An Agent Orchestrator instance pulls this registry's signed list, verifies the signature with the public key you configure, and shows the artifacts in the AO Hub. Nothing is installed without a workspace administrator's confirmation.

1. Set the instance environment
Add these lines to the backend's environment (for example infra/.env) and restart the backend.
```
AO_REGISTRY_ENABLED=true
AO_REGISTRY_URL=https://<address of this registry>
AO_REGISTRY_CHANNEL=stable
AO_REGISTRY_TRUSTED_KEYS=prod-registry-1=ZjE4DSssQ73LslRfzYplZNFn3H4oNj8ox4Y7GT71TbI=
```
The key is the public half of the signing key. Compare it with a source you trust — anyone may know it; it can only verify, not sign.
2. Switch the registry on in the product
Enterprise edition: in the global settings, tick AO Registry under feature flags (the registry flag). It is off by default. The synchronisation from step 1 runs in every edition; the registry tabs in the AO Hub currently exist only in the Enterprise edition.
3. Install in the AO Hub
The AO Hub shows the Agents, Skills and Bundles tabs. A workspace administrator picks an artifact and confirms the installation. Installed agents start disabled and without a runtime.

How trust works

Every version is immutable and signed with an Ed25519 key; every artifact's checksum is in the signed list.
The instance refuses a list older than the last one it saw, and any list signed by an unknown key.
An artifact's trust level is written in the artifact and checked when it is merged. It is not a certification.

Release 2026.10.26-2 · sequence 2 · channel stable · signed with prod-registry-1 · 2026-10-26

Connect an instance to the registry

1. Set the instance environment

2. Switch the registry on in the product

3. Install in the AO Hub

How trust works