github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 16:40:08 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #11273] template: Add deepseek with tools support #13495

New Issue
Closed
opened 2026-04-13 00:28:51 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 00:28:51 -05:00
Owner
Copy Link

Original Pull Request: https://github.com/ollama/ollama/pull/11273

State: closed
Merged: No

  • add template tests involving tools
  • add deepseek template from current model and add tools support

Addressing https://github.com/ollama/ollama/issues/10912

Using https://huggingface.co/deepseek-ai/DeepSeek-R1-Distill-Qwen-32B?chat_template=default&format=true as reference for the special tokens.

Now, I don't really understand what is important in the templates and which tokens need to be included in parameters too. So:

  1. are the test cases sufficiently complex or should there be more interleaving messages?
  2. review the use of tokens, should some be included in params?
  3. template doesn't try to join consecutive tool outputs and surround them in <tools_output></tools_output> like the jinja2 seems to try. should it?

It does seem to work but I'm not qualified to evaluate how well or if something else broke (see https://github.com/ollama/ollama/issues/10912#issuecomment-2927853932)

It could be useful to have tests verifying that the tool calls do indeed get parsed as tool calls.

Is "deepseek" ok for levenshtein or should it be "deepseek-r1"?

**Original Pull Request:** https://github.com/ollama/ollama/pull/11273 **State:** closed **Merged:** No --- * add template tests involving tools * add deepseek template from current model and add tools support Addressing https://github.com/ollama/ollama/issues/10912 Using https://huggingface.co/deepseek-ai/DeepSeek-R1-Distill-Qwen-32B?chat_template=default&format=true as reference for the special tokens. Now, I don't really understand what is important in the templates and which tokens need to be included in parameters too. So: 1. are the test cases sufficiently complex or should there be more interleaving messages? 2. review the use of tokens, should some be included in params? 3. template doesn't try to join consecutive tool outputs and surround them in `<tools_output></tools_output>` like the jinja2 seems to try. should it? It does seem to work but I'm not qualified to evaluate how well or if something else broke (see https://github.com/ollama/ollama/issues/10912#issuecomment-2927853932) It could be useful to have tests verifying that the tool calls do indeed get parsed as tool calls. Is "deepseek" ok for levenshtein or should it be "deepseek-r1"?
GiteaMirror added the pull-request label 2026-04-13 00:28:51 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#13495
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?