Feature/agentchat message id field 6317 #6645
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…on guide- Fix version format from 0.4.0-dev-1 to 0.4.0-dev.1 for all packages- Remove reference to non-existent Microsoft.AutoGen.Extensions package- Add correct extension packages: Aspire, MEAI, and SemanticKernel- Fix typo: RuntimeGatewway -> RuntimeGateway- Improve documentation structure with clear section headersFixes #6244
Fix issue #6277 where TextMessage was used but not imported in three code cells of the custom agents documentation, causing NameError when users run the examples. Changes: - Add TextMessage to imports in ArithmeticAgent section - Add TextMessage to imports in GeminiAssistantAgent section - Add TextMessage to imports in Declarative GeminiAssistantAgent section The CountDownAgent section already had the correct import. Fixes #6277
Add unique id field to BaseChatMessage and BaseAgentEvent, plus full_message_id to ModelClientStreamingChunkEvent for streaming correlation. Closes #6317
|
@microsoft-github-policy-service agree |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6645 +/- ##
==========================================
+ Coverage 79.74% 79.75% +0.01%
==========================================
Files 232 232
Lines 17403 17414 +11
==========================================
+ Hits 13878 13889 +11
Misses 3525 3525
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ekzhu
approved these changes
Jun 7, 2025
|
Hello @victordibia Sir, Can you please review this PR ? |
…stallation guide- Fix version format from 0.4.0-dev-1 to 0.4.0-dev.1 for all packages- Remove reference to non-existent Microsoft.AutoGen.Extensions package- Add correct extension packages: Aspire, MEAI, and SemanticKernel- Fix typo: RuntimeGatewway -> RuntimeGateway- Improve documentation structure with clear section headersFixes #6244" This reverts commit 6d9fb2e.
…tation" This reverts commit d07898b.
ekzhu
reviewed
Jun 26, 2025
Hello @ekzhu Sir, I have implemented the feature. |
ekzhu
requested changes
Jun 27, 2025
python/packages/autogen-agentchat/src/autogen_agentchat/agents/_assistant_agent.py
Outdated
Show resolved
Hide resolved
python/packages/autogen-agentchat/src/autogen_agentchat/agents/_assistant_agent.py
Outdated
Show resolved
Hide resolved
ekzhu
requested changes
Jun 27, 2025
python/packages/autogen-agentchat/src/autogen_agentchat/agents/_assistant_agent.py
Outdated
Show resolved
Hide resolved
…chitecture, lower memory footprint, safer for concurrency
ekzhu
approved these changes
Jun 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
This PR implements unique ID fields for AgentChat messages to enable proper correlation between streaming chunks and completed messages. Currently, there's no way to correlate
ModelClientStreamingChunkEventchunks with their eventual completed message, which can lead to duplicate message display in streaming scenarios.The implementation adds:
id: strfield toBaseChatMessagewith automatic UUID generationid: strfield toBaseAgentEventwith automatic UUID generationfull_message_id: str | Nonefield toModelClientStreamingChunkEventfor chunk-to-message correlationThis allows consumers of the streaming API to avoid double-printing messages by correlating chunks with their final complete message.
Related issue number
Closes #6317
Checks