copilot-swe-agent[bot]
9843355c83
- Moved getting_started/durabletask to durable/console_apps - Moved getting_started/azure_functions to durable/azure_functions - Updated all paths in README files - Created durable/README.md with overview - Updated main samples README.md with new structure Co-authored-by: larohra <41490930+larohra@users.noreply.github.com>
Single Agent Sample (Python)
This sample demonstrates how to use the Durable Extension for Agent Framework to create a simple Azure Functions app that hosts a single AI agent and provides direct HTTP API access for interactive conversations.
Key Concepts Demonstrated
- Defining a simple agent with the Microsoft Agent Framework and wiring it into an Azure Functions app via the Durable Extension for Agent Framework.
- Calling the agent through generated HTTP endpoints (
/api/agents/Joker/run). - Managing conversation state with thread identifiers, so multiple clients can interact with the agent concurrently without sharing context.
Prerequisites
Follow the common setup steps in ../README.md to install tooling, configure Azure OpenAI credentials, and install the Python dependencies for this sample.
Running the Sample
Send a prompt to the Joker agent:
Bash (Linux/macOS/WSL):
curl -i -X POST http://localhost:7071/api/agents/Joker/run \
-d "Tell me a short joke about cloud computing."
PowerShell:
Invoke-RestMethod -Method Post -Uri http://localhost:7071/api/agents/Joker/run `
-Body "Tell me a short joke about cloud computing."
The agent responds with a JSON payload that includes the generated joke.
Tip
To return immediately with an HTTP 202 response instead of waiting for the agent output, set the
x-ms-wait-for-responseheader or include"wait_for_response": falsein the request body. The default behavior waits for the response.
Expected Output
The default plain-text response looks like the following:
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
x-ms-thread-id: 4f205157170244bfbd80209df383757e
Why did the cloud break up with the server?
Because it found someone more "uplifting"!
When you specify the x-ms-wait-for-response header or include "wait_for_response": false in the request body, the Functions host responds with an HTTP 202 and queues the request to run in the background. A typical response body looks like the following:
{
"status": "accepted",
"response": "Agent request accepted",
"message": "Tell me a short joke about cloud computing.",
"thread_id": "<guid>",
"correlation_id": "<guid>"
}