Bumps [picomatch](https://github.com/micromatch/picomatch) from 4.0.3 to 4.0.4. - [Release notes](https://github.com/micromatch/picomatch/releases) - [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md) - [Commits](https://github.com/micromatch/picomatch/compare/4.0.3...4.0.4) --- updated-dependencies: - dependency-name: picomatch dependency-version: 4.0.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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_agentrefund_agentorder_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.interruptspayloads.
The backend uses Azure OpenAI responses and supports intent-driven, non-linear handoff routing.
This demo keeps workflow state per thread_id. When the assistant ends a case with Case complete., the UI blocks
later top-level input on that same thread and asks the user to start a new case explicitly instead of resuming a
terminated workflow.
Folder Layout
backend/server.py- FastAPI + AG-UI endpoint + Handoff workflowfrontend/- 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_ENDPOINTFOUNDRY_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
- Click one of the starter prompts (or type a refund request).
- Refund Agent asks for an order number; reply with a numeric ID (for example:
987654). - If your initial request did not explicitly choose refund vs replacement, the agent asks a clarifying choice question.
- Wait for the
submit_refundreviewer interrupt (built from your provided order ID). - In the HITL Reviewer Console modal, click Approve Tool Call.
- If you asked for replacement, the Order agent asks for shipping preference; reply in the chat input (for example:
expedited). - When replacement is requested, wait for the
submit_replacementreviewer interrupt and approve/reject it. - If you asked for refund-only, the flow should close without replacement/shipping prompts.
- Confirm the case snapshot updates and workflow completion.
- After the case closes, another top-level message on the same thread is rejected with a notice.
- Click Start New Case to begin a fresh thread.
Important: require_per_service_call_history_persistence
All agents participating in a handoff workflow must be constructed with
require_per_service_call_history_persistence=True. The HandoffBuilder will
raise a ValueError at build time if any participant is missing this flag.
Why this is required: Handoff workflows use middleware that short-circuits
tool calls via MiddlewareTermination when a handoff tool is invoked. Without
per-service-call history persistence, local history providers would persist tool
results that the service never received, causing call/result mismatches on
subsequent turns.
agent = Agent(
client=client,
name="my_agent",
require_per_service_call_history_persistence=True, # Required for handoff
)
What This Validates
add_agent_framework_fastapi_endpoint(...)withAgentFrameworkWorkflow(workflow_factory=...)- Thread-scoped workflow state across turns
RUN_FINISHED.interruptpause behaviorresume.interruptscontinuation behavior- JSON resume payload coercion for
Contentandlist[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)