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

[GH-ISSUE #5993] Tool calls streaming #65786

New Issue
Closed
opened 2026-05-03 22:41:18 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-03 22:41:18 -05:00
Owner
Copy Link

Originally created by @jacob-ebey on GitHub (Jul 26, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5993

What is the issue?

Looking through PR's and issues around tool calls + streaming, it seems we are overlooking that when a tool call is encountered, the body of the tool-call should be discriminated from the "chat response".

We need to be able to implement the following high level logic:

for await (const chunk of response) {
  if (chunk is tool response) {
    storeAndCallToolLater(chunk);
  } else {
    showChatResponseToUser(chunk);
  }

I may be overlooking something, so please let me know if I am.

Originally created by @jacob-ebey on GitHub (Jul 26, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5993 ### What is the issue? Looking through PR's and issues around tool calls + streaming, it seems we are overlooking that when a tool call is encountered, the body of the tool-call should be discriminated from the "chat response". We need to be able to implement the following high level logic: ```js for await (const chunk of response) { if (chunk is tool response) { storeAndCallToolLater(chunk); } else { showChatResponseToUser(chunk); } ``` I may be overlooking something, so please let me know if I am.
GiteaMirror added the bug label 2026-05-03 22:41:18 -05:00
GiteaMirror commented 2026-05-03 22:41:23 -05:00
Author
Owner
Copy Link

@jacob-ebey commented on GitHub (Jul 27, 2024):

I've implemented this functionality in user-land if anyone needs it now: https://github.com/jacob-ebey/ollama-tools

<!-- gh-comment-id:2253783609 --> @jacob-ebey commented on GitHub (Jul 27, 2024): I've implemented this functionality in user-land if anyone needs it now: https://github.com/jacob-ebey/ollama-tools
GiteaMirror commented 2026-05-03 22:41:24 -05:00
Author
Owner
Copy Link

@RobinBially commented on GitHub (Jul 27, 2024):

There are already multiple pull requests:
https://github.com/ollama/ollama/pull/5995
and
https://github.com/ollama/ollama/pull/5915

<!-- gh-comment-id:2254071647 --> @RobinBially commented on GitHub (Jul 27, 2024): There are already multiple pull requests: https://github.com/ollama/ollama/pull/5995 and https://github.com/ollama/ollama/pull/5915
GiteaMirror commented 2026-05-03 22:41:25 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (Sep 4, 2024):

Merging with https://github.com/ollama/ollama/issues/5796

<!-- gh-comment-id:2327885043 --> @jmorganca commented on GitHub (Sep 4, 2024): Merging with https://github.com/ollama/ollama/issues/5796
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 bug
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#65786
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?