Install a plugin from a URL - ADOS Documentation

URL install lets the agent download a published .adosplug itself, then run the same install flow as a local file: archive parse, signature verification, manifest validation, board check and permission gating. Only the transport differs.

How it works

The agent’s POST /api/plugins/install_from_url endpoint takes the URL and downloads the archive directly. Two callers use it:

Mission Control. Clicking Install on a catalog card in a node’s Extensions tab sends the catalog’s archive URL plus its sha256 pin; the agent fetches the archive itself. There is no paste-a-link field in Mission Control.
The agent CLI. ados plugin install <https-url> previews the archive through POST /api/plugins/parse_from_url, then installs pinned to the sha256 of the bytes you reviewed. Use this to install any allowlisted URL.

ados plugin install https://github.com/acme/acme-extensions/releases/download/my-plugin-v1.0.0/com.example.my-plugin-1.0.0.signed.adosplug

Rules the agent enforces

Rule	Detail
HTTPS only	Plain `http://` is rejected.
Host allowlist	GitHub release hosts (`github.com`, `objects.githubusercontent.com`, `release-assets.githubusercontent.com`) and the cloud relay’s archive hosts. S3 buckets, `localhost` and IP addresses are rejected. Matching is on a label boundary, and each redirect hop (up to five) is re-checked.
Download size	Capped at the 50 MB archive limit; the download aborts one byte past it.
Hash pin	When the caller supplies a SHA-256, the streamed bytes must match or the install aborts.
Catalog installs	An install marked as from the catalog must carry a sha256 that matches a bundled catalog entry, or it fails with `sha256_required` or `catalog_mismatch`.
Timeout	30 minutes end to end.

A URL whose host is not on the allowlist is rejected before any bytes are downloaded.

Self-hosted release hosts

Self-hosted release hosts are not supported: the allowlist is compiled into the agent. Publish on a GitHub release, or copy the file to the node and use local install.

Integrity is identical to local install

Once the bytes are on disk, URL and local install are the same flow. A signer the agent does not trust fails the install however the archive arrived. The transport adds the host allowlist, the size cap and the hash pin on top. Signing is on Signing keys.

Next steps

Catalog and registry

Browse, auto-update and the registry API.

Local install

Install from a file.

Last modified on October 11, 2026