Conversation
Move provider specific logic into prepare_args method mostly. The only exceptions are OpenAI because it uses completely different method to call the API and TestMock which doesn't require most of the things.
Change the LLM call API to pass the list of tools to call and receive the list of tool calls. Adapt loop.metta to this change. Fix unit tests.
The historical information is still returned via HISTORY paragraph of the system prompt.
vsbogd
marked this pull request as ready for review
September 23, 2026 09:03
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR is part of #349 which doesn't include loop and memory changes. It delivers the most massive code change: using tools API to get the list of tool calls from LLM. It obsoletes
helper.balance_parenthesisfunction.How Has This Been Tested?
This PR doesn't introduce any code logic change just migrates existing logic to the new API. Regression testing should be enough. This PR is checked using automatic regression testing and manual smoke check with each provider.
Checklist