Upload folder using huggingface_hub

README.md

@@ -9,22 +9,187 @@ language:
 - es
 - th
 library_name: transformers
+base_model: meta-llama/Meta-Llama-3.1-70B
 license: llama3.1
 pipeline_tag: text-generation
 tags:
 - facebook
 - meta
-
+- pytorch
 - llama
 - llama-3
-
+extra_gated_prompt: "### LLAMA 3.1 COMMUNITY LICENSE AGREEMENT\nLlama 3.1 Version\
+  \ Release Date: July 23, 2024\n\"Agreement\" means the terms and conditions for\
+  \ use, reproduction, distribution and modification of the  Llama Materials set forth\
+  \ herein.\n\"Documentation\" means the specifications, manuals and documentation\
+  \ accompanying Llama 3.1 distributed by Meta at https://llama.meta.com/doc/overview.\n\
+  \"Licensee\" or \"you\" means you, or your employer or any other person or entity\
+  \ (if you are entering into this Agreement on such person or entity’s behalf), of\
+  \ the age required under applicable laws, rules or regulations to provide legal\
+  \ consent and that has legal authority to bind your employer or such other person\
+  \ or entity if you are entering in this Agreement on their behalf.\n\"Llama 3.1\"\
+  \ means the foundational large language models and software and algorithms, including\
+  \ machine-learning model code, trained model weights, inference-enabling code, training-enabling\
+  \ code, fine-tuning enabling code and other elements of the foregoing distributed\
+  \ by Meta at https://llama.meta.com/llama-downloads.\n\"Llama Materials\" means,\
+  \ collectively, Meta’s proprietary Llama 3.1 and Documentation (and any portion\
+  \ thereof) made available under this Agreement.\n\"Meta\" or \"we\" means Meta Platforms\
+  \ Ireland Limited (if you are located in or, if you are an entity, your principal\
+  \ place of business is in the EEA or Switzerland) and Meta Platforms, Inc. (if you\
+  \ are located outside of the EEA or Switzerland).\n   \n1. License Rights and Redistribution.\n\
+  a. Grant of Rights. You are granted a non-exclusive, worldwide, non-transferable\
+  \ and royalty-free limited license under Meta’s intellectual property or other rights\
+  \ owned by Meta embodied in the Llama Materials to use, reproduce, distribute, copy,\
+  \ create derivative works of, and make modifications to the Llama Materials.\nb.\
+  \ Redistribution and Use.\ni. If you distribute or make available the Llama Materials\
+  \ (or any derivative works thereof), or a product or service (including another\
+  \ AI model) that contains any of them, you shall (A) provide a copy of this Agreement\
+  \ with any such Llama Materials; and (B) prominently display “Built with Llama”\
+  \ on a related website, user interface, blogpost, about page, or product documentation.\
+  \ If you use the Llama Materials or any outputs or results of the Llama Materials\
+  \ to create, train, fine tune, or otherwise improve an AI model, which is distributed\
+  \ or made available, you shall also include “Llama” at the beginning of any such\
+  \ AI model name.\nii. If you receive Llama Materials, or any derivative works thereof,\
+  \ from a Licensee as part  of an integrated end user product, then Section 2 of\
+  \ this Agreement will not apply to you.\niii. You must retain in all copies of the\
+  \ Llama Materials that you distribute the following attribution notice within a\
+  \ “Notice” text file distributed as a part of such copies: “Llama 3.1 is licensed\
+  \ under the Llama 3.1 Community License, Copyright © Meta Platforms, Inc. All Rights\
+  \ Reserved.”\niv. Your use of the Llama Materials must comply with applicable laws\
+  \ and regulations (including trade compliance laws and regulations) and adhere to\
+  \ the Acceptable Use Policy for the Llama Materials (available at https://llama.meta.com/llama3_1/use-policy),\
+  \ which is hereby incorporated by reference into this Agreement.\n2. Additional\
+  \ Commercial Terms. If, on the Llama 3.1 version release date, the monthly active\
+  \ users of the products or services made available by or for Licensee, or Licensee’s\
+  \ affiliates, is greater than 700 million monthly active users in the preceding\
+  \ calendar month, you must request a license from Meta, which Meta may grant to\
+  \ you in its sole discretion, and you are not authorized to exercise any of the\
+  \ rights under this Agreement unless or until Meta otherwise expressly grants you\
+  \ such rights.\n3. Disclaimer of Warranty. UNLESS REQUIRED BY APPLICABLE LAW, THE\
+  \ LLAMA MATERIALS AND ANY OUTPUT AND RESULTS THEREFROM ARE PROVIDED ON AN “AS IS”\
+  \ BASIS, WITHOUT WARRANTIES OF ANY KIND, AND META DISCLAIMS ALL WARRANTIES OF ANY\
+  \ KIND, BOTH EXPRESS AND IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES\
+  \ OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.\
+  \ YOU ARE SOLELY RESPONSIBLE FOR DETERMINING THE APPROPRIATENESS OF USING OR REDISTRIBUTING\
+  \ THE LLAMA MATERIALS AND ASSUME ANY RISKS ASSOCIATED WITH YOUR USE OF THE LLAMA\
+  \ MATERIALS AND ANY OUTPUT AND RESULTS.\n4. Limitation of Liability. IN NO EVENT\
+  \ WILL META OR ITS AFFILIATES BE LIABLE UNDER ANY THEORY OF LIABILITY, WHETHER IN\
+  \ CONTRACT, TORT, NEGLIGENCE, PRODUCTS LIABILITY, OR OTHERWISE, ARISING OUT OF THIS\
+  \ AGREEMENT, FOR ANY LOST PROFITS OR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL,\
+  \ EXEMPLARY OR PUNITIVE DAMAGES, EVEN IF META OR ITS AFFILIATES HAVE BEEN ADVISED\
+  \ OF THE POSSIBILITY OF ANY OF THE FOREGOING.\n5. Intellectual Property.\na. No\
+  \ trademark licenses are granted under this Agreement, and in connection with the\
+  \ Llama Materials, neither Meta nor Licensee may use any name or mark owned by or\
+  \ associated with the other or any of its affiliates, except as required for reasonable\
+  \ and customary use in describing and redistributing the Llama Materials or as set\
+  \ forth in this Section 5(a). Meta hereby grants you a license to use “Llama” (the\
+  \ “Mark”) solely as required to comply with the last sentence of Section 1.b.i.\
+  \ You will comply with Meta’s brand guidelines (currently accessible at https://about.meta.com/brand/resources/meta/company-brand/\
+  \ ). All goodwill arising out of your use of the Mark will inure to the benefit\
+  \ of Meta.\nb. Subject to Meta’s ownership of Llama Materials and derivatives made\
+  \ by or for Meta, with respect to any derivative works and modifications of the\
+  \ Llama Materials that are made by you, as between you and Meta, you are and will\
+  \ be the owner of such derivative works and modifications.\nc. If you institute\
+  \ litigation or other proceedings against Meta or any entity (including a cross-claim\
+  \ or counterclaim in a lawsuit) alleging that the Llama Materials or Llama 3.1 outputs\
+  \ or results, or any portion of any of the foregoing, constitutes infringement of\
+  \ intellectual property or other rights owned or licensable by you, then any licenses\
+  \ granted to you under this Agreement shall terminate as of the date such litigation\
+  \ or claim is filed or instituted. You will indemnify and hold harmless Meta from\
+  \ and against any claim by any third party arising out of or related to your use\
+  \ or distribution of the Llama Materials.\n6. Term and Termination. The term of\
+  \ this Agreement will commence upon your acceptance of this Agreement or access\
+  \ to the Llama Materials and will continue in full force and effect until terminated\
+  \ in accordance with the terms and conditions herein. Meta may terminate this Agreement\
+  \ if you are in breach of any term or condition of this Agreement. Upon termination\
+  \ of this Agreement, you shall delete and cease use of the Llama Materials. Sections\
+  \ 3, 4 and 7 shall survive the termination of this Agreement.\n7. Governing Law\
+  \ and Jurisdiction. This Agreement will be governed and construed under the laws\
+  \ of the State of California without regard to choice of law principles, and the\
+  \ UN Convention on Contracts for the International Sale of Goods does not apply\
+  \ to this Agreement. The courts of California shall have exclusive jurisdiction\
+  \ of any dispute arising out of this Agreement.\n### Llama 3.1 Acceptable Use Policy\n\
+  Meta is committed to promoting safe and fair use of its tools and features, including\
+  \ Llama 3.1. If you access or use Llama 3.1, you agree to this Acceptable Use Policy\
+  \ (“Policy”). The most recent copy of this policy can be found at [https://llama.meta.com/llama3_1/use-policy](https://llama.meta.com/llama3_1/use-policy)\n\
+  #### Prohibited Uses\nWe want everyone to use Llama 3.1 safely and responsibly.\
+  \ You agree you will not use, or allow others to use, Llama 3.1 to:\n 1. Violate\
+  \ the law or others’ rights, including to:\n    1. Engage in, promote, generate,\
+  \ contribute to, encourage, plan, incite, or further illegal or unlawful activity\
+  \ or content, such as:\n        1. Violence or terrorism\n        2. Exploitation\
+  \ or harm to children, including the solicitation, creation, acquisition, or dissemination\
+  \ of child exploitative content or failure to report Child Sexual Abuse Material\n\
+  \        3. Human trafficking, exploitation, and sexual violence\n        4. The\
+  \ illegal distribution of information or materials to minors, including obscene\
+  \ materials, or failure to employ legally required age-gating in connection with\
+  \ such information or materials.\n        5. Sexual solicitation\n        6. Any\
+  \ other criminal activity\n    3. Engage in, promote, incite, or facilitate the\
+  \ harassment, abuse, threatening, or bullying of individuals or groups of individuals\n\
+  \    4. Engage in, promote, incite, or facilitate discrimination or other unlawful\
+  \ or harmful conduct in the provision of employment, employment benefits, credit,\
+  \ housing, other economic benefits, or other essential goods and services\n    5.\
+  \ Engage in the unauthorized or unlicensed practice of any profession including,\
+  \ but not limited to, financial, legal, medical/health, or related professional\
+  \ practices\n    6. Collect, process, disclose, generate, or infer health, demographic,\
+  \ or other sensitive personal or private information about individuals without rights\
+  \ and consents required by applicable laws\n    7. Engage in or facilitate any action\
+  \ or generate any content that infringes, misappropriates, or otherwise violates\
+  \ any third-party rights, including the outputs or results of any products or services\
+  \ using the Llama Materials\n    8. Create, generate, or facilitate the creation\
+  \ of malicious code, malware, computer viruses or do anything else that could disable,\
+  \ overburden, interfere with or impair the proper working, integrity, operation\
+  \ or appearance of a website or computer system\n2. Engage in, promote, incite,\
+  \ facilitate, or assist in the planning or development of activities that present\
+  \ a risk of death or bodily harm to individuals, including use of Llama 3.1 related\
+  \ to the following:\n    1. Military, warfare, nuclear industries or applications,\
+  \ espionage, use for materials or activities that are subject to the International\
+  \ Traffic Arms Regulations (ITAR) maintained by the United States Department of\
+  \ State\n    2. Guns and illegal weapons (including weapon development)\n    3.\
+  \ Illegal drugs and regulated/controlled substances\n    4. Operation of critical\
+  \ infrastructure, transportation technologies, or heavy machinery\n    5. Self-harm\
+  \ or harm to others, including suicide, cutting, and eating disorders\n    6. Any\
+  \ content intended to incite or promote violence, abuse, or any infliction of bodily\
+  \ harm to an individual\n3. Intentionally deceive or mislead others, including use\
+  \ of Llama 3.1 related to the following:\n    1. Generating, promoting, or furthering\
+  \ fraud or the creation or promotion of disinformation\n    2. Generating, promoting,\
+  \ or furthering defamatory content, including the creation of defamatory statements,\
+  \ images, or other content\n    3. Generating, promoting, or further distributing\
+  \ spam\n    4. Impersonating another individual without consent, authorization,\
+  \ or legal right\n    5. Representing that the use of Llama 3.1 or outputs are human-generated\n\
+  \    6. Generating or facilitating false online engagement, including fake reviews\
+  \ and other means of fake online engagement\n4. Fail to appropriately disclose to\
+  \ end users any known dangers of your AI system\nPlease report any violation of\
+  \ this Policy, software “bug,” or other problems that could lead to a violation\
+  \ of this Policy through one of the following means:\n    * Reporting issues with\
+  \ the model: [https://github.com/meta-llama/llama-models/issues](https://github.com/meta-llama/llama-models/issues)\n\
+  \    * Reporting risky content generated by the model:\n    developers.facebook.com/llama_output_feedback\n\
+  \    * Reporting bugs and security concerns: facebook.com/whitehat/info\n    * Reporting\
+  \ violations of the Acceptable Use Policy or unlicensed uses of Meta Llama 3: [email protected]"
+extra_gated_fields:
+  First Name: text
+  Last Name: text
+  Date of birth: date_picker
+  Country: country
+  Affiliation: text
+  Job title:
+    type: select
+    options:
+    - Student
+    - Research Graduate
+    - AI researcher
+    - AI developer/engineer
+    - Reporter
+    - Other
+  geo: ip_location
+  ? By clicking Submit below I accept the terms of the license and acknowledge that
+    the information I provide will be collected stored processed and shared in accordance
+    with the Meta Privacy Policy
+  : checkbox
+extra_gated_description: The information you provide will be collected, stored, processed
+  and shared in accordance with the [Meta Privacy Policy](https://www.facebook.com/privacy/policy/).
+extra_gated_button_content: Submit
 ---
 
-Exl2 quant version using [exllamav2 0.1.8](https://github.com/turboderp/exllamav2/releases/tag/v0.1.8)
-
-Update 25/07 - requanted with [fixed tokenizer ](https://huggingface.co/meta-llama/Meta-Llama-3.1-8B-Instruct/discussions/28/files)
-
-
 ## Model Information
 
 The Meta Llama 3.1 collection of multilingual large language models (LLMs) is a collection of pretrained and instruction tuned generative models in 8B, 70B and 405B sizes (text in/text out). The Llama 3.1 instruction tuned text only models (8B, 70B, 405B) are optimized for multilingual dialogue use cases and outperform many of the available open source and closed chat models on common industry benchmarks.
@@ -160,6 +325,52 @@ outputs = pipeline(
 print(outputs[0]["generated_text"][-1])
 ```
 
+### Tool use with transformers
+
+LLaMA-3.1 supports multiple tool use formats. You can see a full guide to prompt formatting [here](https://llama.meta.com/docs/model-cards-and-prompt-formats/llama3_1/).
+
+Tool use is also supported through [chat templates](https://huggingface.co/docs/transformers/main/chat_templating#advanced-tool-use--function-calling) in Transformers. 
+Here is a quick example showing a single simple tool:
+
+```python
+# First, define a tool
+def get_current_temperature(location: str) -> float:
+    """
+    Get the current temperature at a location.
+    
+    Args:
+        location: The location to get the temperature for, in the format "City, Country"
+    Returns:
+        The current temperature at the specified location in the specified units, as a float.
+    """
+    return 22.  # A real function should probably actually get the temperature!
+
+# Next, create a chat and apply the chat template
+messages = [
+  {"role": "system", "content": "You are a bot that responds to weather queries."},
+  {"role": "user", "content": "Hey, what's the temperature in Paris right now?"}
+]
+
+inputs = tokenizer.apply_chat_template(messages, tools=[get_current_temperature], add_generation_prompt=True)
+```
+
+You can then generate text from this input as normal. If the model generates a tool call, you should add it to the chat like so:
+
+```python
+tool_call = {"name": "get_current_temperature", "arguments": {"location": "Paris, France"}}
+messages.append({"role": "assistant", "tool_calls": [{"type": "function", "function": tool_call}]})
+```
+
+and then call the tool and append the result, with the `tool` role, like so:
+
+```python
+messages.append({"role": "tool", "name": "get_current_temperature", "content": "22.0"})
+```
+
+After that, you can `generate()` again to let the model use the tool result in the chat. Note that this was a very brief introduction to tool calling - for more information,
+see the [LLaMA prompt format docs](https://llama.meta.com/docs/model-cards-and-prompt-formats/llama3_1/) and the Transformers [tool use documentation](https://huggingface.co/docs/transformers/main/chat_templating#advanced-tool-use--function-calling).
+
+
 ### Use with `bitsandbytes`
 
 The model checkpoints can be used in `8-bit` and `4-bit` for further memory optimisations using `bitsandbytes` and `transformers`

config.json

@@ -37,7 +37,7 @@
     "vocab_size": 128256,
     "quantization_config": {
         "quant_method": "exl2",
-        "version": "0.1.8",
+        "version": "0.1.9",
         "bits": 5.0,
         "head_bits": 6,
         "calibration": {

output-00001-of-00006.safetensors

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ca879d125e6b1be5196dc4ef7d9e3554aba59c6332c38f10c7059bb39f38129e
-size 8494434338
+oid sha256:692d9d2839eb78ad3a9c1236ad9443964c11047f00266644ba94ae443afb4f0a
+size 8467807736

output-00002-of-00006.safetensors

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b8af660e828fbef453a2e7cf53fe22dd0b17a4771a2b203f630a2f08ad9320bf
-size 8578884620
+oid sha256:8b07749369ca1b410e3ffae8bb388c283169010da0504ebab92ca4e3c75115af
+size 8443335848

output-00003-of-00006.safetensors

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1e511619dce1f9033a97cd846bc1407945ae1888187b07bad91bb662d10dc6ff
-size 8533289496
+oid sha256:73a632da297718e4646318bc8c511fb0585ee63d89f2348b119a14720ac8901c
+size 8477458152

output-00004-of-00006.safetensors

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:406d42ace5f660f3e7b74a1955b4964c2a764237f103f5577eda30eb9f4e5a34
-size 8510358412
+oid sha256:b5dda46503662818a877f12a24f69b84431f42e6ad558c92e35aa72b746b030a
+size 8472961552

output-00005-of-00006.safetensors

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f87390803885b6e1075da6d607a598f3cbcbdaee4552f7a7be3b5ed1e74233d6
-size 8580638220
+oid sha256:cc3ed49e367f1cd57f5fa628e5848f5a9cdb30a667410524c4dbd235ef91c68b
+size 8515209568

output-00006-of-00006.safetensors

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e34d634a3a95cc361b76a0bf99afdc98bae6f2e4fa18513d10f9c627c754330d
-size 2989025256
+oid sha256:907552d78c8b98374c22dffe3629f9243c127a251faf20cfa38f4626f0e863a7
+size 3314370060

tokenizer_config.json

@@ -2050,7 +2050,7 @@
     }
   },
   "bos_token": "<|begin_of_text|>",
-  "chat_template": "{% set loop_messages = messages %}{% for message in loop_messages %}{% set content = '<|start_header_id|>' + message['role'] + '<|end_header_id|>\n\n'+ message['content'] | trim + '<|eot_id|>' %}{% if loop.index0 == 0 %}{% set content = bos_token + content %}{% endif %}{{ content }}{% endfor %}{{ '<|start_header_id|>assistant<|end_header_id|>\n\n' }}",
+  "chat_template": "{{- bos_token }}\n{%- if custom_tools is defined %}\n    {%- set tools = custom_tools %}\n{%- endif %}\n{%- if not tools_in_user_message is defined %}\n    {%- set tools_in_user_message = true %}\n{%- endif %}\n{%- if not date_string is defined %}\n    {%- set date_string = \"26 Jul 2024\" %}\n{%- endif %}\n{%- if not tools is defined %}\n    {%- set tools = none %}\n{%- endif %}\n\n{#- This block extracts the system message, so we can slot it into the right place. #}\n{%- if messages[0]['role'] == 'system' %}\n    {%- set system_message = messages[0]['content']|trim %}\n    {%- set messages = messages[1:] %}\n{%- else %}\n    {%- set system_message = \"\" %}\n{%- endif %}\n\n{#- System message + builtin tools #}\n{{- \"<|start_header_id|>system<|end_header_id|>\\n\\n\" }}\n{%- if builtin_tools is defined or tools is not none %}\n    {{- \"Environment: ipython\\n\" }}\n{%- endif %}\n{%- if builtin_tools is defined %}\n    {{- \"Tools: \" + builtin_tools | reject('equalto', 'code_interpreter') | join(\", \") + \"\\n\\n\"}}\n{%- endif %}\n{{- \"Cutting Knowledge Date: December 2023\\n\" }}\n{{- \"Today Date: \" + date_string + \"\\n\\n\" }}\n{%- if tools is not none and not tools_in_user_message %}\n    {{- \"You have access to the following functions. To call a function, please respond with JSON for a function call.\" }}\n    {{- 'Respond in the format {\"name\": function name, \"parameters\": dictionary of argument name and its value}.' }}\n    {{- \"Do not use variables.\\n\\n\" }}\n    {%- for t in tools %}\n        {{- t | tojson(indent=4) }}\n        {{- \"\\n\\n\" }}\n    {%- endfor %}\n{%- endif %}\n{{- system_message }}\n{{- \"<|eot_id|>\" }}\n\n{#- Custom tools are passed in a user message with some extra guidance #}\n{%- if tools_in_user_message and not tools is none %}\n    {#- Extract the first user message so we can plug it in here #}\n    {%- if messages | length != 0 %}\n        {%- set first_user_message = messages[0]['content']|trim %}\n        {%- set messages = messages[1:] %}\n    {%- else %}\n        {{- raise_exception(\"Cannot put tools in the first user message when there's no first user message!\") }}\n{%- endif %}\n    {{- '<|start_header_id|>user<|end_header_id|>\\n\\n' -}}\n    {{- \"Given the following functions, please respond with a JSON for a function call \" }}\n    {{- \"with its proper arguments that best answers the given prompt.\\n\\n\" }}\n    {{- 'Respond in the format {\"name\": function name, \"parameters\": dictionary of argument name and its value}.' }}\n    {{- \"Do not use variables.\\n\\n\" }}\n    {%- for t in tools %}\n        {{- t | tojson(indent=4) }}\n        {{- \"\\n\\n\" }}\n    {%- endfor %}\n    {{- first_user_message + \"<|eot_id|>\"}}\n{%- endif %}\n\n{%- for message in messages %}\n    {%- if not (message.role == 'ipython' or message.role == 'tool' or 'tool_calls' in message) %}\n        {{- '<|start_header_id|>' + message['role'] + '<|end_header_id|>\\n\\n'+ message['content'] | trim + '<|eot_id|>' }}\n    {%- elif 'tool_calls' in message %}\n        {%- if not message.tool_calls|length == 1 %}\n            {{- raise_exception(\"This model only supports single tool-calls at once!\") }}\n        {%- endif %}\n        {%- set tool_call = message.tool_calls[0].function %}\n        {%- if builtin_tools is defined and tool_call.name in builtin_tools %}\n            {{- '<|start_header_id|>assistant<|end_header_id|>\\n\\n' -}}\n            {{- \"<|python_tag|>\" + tool_call.name + \".call(\" }}\n            {%- for arg_name, arg_val in tool_call.arguments | items %}\n                {{- arg_name + '=\"' + arg_val + '\"' }}\n                {%- if not loop.last %}\n                    {{- \", \" }}\n                {%- endif %}\n                {%- endfor %}\n            {{- \")\" }}\n        {%- else  %}\n            {{- '<|start_header_id|>assistant<|end_header_id|>\\n\\n' -}}\n            {{- '{\"name\": \"' + tool_call.name + '\", ' }}\n            {{- '\"parameters\": ' }}\n            {{- tool_call.arguments | tojson }}\n            {{- \"}\" }}\n        {%- endif %}\n        {%- if builtin_tools is defined %}\n            {#- This means we're in ipython mode #}\n            {{- \"<|eom_id|>\" }}\n        {%- else %}\n            {{- \"<|eot_id|>\" }}\n        {%- endif %}\n    {%- elif message.role == \"tool\" or message.role == \"ipython\" %}\n        {{- \"<|start_header_id|>ipython<|end_header_id|>\\n\\n\" }}\n        {%- if message.content is mapping or message.content is iterable %}\n            {{- message.content | tojson }}\n        {%- else %}\n            {{- message.content }}\n        {%- endif %}\n        {{- \"<|eot_id|>\" }}\n    {%- endif %}\n{%- endfor %}\n{%- if add_generation_prompt %}\n    {{- '<|start_header_id|>assistant<|end_header_id|>\\n\\n' }}\n{%- endif %}\n",
   "clean_up_tokenization_spaces": true,
   "eos_token": "<|eot_id|>",
   "model_input_names": [