agent-framework/python/samples/05-end-to-end/ag_ui_workflow_handoff

AG-UI Handoff Workflow Demo

This demo is a full custom AG-UI application built on top of the new workflow abstractions in agent_framework_ag_ui.

It includes:

• A backend FastAPI AG-UI endpoint serving a HandoffBuilder workflow with:
  • triage_agent
  • refund_agent
  • order_agent
• Required tool approval checkpoints:
  • submit_refund (approval_mode="always_require")
  • submit_replacement (approval_mode="always_require")
• A second request-info resume step (order agent asks for shipping preference)
• A frontend React app that consumes AG-UI SSE events, renders workflow cards, and sends resume.interrupts payloads.

The backend uses Azure OpenAI responses and supports intent-driven, non-linear handoff routing.

Folder Layout

• backend/server.py - FastAPI + AG-UI endpoint + Handoff workflow
• frontend/ - Vite + React AG-UI client UI

Prerequisites

• Python 3.10+
• Node.js 18+
• npm 9+
• Azure AI project + model deployment configured in environment variables:
  • FOUNDRY_PROJECT_ENDPOINT
  • FOUNDRY_MODEL

1) Run Backend

From the Python repo root:

cd python
uv sync
uv run python samples/05-end-to-end/ag_ui_workflow_handoff/backend/server.py

Backend default URL:

• http://127.0.0.1:8891
• AG-UI endpoint: POST http://127.0.0.1:8891/handoff_demo

2) Install Frontend Packages (npm)

From the python/ directory (where Step 1 left you):

cd samples/05-end-to-end/ag_ui_workflow_handoff/frontend
npm install

3) Run Frontend Locally

npm run dev

Frontend default URL:

• http://127.0.0.1:5173

If you changed backend host/port, run with:

VITE_BACKEND_URL=http://127.0.0.1:8891 npm run dev

4) Demo Flow to Verify

1. Click one of the starter prompts (or type a refund request).
2. Refund Agent asks for an order number; reply with a numeric ID (for example: 987654).
3. If your initial request did not explicitly choose refund vs replacement, the agent asks a clarifying choice question.
4. Wait for the submit_refund reviewer interrupt (built from your provided order ID).
5. In the HITL Reviewer Console modal, click Approve Tool Call.
6. If you asked for replacement, the Order agent asks for shipping preference; reply in the chat input (for example: expedited).
7. When replacement is requested, wait for the submit_replacement reviewer interrupt and approve/reject it.
8. If you asked for refund-only, the flow should close without replacement/shipping prompts.
9. Confirm the case snapshot updates and workflow completion.

What This Validates

• add_agent_framework_fastapi_endpoint(...) with AgentFrameworkWorkflow(workflow_factory=...)
• Thread-scoped workflow state across turns
• RUN_FINISHED.interrupt pause behavior
• resume.interrupts continuation behavior
• JSON resume payload coercion for Content and list[Message] workflow response types
• Intent-driven routing between triage, refund, and order specialists (no forced linear path)
• Multiple HITL approvals in one case (submit_refund + submit_replacement)