[Feature]: Add AG2 provider support

[VasiliyRad]

Area of Improvement

Python SDK

Feature Name

Add AG2 (AutoGen) provider support

Describe the Feature

Summary

This issue proposes adding native support for AG2 as a Composio provider, similar to the existing Autogen integration.
AG2 is one of the most widely adopted AI agent frameworks, with 20,000+ developers and ~400,000 monthly downloads. While AG2 and Autogen share the same PyPI package (ag2/autogen are aliases), AG2 has its own distinct identity, community, and branding. Developers building with AG2 would benefit from a first-class Composio integration under the composio-ag2 package name.

Use Case / Motivation

AG2 users currently have no dedicated Composio provider — they would need to use composio-autogen and know it's compatible, which is not obvious.
A dedicated composio-ag2 package improves discoverability and the developer experience for the AG2 community.
This mirrors how other frameworks (e.g. LangChain, CrewAI) have their own provider packages.

Proposed Solution or API Design (Optional)

Add a composio_ag2 provider package under python/providers/ag2/
The provider wraps Composio tools as FunctionTool objects compatible with AG2's ConversableAgent
Include a working demo (ag2_demo.py) and documentation page
The implementation can delegate to or extend AutogenProvider to avoid code duplication

Who does this impact?

• Developers using the SDK
• AI Agent frameworks (LangChain, OpenAI, etc.)
• Dashboard users
• End users of connected apps

Related Issues / References

No response

Would you like to contribute to this feature?

• Yes, I can help implement it
• Maybe, I can help test or review
• No, just sharing the idea

Additional Context

#2615

[Uday-sidagana]

Hey @VasiliyRad, could you checkout our doc: https://docs.composio.dev/docs/providers/autogen. Let me know if this works for you.

[VasiliyRad]

Hi Uday,

Thanks for the pointer! Unfortunately, the existing AutoGen doc doesn't fully address the AG2 use case, for a few reasons:

1. The code example isn't compatible with AG2 0.11

The doc uses the deprecated config_list dict form for llm_config:

llm_config={"config_list": [{"model": "gpt-5.2"}]}

In AG2 0.9+, the modern API is LLMConfig({"model": "...", "api_key": "..."}). The config_list kwarg form is explicitly marked deprecated in AG2 0.11. The doc also uses user_proxy.initiate_chat(...), while AG2's current recommended pattern is user_proxy.run(assistant, message=...).process().

2. AG2 and AutoGen are not the same project

AG2 is the community-driven fork of AutoGen under active development (20k+ developers, ~400k monthly downloads), while Microsoft's AutoGen is no longer actively maintained. They share the same PyPI package names (ag2/autogen are aliases), but have distinct identities, communities, docs, and branding. Pointing AG2 developers to an "AutoGen" page creates real confusion — it signals the integration is built for the old, unmaintained project.

3. A dedicated page matters for discoverability

Other active frameworks (LangChain, CrewAI) have their own Composio provider pages. AG2 users searching for "composio ag2" currently find nothing, while AG2-specific examples with the correct 0.11 API would immediately unblock them.

4. There's already a PR for this

PR #2615 brings native AG2 integration — it's a clear signal this is the right direction. A dedicated composio-ag2 package and docs page (using the current AG2 API) would close the gap properly.

Happy to help validate examples or review the docs if that unblocks things!