GitHub Agent and Tools in AG2

[marufaytekin]

Hi folks,

I propose creating a GitHub agent and necessary tools in AG2. This will enable developers and automation engineers to build agents that automate tasks related to code and change log analysis.

Key tool operations include:

Search:

• Code search
• Issue and pull request search

Read:

• List open pull requests (PRs)
• View PR commit patches (changes)
• List merged PRs (filter by date range)
• List files in a PR
• Retrieve files from multiple PRs
• List files in a branch
• Retrieve files from a directory
• Read file(s)

Write:

• Create a pull request
• Create, update, or delete a file
• Set the active branch
• Create a new branch
• Request a review

Once these tools are built, we can develop dedicated agents such as a GitHub Agent and a PR Review Agent.

Please let me know what you think.

[marklysze]

Love it!

[marufaytekin]

@marklysze @davorrunje I think this requires a mechanism similar to toolbox (in Langchain) or register_tool_group (in Autogen). All these functionalities can't be implemented as separate tools. It'll be too messy.

Do AG2 support registering a class containing multiple methods as distinct tools, where the LLM agent can dynamically select which method to call based on context?

[marklysze]

I believe there was a discussion about a toolkit, @davorrunje.

BTW, I love the idea of this agent! I can definitely see it as an agent with the tools (or a tool kit). I feel a bit of an internal workflow and custom system message would help.

[marufaytekin]

@marklysze @davorrunje There are reference MCP servers published for Git/GitHub, etc.: MCP Servers Repo.

Instead of implementing tools from scratch, we could implement an Agent (e.g., a Git Agent) that runs MCP Server (Git) as local process (direct execution) or in Docker and then use client to utilize the tools provided by the MCP server.

Does this approach make sense to you? Are there any potential challenges or alternative considerations we should keep in mind?

Looking forward to your thoughts!

[marufaytekin]

Will be implemented with this issue: #1654