What problem does it solve? Working with a self-hosted Gitea container registry involves specific authentication rules, naming conventions, and API endpoints that differ from Docker Hub, and mistakes like using account passwords with 2FA or malformed delete requests waste debugging time. ## Core Features & Use Cases - Push and Pull OCI Artifacts: Push and pull Docker images, Helm charts, and any OCI artifact using the Docker Registry v2 API with correct {registry}/{owner}/{image}:{tag} naming. - Multi-Architecture Builds: Build and publish multi-arch images for linux/amd64 and linux/arm64 using docker buildx. - Package Management via API: List and delete packages through the Gitea REST API across 20+ supported package types including npm, maven, helm, and terraform. - Use Case: You need to publish a multi-arch image of your backend service to your organization's Gitea instance and later clean up old versions via the API. ## Quick Start Ask the agent to push a multi-arch build of your local Docker image to your Gitea registry and list the published package versions.