Legacy reference: this page describes OCX 2 for OpenCode V1. For OCX 3 and OpenCode V2, see the V2 documentation.
Usage
Description
Manage configured component registries. Registries are sources for components that OCX can install. By default, registry commands operate on local project configuration; use--global for global scope.
Subcommands
ocx registry add— Add a registryocx registry remove— Remove a registryocx registry list— List configured registries
Registry Add
Add a new registry to your configuration.Usage
Arguments
Flags
Examples
Identity Model
- Registry name is canonical identity: The
--nameyou provide becomes the canonical identifier for the registry in your configuration. - Components referenced as
name/component: Users reference components using the configured registry name (e.g.,kdco/researcher). - Registry
index.namespacenot authoritative: Thenamespacefield in the registry’sindex.jsonis informational only.
Constraints
- URL uniqueness: The same URL cannot be added under multiple names. To change the name, remove it first with
ocx registry remove <name>, then add with the new name. - No
--forcefor conflicts: Use remove-then-add to update an existing registry name or URL.
Errors
--global and --cwd are mutually exclusive.Registry Remove
Remove a registry from your configuration.Usage
Arguments
Flags
Examples
Errors
Registry List
List all configured registries.Usage
Flags
Examples
Output
See Also
- ocx add — Install components from registries.
- ocx init — Initialize configuration before adding registries.
- Enterprise Overview — Registry locking for teams.