Managing Registry Components

Execution contract

1. Execute commands with a 60 second timeout.
2. Use machine output by default: add --output json whenever supported. Parse list results from items and pagination fields.
3. Run the leaf command's --help when any path, flag, enum, or payload shape is uncertain.
4. Supply all required inputs and confirmation flags. Do not leave an agent waiting at a prompt.
5. Reuse returned UUIDs and qualified_name values. Never automate with row numbers or ambiguous bare names.
6. Verify installs, submissions, edits, versions, ownership changes, and lifecycle transitions.
7. Submit or modify only components the user owns or is authorized to manage.
8. Never expose environment values, headers, tokens, private source data, or submitted secret fields.
9. Mutations are sent once. After an uncertain transport failure, read component state before retrying.
10. Authentication is optional for approved public content when the server setting deployment.public_registry_enabled is enabled; it is disabled by default on self-hosted deployments. Public list, show, install, and prompt render commands use https://public.observal.io by default. Authenticate before submitting, editing, reviewing, rating, or accessing private team content.

Choose the workflow

User intent	Read
Find, inspect, recommend, or install components	Discovery and installation
Submit one component or a mixed bulk file, or register a remote A2A agent	Component submission
Fork, edit, version, archive, restore, transfer, or manage co-authors	Registry lifecycle

Read only the selected reference, and read it completely before executing.

Registry rules