This sample demonstrates how to use Redis Streams with agent response callbacks to enable reliable, resumable streaming for durable agents. Streaming responses are persisted to Redis, allowing clients to disconnect and reconnect without losing messages.
- Using
AgentResponseCallbackProtocolto capture streaming agent responses. - Persisting streaming chunks to Redis Streams for reliable delivery.
- Non-blocking agent execution with
options={"wait_for_response": False}(fire-and-forget mode). - Cursor-based resumption for disconnected clients.
- Decoupling agent execution from response streaming.
In addition to the common setup in the parent README.md, this sample requires Redis:
docker run -d --name redis -p 6379:6379 redis:latestSee the README.md file in the parent directory for more information on how to configure the environment, including how to install and run common sample dependencies.
Additional environment variables for this sample:
# Optional: Redis Configuration
REDIS_CONNECTION_STRING=redis://localhost:6379
REDIS_STREAM_TTL_MINUTES=10With the environment setup, you can run the sample using the combined approach or separate worker and client processes:
Option 1: Combined (Recommended for Testing)
cd samples/04-hosting/durabletask/03_single_agent_streaming
python sample.pyOption 2: Separate Processes
Start the worker in one terminal:
python worker.pyIn a new terminal, run the client:
python client.pyThe client will send a travel planning request to the TravelPlanner agent and stream the response from Redis in real-time:
================================================================================
TravelPlanner Agent - Redis Streaming Demo
================================================================================
You: Plan a 3-day trip to Tokyo with emphasis on culture and food
TravelPlanner (streaming from Redis):
--------------------------------------------------------------------------------
# Your Amazing 3-Day Tokyo Adventure! 🗾
Let me create the perfect cultural and culinary journey through Tokyo...
## Day 1: Traditional Tokyo & First Impressions
...
(continues streaming)
...
✓ Response complete!
The RedisStreamCallback class implements AgentResponseCallbackProtocol to capture streaming updates and persist them to Redis:
class RedisStreamCallback(AgentResponseCallbackProtocol):
async def on_streaming_response_update(self, update, context):
# Write chunk to Redis Stream
async with await get_stream_handler() as handler:
await handler.write_chunk(thread_id, update.text, sequence)
async def on_agent_response(self, response, context):
# Write end-of-stream marker
async with await get_stream_handler() as handler:
await handler.write_completion(thread_id, sequence)The worker registers the agent with the Redis streaming callback:
redis_callback = RedisStreamCallback()
agent_worker = DurableAIAgentWorker(worker, callback=redis_callback)
agent_worker.add_agent(create_travel_agent())The client uses fire-and-forget mode to start the agent and streams from Redis:
# Start agent run with wait_for_response=False for non-blocking execution
travel_planner.run(user_message, thread=thread, options={"wait_for_response": False})
# Stream response from Redis while the agent is processing
async with await get_stream_handler() as stream_handler:
async for chunk in stream_handler.read_stream(thread_id):
if chunk.text:
print(chunk.text, end="", flush=True)
elif chunk.is_done:
breakFire-and-Forget Mode: Use options={"wait_for_response": False} to enable non-blocking execution. The run() method signals the agent and returns immediately, allowing the client to stream from Redis without blocking.
Clients can resume streaming from any point after disconnection:
cursor = "1734649123456-0" # Entry ID from previous stream
async with await get_stream_handler() as stream_handler:
async for chunk in stream_handler.read_stream(thread_id, cursor=cursor):
# Process chunkYou can view the state of the TravelPlanner agent in the Durable Task Scheduler dashboard:
- Open your browser and navigate to
http://localhost:8082 - In the dashboard, you can view:
- The state of the TravelPlanner agent entity (dafx-TravelPlanner)
- Conversation history and current state
- How the durable agents extension manages conversation context with streaming