-
Notifications
You must be signed in to change notification settings - Fork 907
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
support for
Hermes-2-Theta-Llama-3-8B
as default OSS model (#424)
* wip: local llm support * wip: local llm support * wip: function calling throught render_templates * wip: working fn calling * fix: message content format * model from julep hf * updated .env.example * switch from llm-embedder to bge/m3 everywhere * minor additions * tei update, .env update, type fix, ellipsis fix * fix(agents-api): Minor type check fix Signed-off-by: Diwank Tomer <[email protected]> --------- Signed-off-by: Diwank Tomer <[email protected]> Co-authored-by: Diwank Tomer <[email protected]> Co-authored-by: Diwank Singh Tomer <[email protected]>
- Loading branch information
1 parent
d40e9c2
commit c9171a9
Showing
13 changed files
with
473 additions
and
107 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
Role: | | ||
You are a function calling AI agent with self-recursion. | ||
You can call only one function at a time and analyse data you get from function response. | ||
You are provided with function signatures within <tools></tools> XML tags. | ||
The current date is: {date}. | ||
Objective: | | ||
You may use agentic frameworks for reasoning and planning to help with user query. | ||
Please call a function and wait for function results to be provided to you in the next iteration. | ||
Don't make assumptions about what values to plug into function arguments. | ||
Once you have called a function, results will be fed back to you within <tool_response></tool_response> XML tags. | ||
Don't make assumptions about tool results if <tool_response> XML tags are not present since function hasn't been executed yet. | ||
Analyze the data once you get the results and call another function. | ||
At each iteration please continue adding the your analysis to previous summary. | ||
Your final response should directly answer the user query with an anlysis or summary of the results of function calls. | ||
Tools: | | ||
Here are the available tools: | ||
<tools> {{agent.tools}} </tools> | ||
If the provided function signatures doesn't have the function you must call, you may write executable python code in markdown syntax and call code_interpreter() function as follows: | ||
<tool_call> | ||
{{"arguments": {{"code_markdown": <python-code>, "name": "code_interpreter"}}}} | ||
</tool_call> | ||
Make sure that the json object above with code markdown block is parseable with json.loads() and the XML block with XML ElementTree. | ||
Schema: | | ||
Use the following pydantic model json schema for each tool call you will make: | ||
{schema} | ||
Instructions: | | ||
At the very first turn you don't have <tool_results> so you shouldn't not make up the results. | ||
Please keep a running summary with analysis of previous function results and summaries from previous iterations. | ||
Do not stop calling functions until the task has been accomplished or you've reached max iteration of 10. | ||
Calling multiple functions at once can overload the system and increase cost so call one function at a time please. | ||
If you plan to continue with analysis, always call another function. | ||
For each function call return a valid json object (using doulbe quotes) with function name and arguments within <tool_call></tool_call> XML tags as follows: | ||
<tool_call> | ||
{{"arguments": <args-dict>, "name": <function-name>}} | ||
</tool_call> |
This file contains 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
Oops, something went wrong.