-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle empty memory type in agent configuration #1745
Handle empty memory type in agent configuration #1745
Conversation
Signed-off-by: Arjun kumar Giri <[email protected]>
4a6112e
to
f998c9f
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## feature/agent_framework_dev #1745 +/- ##
=================================================================
- Coverage 68.95% 68.92% -0.03%
Complexity 2611 2611
=================================================================
Files 241 241
Lines 12880 12882 +2
Branches 1291 1292 +1
=================================================================
- Hits 8881 8879 -2
- Misses 3393 3395 +2
- Partials 606 608 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Can you also test multiple tools use case? |
Updated PR description with testing details using multiple tools. |
Thanks. Question not related to this bug fix: for multi-tool use case, we will return response of each tool? I think we should keep it same with chat agent, which outputs the final answer as response, but user can add the tool response to additional info. |
Agreed. We will need to finalize on agent execution response schema. Will move Tool output of flow agent to |
85aaf14
into
opensearch-project:feature/agent_framework_dev
Description
Handle empty memory type in flow agent configuration. Note that conversational agent still requires memory type to be defined.
Test agent configuration
Test request
Response
Issues Resolved
[List any issues this PR will resolve]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.