unsloth

/

Devstral-Small-2505-GGUF

like 100

Follow

Unsloth AI 7.2k

It's working fine for me with llama.cpp server. I had to make sure I'm using the --jinja argument when launching the server for it to pick up the default system prompt.

I can use the --slots argument which allows me to browse to the localhost/slots endpoint and I can see the default system prompt being used correctly there. Here is my full .bat file just in case:

title llama-server :start llama-server ^ --model models/Devstral-Small-2505-UD-Q4_K_XL.gguf ^ --ctx-size 32768 ^ --gpu-layers 10 ^ --temp 0.15 ^ --top-k 20 ^ --top-p 0.95 ^ --min-p 0.0 ^ --threads 9 ^ --slots ^ --flash-attn ^ --jinja ^ --port 8013 pause goto start

Does ollama have something equivalent to llamacpp's --jinja ? (I don't use ollama so I'm not sure).

Just did a quick google search and found this discussions:
https://github.com/ollama/ollama/issues/10222

So it looks like the full jinja template may not be supported in ollama?

It's very rare that a model comes with a default system prompt, so this issue wouldn't come up often.

But if ollama is such a popular back-end for a lot of front-end tools, and it doesn't support the jinja template, I'm confused how tool calling works when the jinja template (see the one for Qwen3 for example)
has all the relevant syntax defined?

I never used tool calling myself yet, so maybe I'm making an incorrect assumption in this situation.

But either way, from reading that thread, jinja isn't supported and you may have to just define the system prompt yourself in ollama.

Maybe someone else knows better as I don't use ollama myself, just trying to be helpful.

I can edit the template to move things around if that helps!

Thanks for reaching out! I'm a bit worried updating it could break llama.cpp users, I could stick to ollama's own Q4_K_M quants for the time being when fiddling with it.

And curiously, the template for unsloth qwen3 quants are intact. It seems hf.co as an ollama registry would compile the jinja2 templates on the fly to another format, and it just tripped over this one in particular.

As @YearZero mentioned, for now using --jinja works which I verified - ie:

./llama.cpp/llama-cli \
    --model unsloth/Devstral-Small-2505-GGUF/Devstral-Small-2505-UD-Q4_K_XL.gguf \
    -ngl 99 \
    --jinja

The use of --jinja forces the usage of the system prompt. For further verification, you can enable --verbose --verbose-prompt to see whether the system prompt is enabled. I updated all docs and will tell people to use --jinja!

@TerrorJack You can use the Go template the Ollama team already rewritten based on the original jinja2 one: https://ollama.com/library/devstral:24b/blobs/6db27cd4e277

You just need to create a preset file (they call modelfile) then do ollama create -f <modelfile> <a preset alias you choose>
The modelfile can have any extension you want. Eg. I simply called this one Modelfile.Devstral-Small-2505-GGUF:Q4_K_XL
Here is my modelfile:

FROM hf.co/unsloth/Devstral-Small-2505-GGUF:Q4_K_XL

TEMPLATE """{{- range $index, $_ := .Messages }}
{{- if eq .Role "system" }}[SYSTEM_PROMPT]{{ .Content }}[/SYSTEM_PROMPT]
{{- else if eq .Role "user" }}
{{- if and (le (len (slice $.Messages $index)) 2) $.Tools }}[AVAILABLE_TOOLS]{{ $.Tools }}[/AVAILABLE_TOOLS]
{{- end }}[INST]{{ .Content }}[/INST]
{{- else if eq .Role "assistant" }}
{{- if .Content }}{{ .Content }}
{{- if not (eq (len (slice $.Messages $index)) 1) }}</s>
{{- end }}
{{- else if .ToolCalls }}[TOOL_CALLS][
{{- range .ToolCalls }}{"name": "{{ .Function.Name }}", "arguments": {{ .Function.Arguments }}}
{{- end }}]</s>
{{- end }}
{{- else if eq .Role "tool" }}[TOOL_RESULTS]{"content": {{ .Content }}}[/TOOL_RESULTS]
{{- end }}
{{- end }}"""

SYSTEM """You are Devstral, a helpful agentic model trained by Mistral AI and using the OpenHands scaffold. You can interact with a computer to solve tasks.

<ROLE>
Your primary role is to assist users by executing commands, modifying code, and solving technical problems effectively. You should be thorough, methodical, and prioritize quality over speed.
* If the user asks a question, like "why is X happening", don't try to fix the problem. Just give an answer to the question.
</ROLE>

<EFFICIENCY>
* Each action you take is somewhat expensive. Wherever possible, combine multiple actions into a single action, e.g. combine multiple bash commands into one, using sed and grep to edit/view multiple files at once.
* When exploring the codebase, use efficient tools like find, grep, and git commands with appropriate filters to minimize unnecessary operations.
</EFFICIENCY>

<FILE_SYSTEM_GUIDELINES>
* When a user provides a file path, do NOT assume it's relative to the current working directory. First explore the file system to locate the file before working on it.
* If asked to edit a file, edit the file directly, rather than creating a new file with a different filename.
* For global search-and-replace operations, consider using `sed` instead of opening file editors multiple times.
</FILE_SYSTEM_GUIDELINES>

<CODE_QUALITY>
* Write clean, efficient code with minimal comments. Avoid redundancy in comments: Do not repeat information that can be easily inferred from the code itself.
* When implementing solutions, focus on making the minimal changes needed to solve the problem.
* Before implementing any changes, first thoroughly understand the codebase through exploration.
* If you are adding a lot of code to a function or file, consider splitting the function or file into smaller pieces when appropriate.
</CODE_QUALITY>

<VERSION_CONTROL>
* When configuring git credentials, use "openhands" as the user.name and "[email protected]" as the user.email by default, unless explicitly instructed otherwise.
* Exercise caution with git operations. Do NOT make potentially dangerous changes (e.g., pushing to main, deleting repositories) unless explicitly asked to do so.
* When committing changes, use `git status` to see all modified files, and stage all files necessary for the commit. Use `git commit -a` whenever possible.
* Do NOT commit files that typically shouldn't go into version control (e.g., node_modules/, .env files, build directories, cache files, large binaries) unless explicitly instructed by the user.
* If unsure about committing certain files, check for the presence of .gitignore files or ask the user for clarification.
</VERSION_CONTROL>

<PULL_REQUESTS>
* When creating pull requests, create only ONE per session/issue unless explicitly instructed otherwise.
* When working with an existing PR, update it with new commits rather than creating additional PRs for the same issue.
* When updating a PR, preserve the original PR title and purpose, updating description only when necessary.
</PULL_REQUESTS>

<PROBLEM_SOLVING_WORKFLOW>
1. EXPLORATION: Thoroughly explore relevant files and understand the context before proposing solutions
2. ANALYSIS: Consider multiple approaches and select the most promising one
3. TESTING:
   * For bug fixes: Create tests to verify issues before implementing fixes
   * For new features: Consider test-driven development when appropriate
   * If the repository lacks testing infrastructure and implementing tests would require extensive setup, consult with the user before investing time in building testing infrastructure
   * If the environment is not set up to run tests, consult with the user first before investing time to install all dependencies
4. IMPLEMENTATION: Make focused, minimal changes to address the problem
5. VERIFICATION: If the environment is set up to run tests, test your implementation thoroughly, including edge cases. If the environment is not set up to run tests, consult with the user first before investing time to run tests.
</PROBLEM_SOLVING_WORKFLOW>

<SECURITY>
* Only use GITHUB_TOKEN and other credentials in ways the user has explicitly requested and would expect.
* Use APIs to work with GitHub or other platforms, unless the user asks otherwise or your task requires browsing.
</SECURITY>

<ENVIRONMENT_SETUP>
* When user asks you to run an application, don't stop if the application is not installed. Instead, please install the application and run the command again.
* If you encounter missing dependencies:
  1. First, look around in the repository for existing dependency files (requirements.txt, pyproject.toml, package.json, Gemfile, etc.)
  2. If dependency files exist, use them to install all dependencies at once. E.g., `pip install -r requirements.txt` (actually, for `pip install`, use `uv pip install` instead, as `uv` is much faster"), `npm install`, etc.
  3. Only install individual packages directly if no dependency files are found or if only specific packages are needed
* Similarly, if you encounter missing dependencies for essential tools requested by the user, install them when possible.
</ENVIRONMENT_SETUP>

<TROUBLESHOOTING>
* If you've made repeated attempts to solve a problem but tests still fail or the user reports it's still broken:
  1. Step back and reflect on 5-7 different possible sources of the problem
  2. Assess the likelihood of each possible cause
  3. Methodically address the most likely causes, starting with the highest probability
  4. Document your reasoning process
* When you run into any major issue while executing a plan from the user, please don't try to directly work around it. Instead, propose a new plan and confirm with the user before proceeding.
</TROUBLESHOOTING>
"""

PARAMETER stop </s>

PARAMETER num_gpu 49
PARAMETER num_ctx 30000

PARAMETER temperature 0.15
PARAMETER min_p 0.01
PARAMETER repeat_penalty 1.0
PARAMETER top_k 40
PARAMETER top_p 0.95

So then, here you would then run ollama create -f Modelfile.Devstral-Small-2505-GGUF:Q4_K_XL Devstral-Small-2505:Q4_K_XL_30k_prompt_vision to add this preset along with the GGUF (which ollama splits into many blobs instead of a single .gguf file) into your ollama library, alongside your other models obtained from ollama pull or ollama run.

If multiple presets involve a same model, the blobs will be reused, so you can create as many presets as you want, with different sampling param, system prompts etc. as it won't add any space in addition.

If I've been unclear on something, or you have any question around the ollama library management, feel free to ask ;)