AXME
Add durable state, HITL, and cross-agent coordination to AutoGen workflows
AutoGen's GroupChat and conversational patterns break when agents need to wait for external systems, humans, or other services. There's no durable state across conversation turns.
Integrate AXME Cloud with Microsoft AutoGen.
AutoGen excels at multi-agent conversation inside one process. When agents live on different machines or need human approval mid-conversation, you need a lifecycle layer — AXP intents coordinate handoffs, waits, and audit without a bespoke message broker per team.
Quickstart
import axme from autogen import GroupChat chat = GroupChat(...) await axme.autogen.run(chat, task)
In-process vs cross-host
AutoGen only
# GroupChat on one machine manager.run(task)
AutoGen + AXME
# AXP intent links agents on host A and B await axme.autogen.run(manager, task)
PATTERNS
Common production patterns.
Cross-machine handoff
Agents on different hosts share intent state.
Human checkpoint
Manager approval without custom UI per gate.
Multi-agent coordination
Shared intent.
Learn more →Related reading
Deeper dives from the AXME blog.
Your AutoGen Agents Can't Talk Across Machines. Here's the Missing Piece.
AutoGen handles multi-agent conversations beautifully - inside one process. Put agents on different machines and you're back to building message brokers from scratch.
Read post →A2A Tells Agents How to Talk. It Doesn't Tell Them What Happens When Things Break.
Google's A2A protocol handles agent communication. But crash recovery, retries, timeouts, and human approval gates? That's still on you. Unless you add a lifecycle layer.
Read post →
Related capabilities
Related links
Ship your first durable agent — in under 10 minutes.
Free tier. No credit card. Self-host or hosted — your choice.