This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the agents-cli publish gemini-enterprise command. Also use when the user wants to "manage agents in Agent Regi

Gemini Enterprise Registration Requires: A deployed agent. For Agent Runtime, deployment metadata.json (created by agents cli deploy ) enables auto detection. For Cloud Run or GKE, provide the agent card URL and flags directly. Prerequisites 1. Agent must be deployed — the agent must be running and reachable 2. Gemini Enterprise app must exist — Create one in Google Cloud Console → Gemini Enterprise → Apps before registering 3. deployment metadata.json (Agent Runtime only) — Created automatically by agents cli deploy ; contains the agent runtime ID, deployment target, the A2A flag, and the agent directory Required Permissions for A2A on Cloud Run roles/run.servicesInvoker granted to the Discovery Engine service account ( service <PROJECT NUMBER @gcp sa discoveryengine.iam.gserviceaccount.com ) on the Cloud Run service. Registration Modes A2A Registration Every scaffolded agent serves the Agent to Agent protocol. A2A is the default — and only — registration type on Cloud Run and GKE (no reasoning engine to invoke natively). It also works on Agent Runtime via registration type a2a . For an ADK agent there the CLI warns against it, because Gemini Enterprise can invoke Agent Runtime natively via :streamQuery — prefer ADK registration in that case. For an agent built on another framework there is no ADK app to invoke natively, so A2A is the right mode on every target and the warning is expected. Pass the agent card URL and the command fetches the card and registers it; display name and description default to the card's name / description . Pass display name / description to override the card defaults. On Agent Runtime, the card URL auto builds from deployment metadata.json if you omit agent card url . ADK Registration (default on Agent Runtime) ADK projects only. The agent must be deployed to Agent Runtime as an ADK app, since registration invokes it through :streamQuery . An agent on another framework registers over A2A, so deploy it to Cloud Run or GKE and publish from there. This is the default and recommended registration for ADK agents on Agent Runtime : Gemini Enterprise invokes the agent natively via :streamQuery on its reasoning engine resource, authenticating end to end. Under the hood, :streamQuery dispatches to the AdkApp 's streaming agent run with events method — when debugging an ADK invocation, search the runtime's reasoning engine stderr logs for that method name to trace the failure. It's also the path to use when the agent needs an OAuth authorization ( authorization id ). The agent is registered directly via its reasoning engine resource name; no agent card URL is needed. Programmatic Mode (CI/CD) The command is non interactive by default — pass all required values via flags or environment variables. This makes it safe for CI/CD pipelines. Via flags Via environment variables Most flags have an env var alternative ( metadata file , interactive , and list do not): Interactive Mode ( interactive ) Pass interactive (or i ) to be guided through any missing values with interactive prompts. The command will list available Gemini Enterprise apps, offer to auto detect the agent runtime ID from metadata, and prompt for display name and description. Complete Flag Reference Flag Env Var Description agent runtime id AGENT RUNTIME ID Agent Runtime resource name (auto detected from deployment metadata.json ) gemini enterprise app id ID or GEMINI ENTERPRISE APP ID Gemini Enterprise app full resource name display name GEMINI DISPLAY NAME Display name in Gemini Enterprise description GEMINI DESCRIPTION Agent description tool description GEMINI TOOL DESCRIPTION Tool description (ADK mode only, defaults to description) registration type REGISTRATION TYPE adk or a2a (defaults to adk for an ADK agent on Agent Runtime, a2a everywhere else, including any non ADK framework) agent card url AGENT CARD URL Agent card URL for A2A registration deployment target DEPLOYMENT TARGET agent runtime , cloud run , or gke (sets the default registration type — ADK on Agent Runtime, A2A on Cloud Run / GKE — and the A2A auth method) project id GOOGLE CLOUD PROJECT GCP project ID for billing project number PROJECT NUMBER GCP project number (used for Gemini Enterprise lookup) authorization id GEMINI AUTHORIZATION ID OAuth authorization resource name metadata file — Path to deployment metadata (default: deployment metadata.json ) interactive / i — Enable interactive prompts list — List Gemini Enterprise apps in the current project and exit Auto Detection from Metadata When deployment metadata.json exists, the command automatically: Reads the agent runtime ID ( remote agent runtime id ) Determines the registration type : defaults to ADK (native :streamQuery ) on Agent Runtime , and A2A on Cloud Run / GKE (which have no reasoning engine). A project scaffolded with another framework serves no ADK app, so it defaults to A2A on every target. Override with registration type . Determines the deployment target for authentication This means that for the simplest case (an ADK agent on Agent Runtime, registered as ADK), you only need to provide the Gemini Enterprise app ID: SDK Compatibility Agent Runtime deployments may encounter "Session not found" errors with google cloud aiplatform versions <= 1.128.0. In interactive mode ( interactive ), the command checks the SDK version from uv.lock and offers to upgrade. In programmatic mode, ensure your SDK is up to date before registering. Agent Registry (agents and MCP servers) Agent Registry (Preview) is the Google Cloud fleet wide catalog of agents and MCP servers , separate from a Gemini Enterprise app. Agents deployed to a managed runtime (Agent Runtime on Gemini Enterprise Agent Platform) are auto registered — no extra step after agents cli deploy . Manage them with gcloud (requires roles/agentregistry.editor ): Terraform: google agent registry service with an mcp server spec block. Docs: https://docs.cloud.google.com/agent registry/manage agents · https://docs.cloud.google.com/agent registry/register mcp servers Troubleshooting Issue Solution "Session not found" after registration SDK version issue — upgrade google cloud aiplatform (see SDK Compatibility above), redeploy, then re register registration type is required Non interactive mode needs registration type when no deployment metadata.json exists "Gemini Enterprise App ID is required" Provide gemini enterprise app id or set the ID / GEMINI ENTERPRISE APP ID env var Re publishing the same agent Registration is idempotent — re running updates the existing registration in place instead of creating a duplicate HTTP 403 on registration Check that your account has Discovery Engine Editor permissions on the Gemini Enterprise project Debugging ADK invocation failures on Agent Runtime Gemini Enterprise calls the agent via the AdkApp 's streaming agent run with events method (the native :streamQuery contract). Grep the runtime's reasoning engine stderr logs for streaming agent run with events to find the underlying error "Could not fetch agent card" Verify the agent is running and the URL is correct; for Cloud Run, ensure gcloud auth login is done Related Skills /google agents cli deploy — Deployment targets, CI/CD pipelines, and production workflows (also covers Agent Gateway governed ingress/egress and Semantic Governance awareness) /google agents cli workflow — Development workflow, coding guidelines, and operational rules /google agents cli scaffold — Project creation and enhancement with agents cli scaffold create / scaffold enhance

google-agents-cli-publish