-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feat!: Add method for fetching extended card #929
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @kthota-g, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request focuses on extending the A2A specification by adding a new JSON-RPC method to fetch an 'extended card'. It includes the necessary type definitions for the request, successful response, and a dedicated error type for when the extended card is not configured. This change enhances the API's functionality by providing a structured way to retrieve this specific card information.
Highlights
- New API Method Definition: This pull request introduces a new JSON-RPC method,
agent/authenticatedExtendedCard, designed for fetching an extended card. This expands the A2A specification's capabilities. - Request and Response Types: New TypeScript interfaces and types have been defined for the
agent/authenticatedExtendedCardmethod, includingGetAuthenticatedExtendedCardRequest,GetAuthenticatedExtendedCardSuccessResponse, andGetAuthenticatedExtendedCardResponse, to standardize the communication structure. - New Error Type: A specific error type,
AuthenticatedExtendedCardNotConfiguredError(with error code -32007), has been added to handle scenarios where an authenticated extended card is not configured, improving error handling clarity. - API Type Integration: The core
JSONRPCResponse,A2ARequest, andA2AErrorunion types have been updated to incorporate the newly defined request, response, and error types, ensuring they are recognized within the A2A specification.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces the agent/authenticatedExtendedCard method for fetching an extended agent card and adds corresponding TypeScript types. The review includes suggestions for improving type safety, documentation, and ensuring proper handling of the new method, response, and error types throughout the application.
|
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request successfully refactors the method for fetching an extended agent card from a REST-style GET endpoint to a proper JSON-RPC method. The changes are consistent across the specification document, JSON schema, and TypeScript types. I've left a few comments to improve the consistency of the documentation, particularly around error handling, and to correct some copy-paste errors in descriptions within the schema and type files. Overall, this is a good improvement that aligns the new method with the rest of the A2A protocol.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
# Description Types are manually generated for implementing this PR, but this feature has types dependency on a2aproject/A2A#929 and can only be merged once the type changes are merged into this repository. This PR adds support for agent/authenticatedExtendedCard JSON-RPC method for serving authenticated extended card. The previous HTTP GET /agent/authenticatedExtendedCard endpoint has been deprecated and will be removed in a future release. Release-As: 0.3.0
🤖 I have created a release *beep* *boop* --- ## [0.3.0](v0.2.6...v0.3.0) (2025-07-30) ### ⚠ BREAKING CHANGES * Add mTLS to SecuritySchemes, add oauth2 metadata url field, allow Skills to specify Security ([#901](#901)) * Change Well-Known URI for Agent Card hosting from `agent.json` to `agent-card.json` ([#841](#841)) * Add method for fetching extended card ([#929](#929)) ### Features * Add `signatures` to the `AgentCard` ([#917](#917)) ([ef4a305](ef4a305)) * Add method for fetching extended card ([#929](#929)) ([2cd7d98](2cd7d98)) * Add mTLS to SecuritySchemes, add oauth2 metadata url field, allow Skills to specify Security ([#901](#901)) ([e162c0c](e162c0c)) ### Bug Fixes * **spec:** Add `SendMessageRequest.request` `json_name` mapping to `message` ([#904](#904)) ([2eef3f6](2eef3f6)) * **spec:** Add Transport enum to specification ([#909](#909)) ([e834347](e834347)) ### Code Refactoring * Change Well-Known URI for Agent Card hosting from `agent.json` to `agent-card.json` ([#841](#841)) ([0858ddb](0858ddb)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Description
This change adds support for a new JSON-RPC method
agent/getAuthenticatedExtendedCardfor fetching authenticated extended card.This is only applicable if
AgentCard.supportsAuthenticatedExtendedCardbit is set totruethat allows fetching authenticated context specific agent card.In the previous versions, the extended card was served via
{AgentCard.url}/../agent/authenticatedExtendedCardendpoint. This endpoint is being removed in favor of the JSON-RPC method. This endpoint will be deprecated in the SDKs and will be removed in a future release.Release-As: 0.3.0