Push your agent to a registry and share it by name. Your teammates
reference agentcatalog/security-expert instead of copying YAML files
around or asking you where your agent configuration lives.
When you update the agent in the registry, everyone gets the new version the next time they pull or restart their client.
Prerequisites
To push agents to a registry, authenticate first:
For other registries, use their authentication method.
Publishing agents
Push your agent configuration to a registry:
Push creates the repository if it doesn't exist yet. Use Docker Hub or any OCI-compatible registry.
Tag specific versions:
Using published agents
Pull an agent to inspect it locally:
This saves the configuration as a local YAML file.
Run agents directly from the registry:
Or reference it directly in integrations:
Editor integration (ACP)
Use registry references in ACP configurations so your editor always uses the latest version:
MCP client integration
Agents can be exposed as tools in MCP clients:
What's next
- Set up ACP integration with shared agents
- Configure MCP integration with shared agents
- Browse the agent catalog for examples
