Agent Runtime deploy with A2A agent type

Open
#63 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
google-cloud, python
Domain
cloud

Research direction

Start at the agents-cli deploy entry point and trace how deployed ADK agents are represented for Agent Runtime and Agent Registry discovery. Read the existing deployment and discovery-related documentation or tests, then verify the deployed agent's A2A capability is recognized by Gemini Enterprise App without creating a duplicate registry entry.

Written by the indexing model from the issue text.

Description

What is your feature suggestion?

Enable agents-cli deployed agents to be discovered by the new Gemini Enterprise App feature called "Agents from Agent Registry".

What will this enable you to do?

Gemini Enterprise App (I hope I get the freaking naming right here) introduced a new feature that enables one to easily register an agent from Agent Registry. The problem is that this feature is limited to agents supporting A2A. agents-cli deploy actually deploys ADK agents with A2A support but Agent Runtime has no idea that the agent actually supports A2A as the agent is deployed with agent_framework="google-adk".

Due to this fact, the automatic discovery feature of Agent Registry/Agent Runtime correctly discovers the agent but again it doesn't discover the A2A capability of the agent. And because of this, these agents are never recognized by the Gemini Enterprise App drawing the "Agents from Agent Registry" useless for agents deployed with agents-cli even though the support for A2A is actually in place.

Additional context

Haven't tested yet but it should be possible to register the agents-cli deployed agent to Agent Registry manually by specify the agent card URL but this would make the same agent appear twice in the Agent Registry as the first is auto-discovered ADK agent and the second the manually registered one which is not ideal.

Dominant language
Python
Stars
6k
Forks
670
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/agents-cli

All issues in google/agents-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.