Case: 20260502T045705Z__gptme__local_qwen3_8b__ollama__tool__shell_date
PASS Trajectory: recovered | Invoked: yes | Match: 100%
gptme --non-interactive --no-confirm --name gptme__local_qwen3_8b__ollama__tool__shell_date-warmup --system short --workspace /work/results/runs/20260502T045705Z/cases/gptme__local_qwen3_8b__ollama__tool__shell_date/workspace-warmup --tools shell --tool-format tool -m local/qwen3:8b 'Use the shell tool. Run exactly this command: date +%F > date-output.txt. Do not retry on error. If the command fails, reply only with FAIL. If the command succeeds, reply only with DONE. '
gptme --non-interactive --no-confirm --name gptme__local_qwen3_8b__ollama__tool__shell_date-measured --system short --workspace /work/results/runs/20260502T045705Z/cases/gptme__local_qwen3_8b__ollama__tool__shell_date/workspace --tools shell --tool-format tool -m local/qwen3:8b 'Use the shell tool. Run exactly this command: date +%F > date-output.txt. Do not retry on error. If the command fails, reply only with FAIL. If the command succeeds, reply only with DONE. '
Consistency: diverged
Use the shell tool. Run exactly this command: date +%F > date-output.txt. Do not retry on error. If the command fails, reply only with FAIL. If the command succeeds, reply only with DONE.
2026-05-02
2026-05-02
Expected and observed match.
No structured session transcript found.
[gripprobe] process_started_at=2026-05-02T05:01:28+00:00
[05:01:30] Created config file at /work/results/runs/20260502T045705Z/cases/gptme__local_qwen3_8b__ollama__tool__shell_date/runtime/gptme/warmup/home/.config/gptme/config.toml
[05:01:31] WARNING Skipping all confirmation prompts. cli.py:265
[05:01:31] Using model: local/qwen3:8b
Using logdir: /work/results/runs/20260502T045705Z/cases/gptme__local_qwen3_8b__ollama__tool__shell_date/runtime/gptme/warmup/state/gptme-logs/gptme__local_qwen3_8b__ollama__tool__shell_date-warmup
Using workspace: /work/results/runs/20260502T045705Z/cases/gptme__local_qwen3_8b__ollama__tool__shell_date/workspace-warmup
Skipped 2 hidden system messages, show with --show-hidden
--- ^^^ past messages ^^^ ---
User:
Use the shell tool. Run exactly this command: date +%F > date-output.txt.
Do not retry on error.
If the command fails, reply only with FAIL.
If the command succeeds, reply only with DONE.
Assistant: Thinking...
Assistant:
<think>
<think>
Okay, the user wants me to use the shell tool to run the command 'date +%F > date-output.txt'. Let me make sure I understand what this command does. The 'date' command with the format '%F' will output the current date in YYYY-MM-DD format. Then, the output is redirected to a file called date-output.txt.
First, I need to check if the shell tool is available. According to the tools provided, the shell function is there, and it can execute commands. The user specified not to retry on error, so I should execute the command once and then check the result.
I should construct the tool call with the shell function and the command as an argument. The command is exactly 'date +%F > date-output.txt'. I need to make sure that the arguments are correctly formatted as a JSON object with the command key.
Wait, the function signature for shell has an argument that's a command string. So the arguments should be {"command": "date +%F > date-output.txt"}.
I don't need to handle any background jobs here because the command is simple and won't run indefinitely. The user also mentioned to reply only with FAIL or DONE based on the command's success. So after executing, I'll get the output, and if there's no error, respond with DONE. If there's an error, like permission issues or the command not found, then reply with FAIL. But since the command is straightforward, it's likely to succeed. Let me proceed with the tool call.
</think>
</think>
@shell(call_vlo70fz4): {"command":"date +%F \u003e date-output.txt"}
Preview
date +%F > date-output.txt
System:
Ran command: `date +%F > date-output.txt`
No output
Assistant: Thinking...
[05:01:43] ERROR exception during auto-name auto_naming.py:100
Traceback (most recent call last):
File "/opt/venvs/gptme/lib/python3.12/site-packages/gptme/util/auto_naming.py", line 97, in _generate_llm_name
summary_model_name = get_summary_model(current_model.provider)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/venvs/gptme/lib/python3.12/site-packages/gptme/llm/models.py", line 576, in get_summary_model
raise ValueError(f"Provider {provider} did not have a summary model")
ValueError: Provider local did not have a summary model
[05:02:06] INFO Reasoning content: Okay, the user wants a concise title for this conversation. Let me see. The main task is running a specific shell command to output the date. The examples given are things like "Python debugging help" or "API llm_openai.py:321
integration guide". So I need to capture the main action here.
The command is 'date +%F > date-output.txt'. The user is instructing to use the shell tool and run that exact command. The key points here are using the shell, executing the command, and possibly handling the output. But the examples
don't mention output handling, so maybe focus on the main action.
The examples have titles like "Website creation task" which is about the task. Here, the task is running the command. So maybe "Shell command task" or "Run date command". But the examples have "Python debugging help" which is more about
the problem. Wait, the user's instruction is to run the command, and the assistant's response is either FAIL or DONE. So the main topic is executing that specific command.
Looking at the examples again, "CSS layout issue" is about a problem. But in this case, the user isn't asking for help with an issue; they're giving a task. So maybe "Shell command task" or "Run date command". But the examples have titles
that are more about the action. Let me check the examples again.
The examples include "Python debugging help" (problem), "Website creation task" (task), "CSS layout issue" (problem), "API integration guide" (guide). So for a task, "Website creation task" is similar. Here, the task is to run the
command. So maybe "Shell command task" or "Run date command". But the user's instruction is to use the shell tool and run the command. The main topic is executing that command.
Alternatively, since the command is about getting the date, maybe "Date command task". But the examples don't have that. Wait, the user's command is to run a specific command, so the title should reflect that. The examples have "Python
debugging help" which is a problem, but here it's a task. So "Shell command task" is possible. But maybe "Run date command" is more specific. However, the examples have "Website creation task" which is similar. So maybe "Shell command
task" is better. But the user's command is about writing the date to a file. Maybe "Date output task"? Hmm.
Wait, the user's instruction is to run the command exactly as given. The main topic is executing that command. So the title should be something like "Run date command" or "Shell command task". But the examples have "Website creation task"
which is similar. So "Shell command task" fits. Alternatively, "Date command task". But maybe "Shell command" is sufficient. Wait, the examples have "Python debugging help" which is 3 words. The user's title needs to be 2-4 words. So
"Shell command task" is 3 words. Alternatively, "Run date command" is 3 words. Which one is better? The user's command is about using the shell to run the date command. So "Shell command" might be too vague. "Run date command" is more
specific. But the examples have "Website creation task" which is a task. So maybe "Shell command task" is better. Alternatively, "Date command task".
Wait, the user's instruction is to use the shell tool and run the command. The main action is running the command. So "Run date command" captures that. But the examples have "Python debugging help" which is a problem. Here, it's a task.
So "Shell command task" or "Run date command". Which is more concise? "Run date command" is 3 words. "Shell command task" is also 3. Which one is better? The user's command is about writing the date to a file, but the title should capture
the main topic. The main topic is executing the command. So "Run date command" is more specific. Alternatively, "Date command task". But maybe "Shell command" is enough. Wait, the examples have "Website creation task" which is 3 words. So
"Shell command task" is similar. But the user's command is about the date. Maybe "Date command task".
Alternatively, since the command is to write the date to a file, maybe "Date output task". But the examples don't have that. The user's instruction is to run the command, so the title should reflect that. So "Run date command" is better.
But the user's command is part of a task where they might be testing if the command works. So maybe "Shell command task" is better.
Hmm, I think "Shell command task" is the best fit here. It's concise, captures the main action of running a shell command, and follows the example structure. So the title would be "Shell command task".
INFO Auto-generated conversation name: Shell command task chat.py:332
Assistant:
<think>
<think>
Okay, let's see. The user asked to run the command `date +%F > date-output.txt` using the shell tool. The response from the tool says "Ran command" and mentions there's no output.
First, I need to determine if the command succeeded or failed. The command's purpose is to write the current date in YYYY-MM-DD format to a file called date-output.txt. If there's no output, that might mean the command executed without errors, but the output was redirected to the file. However, sometimes if there's an error, the shell might not show output, but the command could still fail.
Wait, the user specified to reply only with FAIL if the command fails, otherwise DONE. Since the tool's response says "No output," it's possible that the command ran successfully and the output was written to the file. But maybe there's an error in redirecting the output. For example, if the file can't be written to, the command might fail silently. However, the user said not to retry on error, so we have to go with the first attempt.
Alternatively, maybe the command executed successfully, and the output was written to the file, hence no output in the shell. In that case, the correct response would be DONE. But I need to check if the file was created. However, the user's tool response doesn't mention any error, so perhaps the command succeeded. Therefore, the answer should be DONE.
</think>
</think>
DONE
[05:02:14] INFO Auto-reply: Assistant message had no tools. Asking for confirmation... complete.py:138
[05:02:14] [Loop control] <system>No tool call detected in last message. Did you mean to finish? If so, make sure you are comp...
User: <system>No tool call detected in last message. Did you mean to finish? If so, make sure you are completely done and then use the `complete` tool to end the session.</system>
Assistant: Thinking...
Assistant:
<think>
<think>
Okay, let me see. The user asked to run the command `date +%F > date-output.txt` using the shell tool. I called the shell function with that command. The response from the tool said the command ran with no output. Since the command is straightforward and doesn't produce any output by default, the absence of output might just mean it worked as expected. The user also mentioned not to retry on error, so if there was an error, I should reply with FAIL. But since there's no output, maybe it's successful. However, the user wants only DONE if successful. But wait, maybe the command failed silently. How can I check?
Wait, the user's instruction says if the command fails, reply only with FAIL. If it succeeds, reply with DONE. Since the tool's response says "No output," perhaps the command executed without errors. The date command usually outputs the current date, so redirecting it to a file should work. Unless there's a permission issue or the file can't be written. But the user didn't mention any error. The tool's response didn't show any error messages. So maybe it's successful. Therefore, the correct response is DONE. But the system message says to use the complete tool if done. Wait, the user's last message was a system message indicating no tool call was detected. The assistant's previous response was DONE, which is a reply, not a tool call. So maybe the assistant should have used the complete tool to end the session. But the user's instructions said if the command succeeds, reply only with DONE. So perhaps the assistant should have replied with DONE and then used the complete tool. But in the previous interaction, the assistant replied with DONE, and the system message is prompting to finish with the complete tool. So maybe the correct step now is to use the complete tool to end the session.
</think>
</think>
[05:02:23] INFO Auto-reply: Assistant message had no tools. Asking for confirmation... complete.py:138
[05:02:23] [Loop control] <system>No tool call detected in last message. Did you mean to finish? If so, make sure you are comp...
User: <system>No tool call detected in last message. Did you mean to finish? If so, make sure you are completely done and then use the `complete` tool to end the session.</system>
Assistant: Thinking...
Assistant:
<think>
<think>
Okay, let me see. The user asked to run the command `date +%F > date-output.txt` using the shell tool. I called the shell function with that command. The response said the command ran with no output. Then the user's last message was a system note saying no tool call was detected and asking if I meant to finish.
Hmm, since the command executed successfully and there's no error, the correct response should be "DONE". But the system message is prompting me to use the `complete` tool if I'm done. Wait, maybe I should check if the command actually worked. The command writes the current date to date-output.txt. If the file was created and has the correct date, then it's successful. Since there was no output from the command, it's likely successful. The user might expect me to confirm completion. But according to the instructions, if successful, reply with "DONE". However, the system is now asking if I meant to finish, so perhaps I should use the `complete` tool now. But the user said not to retry on error and to reply with FAIL or DONE. Since the command succeeded, DONE is correct. But the system is indicating that no tool call was made, so maybe I should use complete. Wait, the user's last message was a system message, not a new command. So maybe the correct action is to reply with DONE as per the earlier instruction. But the system is now asking if I meant to finish. I'm a bit confused. Let me recheck the initial instructions. The user said if the command succeeds, reply only with DONE. Since the command ran without output, it's successful. So the correct response is DONE. But the system is prompting to use complete. Maybe the user wants to end the session. But according to the problem, after the shell command, if successful, reply with DONE. So I should respond with DONE.
</think>
</think>
DONE
[05:02:33] INFO Autonomous mode: No tools used after 2 confirmations. Exiting. complete.py:134
INFO Hook 'complete.auto_reply' signaled session completion __init__.py:360
[05:02:33] Autonomous mode: No tools used after 2 auto-reply confirmations. Exiting.
Goodbye! (resume with: gptme --name gptme__local_qwen3_8b__ollama__tool__shell_date-warmup)
[gripprobe] process_finished_at=2026-05-02T05:02:33+00:00 exit_code=0
[gripprobe] process_started_at=2026-05-02T05:01:28+00:00 [gripprobe] process_finished_at=2026-05-02T05:02:33+00:00 exit_code=0
[gripprobe] process_started_at=2026-05-02T05:02:33+00:00
[05:02:35] Created config file at /work/results/runs/20260502T045705Z/cases/gptme__local_qwen3_8b__ollama__tool__shell_date/runtime/gptme/measured/home/.config/gptme/config.toml
[05:02:35] WARNING Skipping all confirmation prompts. cli.py:265
Using model: local/qwen3:8b
Using logdir: /work/results/runs/20260502T045705Z/cases/gptme__local_qwen3_8b__ollama__tool__shell_date/runtime/gptme/measured/state/gptme-logs/gptme__local_qwen3_8b__ollama__tool__shell_date-measured
Using workspace: /work/results/runs/20260502T045705Z/cases/gptme__local_qwen3_8b__ollama__tool__shell_date/workspace
Skipped 2 hidden system messages, show with --show-hidden
--- ^^^ past messages ^^^ ---
User:
Use the shell tool. Run exactly this command: date +%F > date-output.txt.
Do not retry on error.
If the command fails, reply only with FAIL.
If the command succeeds, reply only with DONE.
Assistant: Thinking...
Assistant:
<think>
<think>
Okay, I need to use the shell tool to run the command 'date +%F > date-output.txt'. Let me make sure I understand what this command does. The 'date' command with the format '%F' will output the current date in YYYY-MM-DD format. Then, the output is redirected to a file named date-output.txt.
I should check if the shell tool is available. From the tools list, the shell function is present, so I can use it. The user specified not to retry on error, so I need to execute this command once. If there's an error, like permission issues or the command not being found, I should reply with FAIL. If it works, reply with DONE.
Wait, the command is straightforward. The 'date' command is standard, so it should be available. The redirection should create the file if it doesn't exist or overwrite it if it does. Let me make sure there are no typos in the command. The format is correct, and the redirection is properly syntaxed.
I'll proceed to call the shell function with this command. Let me structure the tool call correctly. The function name is 'shell', and the argument is the command as a string. No other parameters are needed. The user wants exactly this command to be executed.
I should not add any additional steps or explanations. Just execute the command and check the result. If the shell tool's response indicates success, then reply with DONE. If there's an error message, reply with FAIL. Since the user mentioned not to retry, I need to handle it in one go.
</think>
</think>
@shell(call_19j5cezp): {"command":"date +%F \u003e date-output.txt"}
Preview
date +%F > date-output.txt
System:
Ran command: `date +%F > date-output.txt`
No output
[05:02:48] ERROR exception during auto-name auto_naming.py:100
Traceback (most recent call last):
File "/opt/venvs/gptme/lib/python3.12/site-packages/gptme/util/auto_naming.py", line 97, in _generate_llm_name
summary_model_name = get_summary_model(current_model.provider)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/venvs/gptme/lib/python3.12/site-packages/gptme/llm/models.py", line 576, in get_summary_model
raise ValueError(f"Provider {provider} did not have a summary model")
ValueError: Provider local did not have a summary model
Assistant: Thinking...
[05:02:58] INFO Reasoning content: Okay, the user wants a concise title for a conversation where they're using a shell command to write the current date to a file. The examples given are all about specific tasks like Python debugging, website creation, llm_openai.py:321
etc. So I need to capture the main action here.
The command is 'date +%F > date-output.txt'. The key elements here are using the shell, running a command, and possibly handling output. The user mentioned using the shell tool and running the exact command. The assistant's response is
either FAIL or DONE based on success or failure.
So the main topic is executing a shell command to output the date. The title should be 2-4 words. Let me think of possible titles. "Shell command run" is 3 words. "Date output command" is 3 words. "Shell date output" is 3 words. "Command
execution" is 2 words but maybe too generic. "Shell command task" is 3 words.
Wait, the user's instruction is to run the command exactly as given. The assistant's role is to execute it and respond with FAIL or DONE. So the main topic is about running a specific shell command. Maybe "Shell command run" or "Date
command output". Alternatively, "Shell date command" could work. But the examples have things like "Python debugging help" which is more specific.
The user's command is about writing the date to a file, but the main action is running the shell command. So maybe "Shell command run" is the best fit. It's concise and captures the main topic without extra details. Let me check the
examples again. The examples are all about the task, like "Website creation task" or "CSS layout issue". So maybe "Shell command task" or "Shell command run".
Alternatively, since the command is about outputting the date, maybe "Date output command". But the user's main action is using the shell tool to run the command. So "Shell command run" seems appropriate. Let me confirm the word count.
"Shell command run" is three words, which fits the 2-4 word rule. That should be it.
INFO Auto-generated conversation name: Shell command run chat.py:332
Assistant:
<think>
<think>
Okay, let me see. The user asked to run the command `date +%F > date-output.txt` using the shell tool. The response from the tool says "Ran command" and mentions there's no output.
Hmm, the command itself is straightforward. The `date` command with the `%F` format should output the current date in YYYY-MM-DD format. Then, it's redirected to a file called `date-output.txt`. If the command ran without errors, the file should be created with the date.
But the tool's response says there's no output. Wait, maybe the command executed successfully but the output wasn't captured because it's redirected to a file. The user might expect a confirmation that the file was created or that the command ran without issues. However, the shell tool's response doesn't show any error messages, so perhaps the command worked as intended.
The user's instructions were to reply with "DONE" if successful or "FAIL" if there's an error. Since there's no error message from the tool, it's likely the command succeeded. Therefore, the correct response should be "DONE".
</think>
</think>
DONE
[05:03:04] INFO Auto-reply: Assistant message had no tools. Asking for confirmation... complete.py:138
[05:03:04] [Loop control] <system>No tool call detected in last message. Did you mean to finish? If so, make sure you are comp...
User: <system>No tool call detected in last message. Did you mean to finish? If so, make sure you are completely done and then use the `complete` tool to end the session.</system>
Assistant: Thinking...
Assistant:
<think>
<think>
Okay, let me see. The user asked to run the command `date +%F > date-output.txt` using the shell tool. I called the shell function with that command. The response from the tool said the command ran with no output. Since the command is straightforward and doesn't produce any output by default, the absence of output might just mean it worked as expected. The user also mentioned not to retry on error, so if there was an error, I should reply with FAIL. But since there's no output, maybe it's successful. However, the user wants only DONE if successful. But wait, maybe the command failed silently. How can I check?
Wait, the user's instruction says if the command fails, reply only with FAIL. If it succeeds, reply with DONE. Since the tool's response says "No output," perhaps the command executed without errors. The date command usually outputs the current date, so redirecting it to a file should work. Unless there's a permission issue or the file can't be written. But the user didn't mention any error. The tool's response didn't show any error messages. So maybe it's successful. Therefore, the correct response is DONE. But the system message says to use the complete tool if done. Wait, the user's last message was a system message indicating no tool call was detected. The assistant's previous response was DONE, which is a reply, not a tool call. So maybe the assistant should have used the complete tool to end the session. But the user's instructions said if the command succeeds, reply only with DONE. So perhaps the assistant should have replied with DONE and then used the complete tool. But in the previous interaction, the assistant replied with DONE, and the system message is prompting to finish with the complete tool. So maybe the correct step now is to use the complete tool to end the session.
</think>
</think>
[05:03:14] INFO Auto-reply: Assistant message had no tools. Asking for confirmation... complete.py:138
[05:03:14] [Loop control] <system>No tool call detected in last message. Did you mean to finish? If so, make sure you are comp...
User: <system>No tool call detected in last message. Did you mean to finish? If so, make sure you are completely done and then use the `complete` tool to end the session.</system>
Assistant: Thinking...
Assistant:
<think>
<think>
Okay, let me see. The user asked to run the command `date +%F > date-output.txt` using the shell tool. I called the shell function with that command. The response said the command ran with no output. Then the user's last message was a system note saying no tool call was detected and asking if I meant to finish.
Hmm, since the command executed successfully and there's no error, the correct response should be "DONE". But the system message is prompting me to use the `complete` tool if I'm done. Wait, maybe I should check if the command actually worked. The command writes the current date to date-output.txt. If the file was created and has the correct date, then it's successful. Since there was no output from the command, it's likely successful. The user might expect me to confirm completion. But according to the instructions, if successful, reply with "DONE". However, the system is now asking if I meant to finish, so perhaps I should use the `complete` tool now. But the user said not to retry on error and to reply with FAIL or DONE. Since the command succeeded, DONE is correct. But the system is indicating that no tool call was made, so maybe I should use complete. Wait, the user's last message was a system message, not a new command. So maybe the correct action is to reply with DONE as per the earlier instruction. But the system is now asking if I meant to finish. I'm a bit confused. Let me recheck the initial instructions. The user said if the command succeeds, reply only with DONE. Since the command ran without output, it's successful. So the correct response is DONE. But the system is prompting to use complete. Maybe the user wants to end the session. But according to the problem, after the shell command, if successful, reply with DONE. So I should respond with DONE.
</think>
</think>
DONE
[05:03:23] INFO Autonomous mode: No tools used after 2 confirmations. Exiting. complete.py:134
INFO Hook 'complete.auto_reply' signaled session completion __init__.py:360
[05:03:23] Autonomous mode: No tools used after 2 auto-reply confirmations. Exiting.
Goodbye! (resume with: gptme --name gptme__local_qwen3_8b__ollama__tool__shell_date-measured)
[gripprobe] process_finished_at=2026-05-02T05:03:23+00:00 exit_code=0
[gripprobe] process_started_at=2026-05-02T05:02:33+00:00 [gripprobe] process_finished_at=2026-05-02T05:03:23+00:00 exit_code=0
# Modelfile generated by "ollama show"
# To build a new Modelfile based on this, replace FROM with:
# FROM qwen3:8b
FROM /usr/share/ollama/.ollama/models/blobs/sha256-a3de86cd1c132c822487ededd47a324c50491393e6565cd14bafa40d0b8e686f
TEMPLATE """
{{- $lastUserIdx := -1 -}}
{{- range $idx, $msg := .Messages -}}
{{- if eq $msg.Role "user" }}{{ $lastUserIdx = $idx }}{{ end -}}
{{- end }}
{{- if or .System .Tools }}<|im_start|>system
{{ if .System }}
{{ .System }}
{{- end }}
{{- if .Tools }}
# Tools
You may call one or more functions to assist with the user query.
You are provided with function signatures within <tools></tools> XML tags:
<tools>
{{- range .Tools }}
{"type": "function", "function": {{ .Function }}}
{{- end }}
</tools>
For each function call, return a json object with function name and arguments within <tool_call></tool_call> XML tags:
<tool_call>
{"name": <function-name>, "arguments": <args-json-object>}
</tool_call>
{{- end -}}
<|im_end|>
{{ end }}
{{- range $i, $_ := .Messages }}
{{- $last := eq (len (slice $.Messages $i)) 1 -}}
{{- if eq .Role "user" }}<|im_start|>user
{{ .Content }}
{{- if and $.IsThinkSet (eq $i $lastUserIdx) }}
{{- if $.Think -}}
{{- " "}}/think
{{- else -}}
{{- " "}}/no_think
{{- end -}}
{{- end }}<|im_end|>
{{ else if eq .Role "assistant" }}<|im_start|>assistant
{{ if (and $.IsThinkSet (and .Thinking (or $last (gt $i $lastUserIdx)))) -}}
<think>{{ .Thinking }}</think>
{{ end -}}
{{ if .Content }}{{ .Content }}
{{- else if .ToolCalls }}<tool_call>
{{ range .ToolCalls }}{"name": "{{ .Function.Name }}", "arguments": {{ .Function.Arguments }}}
{{ end }}</tool_call>
{{- end }}{{ if not $last }}<|im_end|>
{{ end }}
{{- else if eq .Role "tool" }}<|im_start|>user
<tool_response>
{{ .Content }}
</tool_response><|im_end|>
{{ end }}
{{- if and (ne .Role "assistant") $last }}<|im_start|>assistant
{{ if and $.IsThinkSet (not $.Think) -}}
<think>
</think>
{{ end -}}
{{ end }}
{{- end }}"""
PARAMETER stop <|im_start|>
PARAMETER stop <|im_end|>
PARAMETER temperature 0.6
PARAMETER top_k 20
PARAMETER top_p 0.95
PARAMETER repeat_penalty 1
LICENSE """ Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2024 Alibaba Cloud
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License."""