mirror of
https://github.com/microsoft/agent-framework.git
synced 2026-06-16 21:04:09 +08:00
15a11a426a
* Python: add ag-ui tool result display channel Key decisions: - Add TOOL_RESULT_DISPLAY_KEY and make state_update accept optional state plus a tool_result display payload. - Keep text as the LLM-bound tool result while using the display marker only for ToolCallResultEvent.content. - Reuse one outer/inner Content additional_properties extraction helper for state and display markers, preserving fallback behavior when display is absent. Files changed: - python/packages/ag-ui/agent_framework_ag_ui/_state.py - python/packages/ag-ui/agent_framework_ag_ui/_run_common.py - python/packages/ag-ui/tests/ag_ui/test_run_common.py - python/packages/ag-ui/tests/ag_ui/golden/test_scenario_deterministic_state.py - python/issues/done/01-tool-result-display-channel.md Blockers/notes: - Slice 1 is complete and moved to issues/done. - Slice 2 remains for docstring and README documentation. * Python: document ag-ui tool result display channel Key decisions: - Document state_update as the single helper for LLM text, UI-only tool_result display content, and durable shared state. - Keep the display guidance explicit that text remains LLM-bound while tool_result feeds ToolCallResultEvent.content. - List both reserved additional_properties markers in the docstring return contract. Files changed: - python/packages/ag-ui/agent_framework_ag_ui/_state.py - python/packages/ag-ui/README.md - python/issues/done/02-docs-tool-result-display.md Blockers/notes: - Slice 2 is complete and moved to issues/done. - Verification passed: uv run poe syntax -P ag-ui --check; uv run poe test -P ag-ui; uv run poe markdown-code-lint; uv run ruff check packages/ag-ui/agent_framework_ag_ui/_state.py. - Commit hooks were skipped after poe-check repeatedly rewrote uv.lock ordering; the same checks were run manually and passed. * Python: update gitignore
220 lines
7.9 KiB
Markdown
220 lines
7.9 KiB
Markdown
# Agent Framework AG-UI Integration
|
|
|
|
AG-UI protocol integration for Agent Framework, enabling seamless integration with AG-UI's web interface and streaming protocol.
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
pip install agent-framework-ag-ui
|
|
```
|
|
|
|
## Quick Start
|
|
|
|
### Server (Host an AI Agent)
|
|
|
|
```python
|
|
from fastapi import FastAPI
|
|
from agent_framework import Agent
|
|
from agent_framework.openai import OpenAIChatCompletionClient
|
|
from agent_framework.ag_ui import add_agent_framework_fastapi_endpoint
|
|
|
|
# Create your agent
|
|
agent = Agent(
|
|
name="my_agent",
|
|
instructions="You are a helpful assistant.",
|
|
client=OpenAIChatCompletionClient(
|
|
azure_endpoint="https://your-resource.openai.azure.com/",
|
|
model="gpt-4o-mini",
|
|
api_key="your-api-key",
|
|
),
|
|
)
|
|
|
|
# Create FastAPI app and add AG-UI endpoint
|
|
app = FastAPI()
|
|
add_agent_framework_fastapi_endpoint(app, agent, "/")
|
|
|
|
# Run with: uvicorn main:app --reload
|
|
```
|
|
|
|
### Server (Host a Workflow)
|
|
|
|
```python
|
|
from fastapi import FastAPI
|
|
from agent_framework import WorkflowBuilder, WorkflowContext, executor
|
|
from agent_framework.ag_ui import add_agent_framework_fastapi_endpoint
|
|
|
|
@executor(id="start")
|
|
async def start(message: str, ctx: WorkflowContext) -> None:
|
|
await ctx.yield_output(f"Workflow received: {message}")
|
|
|
|
workflow = WorkflowBuilder(start_executor=start).build()
|
|
|
|
app = FastAPI()
|
|
add_agent_framework_fastapi_endpoint(app, workflow, "/")
|
|
```
|
|
|
|
### Server (Thread-Scoped WorkflowBuilder)
|
|
|
|
Use `workflow_factory` when your workflow keeps runtime state (for example pending `request_info` interrupts) and must be isolated per AG-UI thread:
|
|
|
|
```python
|
|
from fastapi import FastAPI
|
|
from agent_framework import Workflow, WorkflowBuilder
|
|
from agent_framework.ag_ui import AgentFrameworkWorkflow, add_agent_framework_fastapi_endpoint
|
|
|
|
def build_workflow_for_thread(thread_id: str) -> Workflow:
|
|
# Build a fresh workflow instance for each thread id.
|
|
return WorkflowBuilder(start_executor=...).build()
|
|
|
|
app = FastAPI()
|
|
thread_scoped_workflow = AgentFrameworkWorkflow(
|
|
workflow_factory=build_workflow_for_thread,
|
|
name="my_workflow",
|
|
)
|
|
add_agent_framework_fastapi_endpoint(app, thread_scoped_workflow, "/")
|
|
```
|
|
|
|
### Client (Connect to an AG-UI Server)
|
|
|
|
```python
|
|
import asyncio
|
|
from agent_framework.ag_ui import AGUIChatClient
|
|
|
|
async def main():
|
|
async with AGUIChatClient(endpoint="http://localhost:8000/") as client:
|
|
# Stream responses
|
|
async for update in client.get_response("Hello!", stream=True):
|
|
for content in update.contents:
|
|
if content.type == "text" and content.text:
|
|
print(content.text, end="", flush=True)
|
|
print()
|
|
|
|
asyncio.run(main())
|
|
```
|
|
|
|
The `AGUIChatClient` supports:
|
|
- Streaming and non-streaming responses
|
|
- Hybrid tool execution (client-side + server-side tools)
|
|
- Automatic thread management for conversation continuity
|
|
- Integration with `Agent` for client-side history management
|
|
- Interrupt metadata passthrough (`availableInterrupts` and `resume`)
|
|
|
|
## Tool Return Helpers
|
|
|
|
Use `state_update` when a backend tool needs to send different payloads to the model, the UI, and shared state. The `text` value remains the LLM-bound tool result, `tool_result` becomes the AG-UI `ToolCallResultEvent.content` for frontend rendering, and `state` is merged into durable shared state.
|
|
|
|
```python
|
|
from agent_framework import Content, tool
|
|
from agent_framework.ag_ui import state_update
|
|
|
|
@tool
|
|
async def get_weather(city: str) -> Content:
|
|
data = await fetch_weather(city)
|
|
return state_update(
|
|
text=f"{city}: {data['temp']}°C and {data['conditions']}",
|
|
tool_result={
|
|
"component": "weather-card",
|
|
"city": city,
|
|
"temperature": data["temp"],
|
|
"conditions": data["conditions"],
|
|
"humidity": data["humidity"],
|
|
},
|
|
state={"weather": {"city": city, **data}},
|
|
)
|
|
```
|
|
|
|
## Documentation
|
|
|
|
- **[Getting Started Tutorial](getting_started/)** - Step-by-step guide to building AG-UI servers and clients
|
|
- Server setup with FastAPI
|
|
- Client examples using `AGUIChatClient`
|
|
- Hybrid tool execution (client-side + server-side)
|
|
- Thread management and conversation continuity
|
|
- **[Examples](agent_framework_ag_ui_examples/)** - Complete examples for AG-UI features
|
|
|
|
## Features
|
|
|
|
This integration supports all 7 AG-UI features:
|
|
|
|
1. **Agentic Chat**: Basic streaming chat with tool calling support
|
|
2. **Backend Tool Rendering**: Tools executed on backend with results streamed to client
|
|
3. **Human in the Loop**: Function approval requests for user confirmation before tool execution
|
|
4. **Agentic Generative UI**: Async tools for long-running operations with progress updates
|
|
5. **Tool-based Generative UI**: Custom UI components rendered on frontend based on tool calls
|
|
6. **Shared State**: Bidirectional state sync between client and server
|
|
7. **Predictive State Updates**: Stream tool arguments as optimistic state updates during execution
|
|
|
|
Additional compatibility and draft support:
|
|
- Native `Workflow` endpoint registration via `add_agent_framework_fastapi_endpoint(...)`
|
|
- Workflow-to-AG-UI event mapping (run/step/activity/tool/custom events)
|
|
- Custom event compatibility for inbound `CUSTOM`, `CUSTOM_EVENT`, and `custom_event`
|
|
- Pragmatic multimodal input parsing for both legacy (`binary`) and draft media-part shapes
|
|
- Pragmatic interrupt/resume handling (`availableInterrupts`, `resume`, and `RUN_FINISHED.interrupt`)
|
|
|
|
## Security: Authentication & Authorization
|
|
|
|
The AG-UI endpoint does not enforce authentication by default. **For production deployments, you should add authentication** using FastAPI's dependency injection system via the `dependencies` parameter.
|
|
|
|
### API Key Authentication Example
|
|
|
|
```python
|
|
import os
|
|
from fastapi import Depends, FastAPI, HTTPException, Security
|
|
from fastapi.security import APIKeyHeader
|
|
from agent_framework import Agent
|
|
from agent_framework.ag_ui import add_agent_framework_fastapi_endpoint
|
|
|
|
# Configure API key authentication
|
|
API_KEY_HEADER = APIKeyHeader(name="X-API-Key", auto_error=False)
|
|
EXPECTED_API_KEY = os.environ.get("AG_UI_API_KEY")
|
|
|
|
async def verify_api_key(api_key: str | None = Security(API_KEY_HEADER)) -> None:
|
|
"""Verify the API key provided in the request header."""
|
|
if not api_key or api_key != EXPECTED_API_KEY:
|
|
raise HTTPException(status_code=401, detail="Invalid or missing API key")
|
|
|
|
# Create agent and app
|
|
agent = Agent(name="my_agent", instructions="...", client=...)
|
|
app = FastAPI()
|
|
|
|
# Register endpoint WITH authentication
|
|
add_agent_framework_fastapi_endpoint(
|
|
app,
|
|
agent,
|
|
"/",
|
|
dependencies=[Depends(verify_api_key)], # Authentication enforced here
|
|
)
|
|
```
|
|
|
|
### Other Authentication Options
|
|
|
|
The `dependencies` parameter accepts any FastAPI dependency, enabling integration with:
|
|
|
|
- **OAuth 2.0 / OpenID Connect** - Use `fastapi.security.OAuth2PasswordBearer`
|
|
- **JWT Tokens** - Validate tokens with libraries like `python-jose`
|
|
- **Azure AD / Entra ID** - Use `azure-identity` for Microsoft identity platform
|
|
- **Rate Limiting** - Add request throttling dependencies
|
|
- **Custom Authentication** - Implement your organization's auth requirements
|
|
|
|
For a complete authentication example, see [getting_started/server.py](getting_started/server.py).
|
|
|
|
## Architecture
|
|
|
|
The package uses a clean, orchestrator-based architecture:
|
|
|
|
- **AgentFrameworkAgent**: Lightweight wrapper that delegates to orchestrators
|
|
- **Orchestrators**: Handle different execution flows (default, human-in-the-loop, etc.)
|
|
- **Confirmation Strategies**: Domain-specific confirmation messages (extensible)
|
|
- **AgentFrameworkEventBridge**: Converts Agent Framework events to AG-UI events
|
|
- **Message Adapters**: Bidirectional conversion between AG-UI and Agent Framework message formats
|
|
- **FastAPI Endpoint**: Streaming HTTP endpoint with Server-Sent Events (SSE)
|
|
|
|
## Next Steps
|
|
|
|
1. **New to AG-UI?** Start with the [Getting Started Tutorial](getting_started/)
|
|
2. **Want to see examples?** Check out the [Examples](agent_framework_ag_ui_examples/) for AG-UI features
|
|
|
|
## License
|
|
|
|
MIT
|