Skip to main content

composio-autogen

Adapts Composio tools to AutoGen FunctionTool objects and registers them with your caller and executor agents, so your AutoGen agents can take action across 1000+ apps.

Installation

pip install composio composio-autogen 'ag2[openai]'

Set COMPOSIO_API_KEY (from the dashboard) and OPENAI_API_KEY in your environment.

Quickstart

import os

from autogen import AssistantAgent, LLMConfig, UserProxyAgent
from composio import Composio
from composio_autogen import AutogenProvider

composio = Composio(provider=AutogenProvider())

# Each session is scoped to one of your users
session = composio.create(user_id="user_123")
tools = session.tools()

chatbot = AssistantAgent(
    "chatbot",
    system_message="Reply TERMINATE when the task is done or when user's content is empty",
    llm_config=LLMConfig({
        "api_type": "openai",
        "model": "gpt-5.2",
        "api_key": os.environ["OPENAI_API_KEY"],
    }),
)

user_proxy = UserProxyAgent(
    "user_proxy",
    is_termination_msg=lambda msg: "TERMINATE" in (msg.get("content", "") or ""),
    human_input_mode="NEVER",
    code_execution_config={"use_docker": False},
)

# Register tools with both agents
composio.provider.register_tools(caller=chatbot, executor=user_proxy, tools=tools)

response = user_proxy.initiate_chat(
    chatbot,
    message="Send an email to john@example.com with the subject 'Hello' and body 'Hello from Composio!'",
)

print(response.chat_history)

For multi-turn use, store session.session_id and reuse it with composio.use(session_id) instead of calling create() again.

Provider specifics

AutoGen needs tools registered with two agents, not passed once. Call composio.provider.register_tools(caller=..., executor=..., tools=tools): the caller decides which tool to invoke, and the executor runs it. This method is unique to the AutoGen provider.

AutoGen caps function names at 64 characters, so the provider hashes and truncates long tool slugs to stay under the limit. The registered name will not always match the original Composio slug.

Metadata

Release files for composio-autogen 0.33.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for composio-autogen 0.33.0
File Size Uploaded Provenance Actions
composio_autogen-0.33.0.tar.gz 5.3 kB With provenance Details for composio_autogen-0.33.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for composio-autogen 0.33.0
File Interpreter ABI Platform Actions
composio_autogen-0.33.0-py3-none-any.whl Python 3 none any Details for composio_autogen-0.33.0-py3-none-any.whl

Total release size: 10.8 kB

Release files / composio_autogen-0.33.0.tar.gz

Download URL composio_autogen-0.33.0.tar.gz
Size 5.3 kB
Tags Source
SHA-256 checksum
How to use checksums
ca6b0c120fd66842c370e86fd708da0b32948d5e20b10565aaf665afdc7666cf
BLAKE2b-256 checksum
How to use checksums
45eeb5430945e66e651200cc67fbbf50337c8506e2a0a4cc5160e68a315a124e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / composio_autogen-0.33.0-py3-none-any.whl

Download URL composio_autogen-0.33.0-py3-none-any.whl
Size 5.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b01c759b23f64b3294cec09706b128b6b95130c7d781cabc8753e3d89df390d9
BLAKE2b-256 checksum
How to use checksums
bc42e81a3cdaf1488c1cf2f3d943fb5799829360c1457b0ce87a8984870bba6c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Security for composio-autogen 0.33.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for composio_autogen-0.33.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.33.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page