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

[GH-ISSUE #2840] Plans for Ollama Go library? #1726

New Issue
Closed
opened 2026-04-12 11:42:18 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-12 11:42:18 -05:00
Owner
Copy Link

Originally created by @eliben on GitHub (Feb 29, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2840

The Ollama team has recently released native client libraries for JS (https://github.com/ollama/ollama-js) and Python (https://github.com/ollama/ollama-python).

Are there plans to develop a similar native Go library?

Originally created by @eliben on GitHub (Feb 29, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2840 The Ollama team has recently released native client libraries for JS (https://github.com/ollama/ollama-js) and Python (https://github.com/ollama/ollama-python). Are there plans to develop a similar native Go library?
GiteaMirror added the feature request label 2026-04-12 11:42:18 -05:00
GiteaMirror commented 2026-04-12 11:42:20 -05:00
Author
Owner
Copy Link

@trymeouteh commented on GitHub (Feb 29, 2024):

Would also like to see a Dart and Rust library.

<!-- gh-comment-id:1971993243 --> @trymeouteh commented on GitHub (Feb 29, 2024): Would also like to see a Dart and Rust library.
GiteaMirror commented 2026-04-12 11:42:21 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Mar 1, 2024):

There is the one in /api, which is what we use for the REPL, but it's not as well commented as the python/js client libraries.

<!-- gh-comment-id:1972256922 --> @pdevine commented on GitHub (Mar 1, 2024): There is the one in `/api`, which is what we use for the REPL, but it's not as well commented as the python/js client libraries.
GiteaMirror commented 2026-04-12 11:42:21 -05:00
Author
Owner
Copy Link

@eliben commented on GitHub (Mar 1, 2024):

There is the one in /api, which is what we use for the REPL, but it's not as well commented as the python/js client libraries.

Thanks for your reply @pdevine
Do you intend to document it as an externally usable API? It's exported and hence appears at https://pkg.go.dev/github.com/jmorganca/ollama/api -- what other documentation would you envision it having? Happy to contribute PRs if that would help.

Ideally it would be positioned on an equal footing with the Python / JS libraries; since for those separate projects exist it may appear like a Go library wasn't developed - folks may not consider looking into the repository itself (and the client-server architecture of the ollama tool isn't immediately apparent). This is something documentation can definitely help solve.

<!-- gh-comment-id:1972458890 --> @eliben commented on GitHub (Mar 1, 2024): > There is the one in `/api`, which is what we use for the REPL, but it's not as well commented as the python/js client libraries. Thanks for your reply @pdevine Do you intend to document it as an externally usable API? It's exported and hence appears at https://pkg.go.dev/github.com/jmorganca/ollama/api -- what other documentation would you envision it having? Happy to contribute PRs if that would help. Ideally it would be positioned on an equal footing with the Python / JS libraries; since for those separate projects exist it may appear like a Go library wasn't developed - folks may not consider looking into the repository itself (and the client-server architecture of the `ollama` tool isn't immediately apparent). This is something documentation can definitely help solve.
GiteaMirror commented 2026-04-12 11:42:22 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Mar 1, 2024):

I'd love to get it up to the same standard as the other two libraries. I think in terms of functionality it should be really close (we use it heavily internally), it's just that we haven't had time (or the people!). It'd be awesome if you wanted to take a look; you can just try to copy the documentation from the other libraries. If you want to ping me on the discord I can give more details.

<!-- gh-comment-id:1973625954 --> @pdevine commented on GitHub (Mar 1, 2024): I'd love to get it up to the same standard as the other two libraries. I think in terms of functionality it should be really close (we use it heavily internally), it's just that we haven't had time (or the people!). It'd be awesome if you wanted to take a look; you can just try to copy the documentation from the other libraries. If you want to ping me on the discord I can give more details.
GiteaMirror commented 2026-04-12 11:42:23 -05:00
Author
Owner
Copy Link

@eliben commented on GitHub (Mar 1, 2024):

SGTM, I'll look into it

<!-- gh-comment-id:1973974682 --> @eliben commented on GitHub (Mar 1, 2024): SGTM, I'll look into it
GiteaMirror commented 2026-04-12 11:42:25 -05:00
Author
Owner
Copy Link

@eliben commented on GitHub (Mar 2, 2024):

@pdevine @jmorganca PTAL at #2878 and let me know if it's heading in the right direction

<!-- gh-comment-id:1974805971 --> @eliben commented on GitHub (Mar 2, 2024): @pdevine @jmorganca PTAL at #2878 and let me know if it's heading in the right direction
GiteaMirror commented 2026-04-12 11:42:26 -05:00
Author
Owner
Copy Link

@eliben commented on GitHub (Mar 2, 2024):

Similarly, https://github.com/ollama/ollama/pull/2879 starts adding examples in examples/

<!-- gh-comment-id:1974816020 --> @eliben commented on GitHub (Mar 2, 2024): Similarly, https://github.com/ollama/ollama/pull/2879 starts adding examples in `examples/`
GiteaMirror commented 2026-04-12 11:42:27 -05:00
Author
Owner
Copy Link

@eliben commented on GitHub (Mar 7, 2024):

@pdevine @jmorganca friendly ping - please review #2878 and #2879 and LMK if this is the right direction to pursue.

<!-- gh-comment-id:1982182347 --> @eliben commented on GitHub (Mar 7, 2024): @pdevine @jmorganca friendly ping - please review #2878 and #2879 and LMK if this is the right direction to pursue.
GiteaMirror commented 2026-04-12 11:42:27 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (May 17, 2024):

Thanks so much @eliben for those two PRs! I'll go ahead and close this guy. I'd still like to do an "official" go client at some point similar to js/python.

<!-- gh-comment-id:2118466137 --> @pdevine commented on GitHub (May 17, 2024): Thanks so much @eliben for those two PRs! I'll go ahead and close this guy. I'd still like to do an "official" go client at some point similar to js/python.
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 feature 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#1726
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?