LIFEHUBBER
Theme

AI Resources

AG2

GitHub stars: 4.9K GitHub forks: 712 Declared license: Apache-2.0: Apache-2.0 Last pushed September 7, 2026: Pushed today
Stats from GitHub

AG2 v1 is a Python framework for building agents that can use models and tools, pause for human input, and coordinate through a multi-agent Network.

The current package uses an Agent class and a protocol-driven Network with a central hub and typed channels. The older AutoGen-derived classes and patterns now live in the separately maintained AG2 Classic repository. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

Agents connected through a Network

A single Agent can call models and Python tools. When several agents need to work together, AG2 can connect them through a hub with conversation, consulting, discussion, or workflow channels.

Why it stands out

A clear split between v1 and Classic

AG2 v1 is not a drop-in upgrade from AG2 Classic. Existing projects using ConversableAgent, GroupChat, swarms, or the autogen import should follow the maintained Classic package and its migration guidance.

Availability

Repository, docs, examples, and PyPI

AG2 v1 is available on PyPI, with a GitHub repository, current documentation, runnable examples, and a Network guide for its hub-and-channel orchestration.

Why it matters

What makes it useful

AG2 v1 separates a standalone Agent from its optional multi-agent Network. The Network adds a hub, named participants, typed channels, durable message records, and rules for how agents exchange work.

Notable points

What stands out

Check the import before following an example: import ag2 is the current v1 framework, while import autogen and classes such as ConversableAgent or GroupChat belong to AG2 Classic.

Before using

What to review

Whether the project is starting on AG2 v1 or maintaining AG2 Classic, because their agent models, orchestration, imports, and documentation differ.

The model-provider setup, API-key handling, tool permissions, and human-input points in any workflow.

Whether a Network is actually needed, or whether one Agent with a small set of tools would be easier to inspect.

Reader fit

Who may find it relevant

Developers and researchers comparing multi-agent channel patterns and orchestration styles.

Readers studying how current AG2 Agents use tools, ask for human input, and coordinate through a Network hub and typed channels.

Not the first stop for readers who want a visual workflow builder, a voice-agent transport stack, or a simple consumer app.

Editorial note

Why LifeHubber lists it

AG2 is most useful when a project benefits from explicit coordination rules: who can participate, which channel pattern governs the exchange, when tools run, and where the application asks a person for input.

Source links

Source materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

What to explore next

Compare how agents coordinate work.

AG2 v1 coordinates agents through a hub and typed channels, with tools and human input available inside the work. Compare a lighter code-first toolkit, a Python framework that separates agent teams from explicit flows, or the wider framework landscape.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

See what’s moving