registry command lists recipes and manages the local recipe registry server.
An agent selects a recipe from the same local registry the CLI enumerates:
Quick Start
1
List recipes
List every recipe in the local registry (An empty registry prints
~/.praison/registry):No recipes found in registry: <path> and still exits 0.2
Check server status
Confirm a running registry server is healthy:
Commands
list
List recipes in the local recipe registry.
Examples:
rich is a soft dependency. With rich installed, list renders a table (Name, Version, Description, Tags). Without it, output degrades to one line per recipe: {name} ({version}): {description}.serve
Start a local HTTP registry server.
Examples:
Both the deprecated and canonical forms default to port 7777. Scripts that omit
--port on praisonai registry serve now bind to 7777 (previously 8080) — the two forms land on the same port. The deprecation warning goes to stderr, so scripts capturing only stdout will not see it unless they redirect 2>&1.status
Check the health of a running registry server.
Examples:
Exit Codes
See Also
Recipe Registry CLI
Publish, pull, and list recipes from local or remote registries
Recipe Registry Server
Deploy the canonical
praisonai serve registry HTTP serverRecipe Registry API
HTTP API endpoints exposed by the registry server
Recipe Registry (Python)
Publish and pull recipes from the Agent’s perspective

