fix: Update Conversation Agent and Truncation Strategy for Better Context #518
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
add new section
update the back link
removed extra space
feat: Add aiDeploymentsLocation parameter to Bicep deployment in deploy-KMGeneric.yml
Updated links
docs: Update links for re-use-log-analytics.md file
feat: Add Broken Link Checker workflow for Markdown files
fix: added proper path for all files
Pavan-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
brittneek
as code owners
Avijit-Microsoft
approved these changes
Jul 8, 2025
Contributor
|
🎉 This PR is included in version 3.11.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
This pull request introduces updates to improve conversational context handling and adjusts the truncation strategy for chat history. The changes aim to enhance the user experience in conversation-based interactions and ensure more relevant context is retained during streaming responses.
Improvements to conversational context handling:
src/api/agents/conversation_agent_factory.py: Updated instructions to allow the use of prior conversation history for understanding context and clarifying follow-up questions. Added guidance to respond appropriately to conversational queries like greetings or follow-ups.Adjustments to truncation strategy:
src/api/services/chat_service.py: Modified thetruncation_strategyto retain the last 4 messages instead of 2, ensuring more context is preserved during streaming responses.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation