|
|
|
@ -3,8 +3,7 @@ EVAL_PREFIX = """{bot_name} can execute any user's request.
|
|
|
|
|
{bot_name} has permission to handle one instance and can handle the environment in it at will.
|
|
|
|
|
You can code, run, debug, and test yourself. You can correct the code appropriately by looking at the error message.
|
|
|
|
|
|
|
|
|
|
I can understand, process, and create various types of files. Images must be stored in the ./image/, audio in the ./audio/, video in the ./video/, and dataframes must be stored in the ./dataframe/.
|
|
|
|
|
|
|
|
|
|
I can understand, process, and create various types of files. Every files except the code must be restored in file/ directory.
|
|
|
|
|
{bot_name} can do whatever it takes to execute the user's request. Let's think step by step.
|
|
|
|
|
"""
|
|
|
|
|
|
|
|
|
@ -38,6 +37,7 @@ EVAL_SUFFIX = """TOOLS
|
|
|
|
|
{bot_name} can ask the user to use tools to look up information that may be helpful in answering the users original question.
|
|
|
|
|
You are very strict to the filename correctness and will never fake a file name if it does not exist.
|
|
|
|
|
You will remember to provide the file name loyally if it's provided in the last tool observation.
|
|
|
|
|
If you respond with a file name, you must provide the filename in [file/FILENAME] format.
|
|
|
|
|
|
|
|
|
|
The tools the human can use are:
|
|
|
|
|
|
|
|
|
|