You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fef846c
Browse filesBrowse the repository at this point in the historyBrowse files
fix(devui): resolve timestamp overwriting and Content serialization errors
- Fix tool call timestamps being overwritten on each render (microsoft#1483)
- Add recursive Content serialization to handle ChatMessage and nested objects (microsoft#1548)
- Implement proper MCP tool cleanup on server shutdown
- Add timestamp field to function_result.complete events
- Enhance credential and client resource cleanup
Fixesmicrosoft#1483, microsoft#1548
Partial improvements for microsoft#1476
Copy file name to clipboardExpand all lines: python/packages/devui/README.md
+56-36Lines changed: 56 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,19 @@ devui ./agents --port 8080
49
49
50
50
When DevUI starts with no discovered entities, it displays a **sample entity gallery** with curated examples from the Agent Framework repository. You can download these samples, review them, and run them locally to get started quickly.
51
51
52
+
## Using MCP Tools
53
+
54
+
**Important:** Don't use `async with` context managers when creating agents with MCP tools for DevUI - connections will close before execution.
MCP tools use lazy initialization and connect automatically on first use. DevUI attempts to clean up connections on shutdown
64
+
52
65
## Directory Structure
53
66
54
67
For your agents to be discovered by the DevUI, they must be organized in a directory structure like below. Each agent/workflow must have an `__init__.py` that exports the required variable (`agent` or `workflow`).
@@ -157,57 +170,62 @@ Options:
157
170
158
171
Given that DevUI offers an OpenAI Responses API, it internally maps messages and events from Agent Framework to OpenAI Responses API events (in `_mapper.py`). For transparency, this mapping is shown below:
159
172
160
-
| Agent Framework Content | OpenAI Event/Type | Status |
These custom extensions are clearly namespaced and can be safely ignored by standard OpenAI clients.
228
+
These custom extensions are clearly namespaced and can be safely ignored by standard OpenAI clients. Note that DevUI also uses standard OpenAI events with custom payloads (e.g., `ExecutorActionItem` within `response.output_item.added`).
211
229
212
230
### Entity Management
213
231
@@ -239,12 +257,14 @@ These custom extensions are clearly namespaced and can be safely ignored by stan
239
257
DevUI is designed as a **sample application for local development** and should not be exposed to untrusted networks or used in production environments.
240
258
241
259
**Security features:**
260
+
242
261
- Only loads entities from local directories or in-memory registration
243
262
- No remote code execution capabilities
244
263
- Binds to localhost (127.0.0.1) by default
245
264
- All samples must be manually downloaded and reviewed before running
0 commit comments