What problem does it solve? After deploying an agent, teams still need to register it with Gemini Enterprise or the Agent Registry so it can be discovered and invoked, and doing this manually involves choosing the right registration mode, wiring flags, and debugging IAM or SDK issues. ## Core Features & Use Cases - ADK and A2A registration modes: Register ADK agents on Agent Runtime natively via :streamQuery, or register any framework's agent over A2A using its agent card URL on Cloud Run or GKE. - Programmatic and interactive usage: Run non-interactively in CI/CD with flags or environment variables, or use --interactive for guided prompts with auto-detection from deployment_metadata.json. - Agent Registry fleet management: List, update, and delete registered agents and register external MCP servers with gcloud agent-registry commands. - Use Case: You deployed an ADK agent to Agent Runtime and want it visible in your Gemini Enterprise app; run agents-cli publish gemini-enterprise with just the app ID and let auto-detection handle the rest. ## Quick Start Ask the assistant to publish your deployed ADK agent to Gemini Enterprise using agents-cli with your Gemini Enterprise app ID.
