# autogen - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `microsoft/autogen` - capability: A programming framework for agentic AI - expected_user_outcome: A programming framework for agentic AI ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Framework Overview and Layered Architecture**: importance `high` - source_paths: README.md, python/packages/autogen-core/README.md, python/packages/autogen-agentchat/README.md, python/packages/autogen-ext/README.md, dotnet/README.md - **Core API: Agent Runtime, Messaging, and Distribution**: importance `high` - source_paths: python/packages/autogen-core/src/autogen_core/_agent.py, python/packages/autogen-core/src/autogen_core/_agent_id.py, python/packages/autogen-core/src/autogen_core/_agent_runtime.py, python/packages/autogen-core/src/autogen_core/_agent_proxy.py, python/packages/autogen-core/src/autogen_core/_topic.py - **AgentChat: Multi-Agent Orchestration Patterns**: importance `high` - source_paths: python/packages/autogen-agentchat/src/autogen_agentchat/agents/_assistant_agent.py, python/packages/autogen-agentchat/src/autogen_agentchat/agents/_code_executor_agent.py, python/packages/autogen-agentchat/src/autogen_agentchat/agents/_user_proxy_agent.py, python/packages/autogen-agentchat/src/autogen_agentchat/agents/_society_of_mind_agent.py, python/packages/autogen-agentchat/src/autogen_agentchat/base/_chat_agent.py - **Extensions, Tools, Models, and Developer Tooling**: importance `high` - source_paths: python/packages/autogen-ext/src/autogen_ext/models/openai/_openai_client.py, python/packages/autogen-ext/src/autogen_ext/models/anthropic/_anthropic_client.py, python/packages/autogen-ext/src/autogen_ext/models/azure/_azure_ai_client.py, python/packages/autogen-ext/src/autogen_ext/models/ollama/_ollama_client.py, python/packages/autogen-ext/src/autogen_ext/tools/mcp/_workbench.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `027ecf0a379bcc1d09956d46d12d44a3ad9cee14` - inspected_files: `README.md`, `docs/design/01 - Programming Model.md`, `docs/design/02 - Topics.md`, `docs/design/03 - Agent Worker Protocol.md`, `docs/design/04 - Agent and Topic ID Specs.md`, `docs/design/05 - Services.md`, `docs/design/readme.md`, `docs/dotnet/README.md`, `docs/dotnet/core/differences-from-python.md`, `docs/dotnet/core/index.md`, `docs/dotnet/core/installation.md`, `docs/dotnet/core/protobuf-message-types.md`, `docs/dotnet/core/toc.yml`, `docs/dotnet/core/tutorial.md`, `docs/dotnet/docfx.json`, `docs/dotnet/index.md`, `docs/dotnet/template/public/main.js`, `docs/dotnet/toc.yml`, `docs/switcher.json` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/4564 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/7487 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/7748 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: Cryptographic governance layer for AutoGen distributed agent runtime - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Cryptographic governance layer for AutoGen distributed agent runtime. Context: Observed during version upgrade or migration. - Why it matters: Developers may expose sensitive permissions or credentials: Cryptographic governance layer for AutoGen distributed agent runtime - Evidence: failure_mode_cluster:github_issue | https://github.com/microsoft/autogen/issues/7372 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/7372 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/7321 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/7875 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/7770 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/7265 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/microsoft/autogen/issues/7356 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.