Message truncator hook to manage tokens #332
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
Test Results93 tests 93 ✅ 2s ⏱️ Results for commit 8258f24. |
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
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.
Description
This is imp for smooth functioning of the chatbot.
In case a tool message returns a very large response, the agent is not able to reply.
For example, if you change the profile video to any other video and then ask chatbot any prompt which triggers the get_dashboard or any other related profile video tool, the Tool Msg has very long URL of video which exceeds the limit of model, thus encountring error that point onwards.
This PR solves that by smarly reducing length to a max limit w/o mch loss of info
Testing
Please describe the tests that you ran to verify your changes. Please summarize what did you test and what needs to be tested e.g. deployed and tested the service locally.
Documentation
Make sure that you have documented corresponding changes in this repository.
Checklist: