Skip to content

Commit 127de07

Browse files
committed
docs: clarify CopilotKit AG-UI runtime guidance
1 parent cd35ecd commit 127de07

3 files changed

Lines changed: 9 additions & 8 deletions

File tree

agent-framework/integrations/ag-ui/index.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ zone_pivot_groups: programming-languages
55
author: moonbox3
66
ms.topic: overview
77
ms.author: evmattso
8-
ms.date: 11/07/2025
8+
ms.date: 06/15/2026
99
ms.service: agent-framework
1010
---
1111

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

4949
## Build agent UIs with CopilotKit
5050

51-
[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.
51+
[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.
5252

53-
CopilotKit helps you focus on your agent’s capabilities while delivering a polished user experience without reinventing the wheel.
54-
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.
53+
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.
5554

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

agent-framework/integrations/ag-ui/security-considerations.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ description: Essential security guidelines for building secure AG-UI application
44
author: moonbox3
55
ms.topic: reference
66
ms.author: evmattso
7-
ms.date: 11/11/2025
7+
ms.date: 06/15/2026
88
ms.service: agent-framework
99
---
1010

1111
# Security Considerations for AG-UI
1212

13-
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.
13+
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.
1414

1515
## Overview
1616

@@ -100,6 +100,8 @@ When using a trusted frontend server, the security model changes significantly:
100100
> [!TIP]
101101
> 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.
102102
103+
When using a runtime or proxy 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.
104+
103105
## Input Validation and Sanitization
104106

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

149151
## Authentication and Authorization
150152

151-
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.
153+
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.
152154

153155
### Session ID Management
154156

agent-framework/integrations/ag-ui/testing-with-dojo.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Before you begin, ensure you have:
3131
First, clone the AG-UI repository which contains the Dojo application and Microsoft Agent Framework integration examples:
3232

3333
```bash
34-
git clone https://github.com/ag-oss/ag-ui.git
34+
git clone https://github.com/ag-ui-protocol/ag-ui.git
3535
cd ag-ui
3636
```
3737

0 commit comments

Comments
 (0)