Agentic (ACP) Agent Guide
This guide demonstrates how to interact with agentic (async) AgentEx agents using the AgentEx SDK.Overview
Agentic agents use an agentic ACP architecture that:- Supports both streaming and non-streaming responses
- Requires explicit task creation before sending events
- Ideal for complex workflows and long-running operations
Key API Method: send_event()
For agentic (ACP) agents, you always use the send_event()
method to communicate with the agent. This is different from sync agents, which use send_message()
for direct communication.
- Task creation required - Must create a task before sending events (sync agents don’t need this)
- Event-based communication - Send events to tasks, not direct messages to agent names
- Asynchronous processing - Events are processed asynchronously, poll or stream for responses
ACP Types: Base vs Temporal
Agentic agents can be implemented using two different backend types:- Base ACP - Simple event-driven architecture, suitable for learning and simple use cases
- Temporal - Robust workflow engine for production, handles race conditions automatically
send_event()
). The choice between base and Temporal is purely a server-side implementation detail that is transparent to client code. You can switch an agent from base to Temporal (or vice versa) without changing any client code.