`agentrig registry`

Manage the registries in your config file.

The official registry is seeded by agentrig init. For AgentRig registry refs, the CLI resolves an InstallBundle from agentrig.ai. Third-party static signed registries are explicit: add the registry first, then install plugins from it with <registryAlias>/<namespace.plugin>. Add @<version> only when you need an exact reproducibility or rollback pin.

List registries

agentrig registry list

Add or update a registry

agentrig registry add georg https://georg.dev/agentrig

After adding a registry:

agentrig search typescript --registry georg
agentrig plugin install codex georg/georg.ts-master-plugin

Registry aliases are for static signed registries only. Direct URLs, local files, ZIP uploads, and author repos are outside the public install contract.

Unversioned refs resolve to the latest installable version returned by the official or third-party registry. The install ledger records the concrete resolved version and snapshot digest, so uninstall and repair stay deterministic.

agentrig inspect <repo> and agentrig use <repo> are separate external-repo workflows. They can scan and reuse selected files, but they must not be added as registry aliases and must not be described as public registry installs.

AI does not change this boundary. CLI enrichment is local BYOK only, and web-hosted enrichment produces draft fields that require admin acceptance before they can enter a submitted manifest.

QA and staging registries

Manual smoke tests that install fixture artifacts must use a non-production registry alias such as agentrig-staging or agentrig-dev:

agentrig registry add agentrig-staging https://raw.githubusercontent.com/agentrig/agentrig-registry-staging/main
agentrig search test --registry agentrig-staging
agentrig plugin install codex agentrig-staging/regenrek.test-submission

Never publish or install regenrek.test-*, test-*, or qa-* fixtures through the production agentrig registry alias. Production examples should keep using real latest-first refs such as agentrig/agentrig.core-committer.

Options

--cwd <path> - working directory.
--global - write to global config.

Notes

Registry aliases use lowercase letters, numbers, and hyphens.
Third-party registry URLs must point at a base URL that serves registry.json at the root.
Use --global when you want a registry available across repos instead of only in the current project.

registry