The #1 mistake with AutoGen is pip install autogen or pip install pyautogen. That often drops you on AG2 or the classic ConversableAgent line – not Microsoft’s AgentChat stack. You paste 0.2-era snippets, hit import errors, and burn an afternoon. Feels like grabbing the wrong USB-C brick: it fits the outlet, nothing downstream works.
Pin the Microsoft names. Clean virtualenv. Install the OpenAI (or other) extra on purpose. Verify with one async agent. As of python-v0.7.5 (30 Sep 2025), that path holds.
Up front: AutoGen sits in maintenance mode on the official GitHub README. New greenfield work gets pointed at Microsoft Agent Framework. Still need 0.7.5 for an existing codebase or to learn AgentChat? This guide gets the install clean.
System requirements for AutoGen 0.7.5
Hard floor from the docs and PyPI: Python 3.10 or later. Classifiers mark the packages OS-independent.
| Item | Minimum | Notes |
|---|---|---|
| Python | 3.10 | 3.11 or 3.12 are the least surprising day-to-day |
| OS | Windows / macOS / Linux | Any box with a working venv + pip |
| RAM / CPU / disk | Not officially specified | Package weight is small; real overhead is the model client and how many agents you run at once |
| Docker (optional) | Daemon up if you use DockerCommandLineCodeExecutor | Docker Desktop or engine with pull access |
| Node.js | Only if you build AutoGen Studio from source | Not required for the PyPI Studio wheel |
API key for the model client you pick (OpenAI, Azure, Ollama, …). Importing the libraries alone needs no key.
Official download / source
Skip random wheels.
- PyPI:
autogen-agentchatandautogen-ext(both 0.7.5 on the Sep 2025 release) - GitHub: https://github.com/microsoft/autogen (tag
python-v0.7.5) - Docs: https://microsoft.github.io/autogen/stable/
- Studio UI (optional):
autogenstudioon PyPI – 0.4.2.2 as of mid-2025, so version lag is real
Those four. Full stop. Anything else is a fork or the old line.
Install AutoGen multi agent framework step by step
Isolated env first. Global site-packages is how the wrong autogen name sneaks in.
# Linux / macOS
python3 -m venv .venv
source .venv/bin/activate
# Windows (cmd)
python -m venv .venv
.venvScriptsactivate.bat
# Or conda
conda create -n autogen python=3.12
conda activate autogen
AgentChat + OpenAI extension – the line from the README and installation docs:
pip install -U "autogen-agentchat" "autogen-ext[openai]"
Azure AD, Docker code exec, Ollama, Anthropic, Redis, disk cache? Stack the extras:
pip install -U "autogen-ext[openai,azure,docker,ollama,anthropic,redis,diskcache]"
Optional no-code UI:
pip install -U autogenstudio
Pro tip: Old
pyautogen, bareautogen, or a mismatched Studio already in the env? Uninstall them first – or delete the venv and start over. Name collisions cause most “wrong API imported” reports.
From source only if you plan to patch (pip install -e inside the monorepo packages). Contributors get .devcontainer setups. Everyone else: PyPI.
First-time configuration
Drop the ceremony. One env var. One tiny async script. No YAML to boot.
# Linux/macOS
export OPENAI_API_KEY="sk-..."
# Windows PowerShell
$env:OPENAI_API_KEY = "sk-..."
Or python-dotenv + a .env file. Keep keys out of git.
Local Ollama: install the ollama extra, point the client at the local base URL, pass a model_info dict (vision / function_calling flags). Shape lives in the migration guide and model tutorial – not worth reinventing here.
Verify the install works
Versions first:
pip show autogen-agentchat autogen-ext
python -c "import autogen_agentchat, autogen_ext; print('imports ok')"
Then the async AgentChat hello-world:
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
async def main() -> None:
model_client = OpenAIChatCompletionClient(model="gpt-4o")
agent = AssistantAgent("assistant", model_client=model_client)
result = await agent.run(task="Say 'Hello World!'")
print(result)
await model_client.close()
asyncio.run(main())
See a model reply? Core is live. Studio:
autogenstudio ui --port 8080 --appdir ./my-app
# open http://localhost:8080
Common install errors and fixes
- Wrong package / old API –
from autogen import ...works but nothing matches current docs, or you landed on AG2. Uninstallautogen/pyautogen/ag2, new venv, onlyautogen-agentchat+autogen-ext[...]. - ModuleNotFoundError: autogen_ext… (e.g.
autogen_ext.models.openai) – agentchat without the extension extra.pip install "autogen-ext[openai]"(or the extras you need). Community threads hit this constantly. - DockerCommandLineCodeExecutor missing dependencies – error text asks for the docker extra. Install
autogen-ext[docker], confirmdocker infoon the host. 0.7.x also nudged security defaults toward the Docker executor. - Studio + agentchat resolver fight – issue #7173 and similar reports: 0.7.5 vs studio 0.4.2.2. Separate envs, or pin a known pair until Studio catches up. Code-first work? Skip Studio in that env.
- Python edge quirks – stay on 3.10-3.12 for fewer surprises.
Upgrade, migrate, and uninstall
In place:
pip install -U "autogen-agentchat" "autogen-ext[openai]"
# optional
pip install -U autogenstudio
Coming from 0.2? Different packages and APIs – model_client instead of llm_config, async handlers, Team abstractions. Use the official migration guide. No drop-in script hope.
Cleanup:
pip uninstall -y autogen-agentchat autogen-ext autogenstudio autogen-core
pip uninstall -y autogen pyautogen ag2
rm -rf .venv # or: conda env remove -n autogen
Studio app data under ~/.autogenstudio or your --appdir if you want a full wipe. Don’t hand-delete inside site-packages.
One open question the docs still leave fuzzy: how much headroom you need when ten agents stream tools against a local 70B model. You’ll only know by measuring your own box.
FAQ
Which package name should I actually pip install for Microsoft AutoGen 0.7.5?
autogen-agentchat plus the extras you need from autogen-ext. Not bare autogen.
Do I need Docker to run a multi agent framework with AutoGen?
No. Agents and model clients run without it. Docker only matters when you turn on DockerCommandLineCodeExecutor for sandboxed code. Then install the docker extra and keep the daemon up. Prefer a local command-line executor only if you accept host risk – one bad generated script and you’re cleaning your own machine.
Is AutoGen still the right choice in late 2025 / 2026?
Short answer: maybe not, if you’re starting cold. The 0.7.5 AgentChat API is solid for prototypes and existing code. The project itself is in maintenance mode and steers new work to Microsoft Agent Framework with a published migration path. Need AutoGen’s current patterns or Studio this week? 0.7.5 still installs and runs. Starting fresh and want a longer support story? Evaluate MAF first. Check your timeline before you pin it.
Next: create the venv, run pip install -U "autogen-agentchat" "autogen-ext[openai]", paste the hello-world script, confirm a model reply – then touch teams or Studio.