Skip to content

Clarify CopilotKit AG-UI guidance #416

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
samjulien wants to merge 1 commit into
base: main
Choose a base branch
from
+9 −8
Open

Clarify CopilotKit AG-UI guidance #416

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions agent-framework/integrations/ag-ui/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ zone_pivot_groups: programming-languages
author: moonbox3
ms.topic: overview
ms.author: evmattso
ms.date: 11/07/2025
ms.date: 06/15/2026
ms.service: agent-framework
---

Expand Down Expand Up @@ -48,10 +48,9 @@ The Agent Framework AG-UI integration supports all 7 AG-UI protocol features:

## Build agent UIs with CopilotKit

[CopilotKit](https://copilotkit.ai/) provides rich UI components for building agent user interfaces based on the standard AG-UI protocol. CopilotKit supports streaming chat interfaces, frontend & backend tool calling, human-in-the-loop interactions, generative UI, shared state, and much more. You can see a examples of the various agent UI scenarios that CopilotKit supports in the [AG-UI Dojo](https://dojo.ag-ui.com/microsoft-agent-framework-dotnet) sample application.
[CopilotKit](https://copilotkit.ai/) provides rich UI components and headless UI primitives for building agent user interfaces based on the standard AG-UI protocol, so you can ship quickly with prebuilt chat experiences or fully customize the interface for your application. CopilotKit supports streaming chat interfaces, frontend and backend tool calling, human-in-the-loop interactions, generative UI, shared state, and much more. You can see examples of the various agent UI scenarios that CopilotKit supports in the [AG-UI Dojo](https://dojo.ag-ui.com/microsoft-agent-framework-dotnet) sample application.

CopilotKit helps you focus on your agent’s capabilities while delivering a polished user experience without reinventing the wheel.
To learn more about getting started with Microsoft Agent Framework and CopilotKit, see the [Microsoft Agent Framework integration for CopilotKit](https://docs.copilotkit.ai/microsoft-agent-framework) documentation.
CopilotKit helps you focus on your agent's capabilities while delivering a polished user experience without reinventing the wheel. To learn more about getting started with Microsoft Agent Framework and CopilotKit, see the [Microsoft Agent Framework integration for CopilotKit](https://docs.copilotkit.ai/microsoft-agent-framework) documentation.

::: zone pivot="programming-language-csharp"

Expand Down
8 changes: 5 additions & 3 deletions agent-framework/integrations/ag-ui/security-considerations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,13 @@ description: Essential security guidelines for building secure AG-UI application
author: moonbox3
ms.topic: reference
ms.author: evmattso
ms.date: 11/11/2025
ms.date: 06/15/2026
ms.service: agent-framework
---

# Security Considerations for AG-UI

AG-UI enables powerful real-time interactions between clients and AI agents. This bidirectional communication requires some security considerations. The following document covers essential security practices for building securing your agents exposed through AG-UI.
AG-UI enables powerful real-time interactions between clients and AI agents. This bidirectional communication requires some security considerations. The following document covers essential security practices for securing your agents exposed through AG-UI.

## Overview

Expand Down Expand Up @@ -100,6 +100,8 @@ When using a trusted frontend server, the security model changes significantly:
> [!TIP]
> The trusted frontend server pattern significantly reduces attack surface by ensuring that only user message **content** comes from untrusted sources, while all other protocol elements (message structure, roles, tools, state, context) are controlled by trusted code.

When using a proxy or trusted server layer, keep authorization decisions in that trusted layer. For example, decide which tools, state fields, context values, and forwarded properties a user can send before constructing the AG-UI request to the server.

## Input Validation and Sanitization

### Message Content Validation
Expand Down Expand Up @@ -148,7 +150,7 @@ Forwarded properties contain arbitrary JSON that passes through the system. Trea

## Authentication and Authorization

AG-UI does not include built-in authorization mechanism. It is up to your application to prevent unauthorized use of the exposed AG-UI endpoint.
AG-UI does not include a built-in authorization mechanism. It is up to your application to prevent unauthorized use of the exposed AG-UI endpoint.

### Session ID Management

Expand Down
2 changes: 1 addition & 1 deletion agent-framework/integrations/ag-ui/testing-with-dojo.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Before you begin, ensure you have:
First, clone the AG-UI repository which contains the Dojo application and Microsoft Agent Framework integration examples:

```bash
git clone https://github.com/ag-oss/ag-ui.git
git clone https://github.com/ag-ui-protocol/ag-ui.git
cd ag-ui
```

Expand Down