Recipe Registry CLI
The recipe registry allows you to publish, pull, and manage recipes in a centralized location.Quick Start
Commands
publish
Publish a recipe bundle or directory to the registry.| Option | Description |
|---|---|
--registry <path-or-url> | Registry path or URL (default: ~/.praison/registry) |
--token <token> | Authentication token for remote registry |
--force | Overwrite existing version |
--json | Output JSON format |
pull
Pull a recipe from the registry.| Option | Description |
|---|---|
--registry <path-or-url> | Registry path or URL |
--token <token> | Authentication token |
-o, --output <dir> | Output directory (default: current) |
--json | Output JSON format |
Registry Types
Local Registry
The default registry is stored at~/.praison/registry. No configuration required.
Custom Local Registry
Specify a custom path for the registry:Remote Registry (Future)
Remote HTTP registries will be supported with token authentication:Registry Structure
Environment Variables
| Variable | Description |
|---|---|
PRAISONAI_REGISTRY_TOKEN | Default authentication token |
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Validation error (invalid bundle) |
| 7 | Recipe not found |
Python API
Next Steps
- Run History - Store and export run history
- Security Features - SBOM, signing, auditing
- Policy Packs - Manage tool permissions

