feat: add display_name support and rebrand langgraph as custom_a2a#737
feat: add display_name support and rebrand langgraph as custom_a2a#737eliasecchig merged 1 commit intomainfrom
Conversation
- Add display_name field to templateconfig.yaml for custom agent names
- Update create and list commands to use display_name when available
- Rebrand langgraph template as "custom_a2a" ("Bring your own framework")
- Add "custom" and "custom_a2a" aliases pointing to langgraph template
- Change group header from "Python (LangGraph)" to "Python (A2A)"
Summary of ChangesHello @eliasecchig, 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 enhances the agent template system by introducing a dedicated Highlights
Using Gemini Code AssistThe 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 by creating a comment using either
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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces support for a display_name for agent templates and rebrands the langgraph template to custom_a2a for better discoverability. The changes are consistently applied across the CLI commands for creating and listing agents, as well as in the template utility functions. Aliases have been added for backward compatibility.
The implementation is solid. I've made one suggestion in create.py to dynamically calculate the padding for agent names in the selection menu. This will make the UI more robust against longer display names in the future.
Overall, this is a good enhancement that improves user experience and template organization.
…oogleCloudPlatform#737) - Add display_name field to templateconfig.yaml for custom agent names - Update create and list commands to use display_name when available - Rebrand langgraph template as "custom_a2a" ("Bring your own framework") - Add "custom" and "custom_a2a" aliases pointing to langgraph template - Change group header from "Python (LangGraph)" to "Python (A2A)"
Summary
display_namefield support for agent templatesChanges
display_name: "custom_a2a"and updated description to "Bring your own framework, A2A-ready"display_namewhen available in agent selection menu; changed group header from "🦜 Python (LangGraph)" to "🐍 Python (A2A)"display_namewhen available in agent list tablecustomandcustom_a2aaliases pointing tolanggraph; extractdisplay_namefrom configRationale
The langgraph template serves as a "bring your own framework" option. Rebranding it as
custom_a2amakes this purpose clearer while maintaining backward compatibility through aliases.