First name the destination
‘I cannot find my agent’ is incomplete: is it absent from a Gemini app, a fleet-wide Agent Registry, or another agent’s discovery flow? Record the intended destination, project, location, account and deployed endpoint. A successful deployment in one project does not prove registration in a different app or project.
Keep credentials, private endpoints and account identifiers out of public troubleshooting notes. An endpoint URL is not permission to make it public or to broaden access until a test succeeds.
- Name the product or app where the agent should appear.
- Match the deployment and registration project/location.
- Use an account authorized to inspect the relevant resources.
Separate the four jobs
Choose the smallest role that answers the missing-stage question. Coding guidance is not deployment, and registration is not evidence that the service can answer correctly. Installing all four Skills does not grant cloud permissions or automatically connect the stages.
| Question | Skill | Expected artifact or state |
|---|---|---|
| How do I implement the agent? | google-agents-cli-adk-code | Code and API-pattern guidance |
| Where is the service running? | google-agents-cli-deploy | A deployed service and deployment metadata |
| How should consumers discover it? | google-agents-cli-publish | Registration of an existing endpoint |
| Which lifecycle stage comes next? | google-agents-cli-workflow | A staged plan with evaluation and approvals |
Inspect deployment evidence before deploying again
Check the actual deployment status, intended service and available deployment metadata. A local command timeout alone does not establish that the remote job failed. Check the existing operation before starting another deployment; a second run can change state or spend money without addressing a registration gap.
The reviewed publish workflow requires an already deployed, reachable agent. It can use deployment metadata for Agent Runtime; other targets need the appropriate endpoint information. Reachable does not mean unauthenticated or public: preserve the service’s intended access controls.
Check registration mode and transport
In the reviewed revision, an ADK app on Agent Runtime uses native ADK registration by default; Cloud Run and GKE use A2A registration. Other frameworks and runtime combinations need their documented mode. Do not choose a mode solely because a copied command used it.
For a Gemini app, check the actual app, service metadata and relevant permissions. The reviewed workflow does not support live/voice agents in that app. Separately, Agent Registry catalogs agents and MCP services; an entry there is not the same as registering with a Gemini app. Confirm which record you are inspecting before creating another one.
Make one approved change, then check the right outcome
Illustrative acceptance plan—not an executed fix: first prove the intended service exists; then identify the missing registration; approve one change against the exact destination; finally check discovery as an authorized intended user. Test the agent’s behavior separately. Visibility alone does not prove task quality or safety.
If permission is missing, ask the resource owner for the narrow access needed. Do not disable authentication, grant broad roles or delete a registration just to clear an error. Review cloud/model costs before any deploy or test that could create charges.
- Record existing resource identifiers before a write.
- Approve the exact registration/IAM change and destination.
- Keep a rollback or correction path for the changed record.
- Separate discoverability, access and behavior checks.
Source boundary
This guide analyzes google/agents-cli revision d445570c61fd446487ea6623c5635b23aded237f, checked October 19, 2026. The instruction files and hashes are recorded below. Product interfaces, current CLI flags and service permissions can change; consult the current official documentation before operating a live account.
We did not log in to Google Cloud, deploy an agent, change IAM, register or delete an endpoint, or reproduce this scenario. No measured resolution rate or keyword volume is claimed. The checklist is original editorial guidance, not a customer case study.