[GH-ISSUE #9903] RAG confusion. #6484

New Issue

GiteaMirror · 2026-04-12T18:03:30-05:00

GiteaMirror commented

2026-04-12 18:03:30 -05:00

Originally created by @JG-Adams on GitHub (Mar 20, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9903

The API documentation for embedding only told half of the picture. You embed it. Now what? How do you actually use RAG? Where does the embedding go? I'm real confused as to why there's little information on it because it's such an important feature. I even had to figure out that this is in fact a RAG.

Originally created by @JG-Adams on GitHub (Mar 20, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9903 The API documentation for embedding only told half of the picture. You embed it. Now what? How do you actually use RAG? Where does the embedding go? I'm real confused as to why there's little information on it because it's such an important feature. I even had to figure out that this is in fact a RAG.

GiteaMirror added the question label 2026-04-12 18:03:30 -05:00

GiteaMirror closed this issue

2026-04-12 18:03:30 -05:00

GiteaMirror commented

2026-04-12 18:03:31 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

ollama is not a RAG, it can be used as a component in a RAG system by creating embeddings and/or response synthesis.

See here for a description of how RAG works, and here for integrations that use ollama in a RAG system.

@rick-github commented on GitHub (Mar 20, 2025): ollama is not a RAG, it can be used as a component in a RAG system by creating embeddings and/or response synthesis. See [here](https://en.wikipedia.org/wiki/Retrieval-augmented_generation) for a description of how RAG works, and [here](https://github.com/ollama/ollama?tab=readme-ov-file#community-integrations) for integrations that use ollama in a RAG system.

GiteaMirror commented

2026-04-12 18:03:32 -05:00

@muhammadismailkhan0009 commented on GitHub (Mar 20, 2025):

RAG is used as input to LLM. so, you will have implement RAG system separately, and add the RAG data into prompts that you are feeding to LLM. the implementation depends upon the programming language and framework you'll be using.

@muhammadismailkhan0009 commented on GitHub (Mar 20, 2025): RAG is used as input to LLM. so, you will have implement RAG system separately, and add the RAG data into prompts that you are feeding to LLM. the implementation depends upon the programming language and framework you'll be using.

GiteaMirror commented

2026-04-12 18:03:32 -05:00

@JG-Adams commented on GitHub (Mar 20, 2025):

Ok thanks. But what I'm asking is not how RAG work or whether Ollama is RAG (I never said it was) but how embedding is used. I'm looking to do RAG.

"RAG is used as input to LLM. so, you will have implement RAG system separately, and add the RAG data into prompts that you are feeding to LLM. the implementation depends upon the programming language and framework you'll be using."

From what I can tell you provide input through the embedding function? That make this a way to do RAG. I'll figure out my own implementation which is C++. (If embedding is not for RAG then I'm curious. What is it for?)

My questions still goes unanswered. "You embed it. Now what?" "Where does the embedding go? " in other word, how is it used afterward?

Guys please just answer the question and maybe provide some clarity in the documents so others wouldn't have to be so confused.

@JG-Adams commented on GitHub (Mar 20, 2025): Ok thanks. But what I'm asking is not how RAG work or whether Ollama is RAG (I never said it was) but how embedding is used. I'm looking to do RAG. "RAG is used as input to LLM. so, you will have implement RAG system separately, and add the RAG data into prompts that you are feeding to LLM. the implementation depends upon the programming language and framework you'll be using." From what I can tell you provide input through the embedding function? That make this a way to do RAG. I'll figure out my own implementation which is C++. (If embedding is not for RAG then I'm curious. What is it for?) My questions still goes unanswered. "You embed it. Now what?" "Where does the embedding go? " in other word, how is it used afterward? Guys please just answer the question and maybe provide some clarity in the documents so others wouldn't have to be so confused.

GiteaMirror commented

2026-04-12 18:03:33 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

The embedding goes in a vector database. Details in the link I provided.

@rick-github commented on GitHub (Mar 20, 2025): The embedding goes in a vector database. Details in the link I provided.

GiteaMirror commented

2026-04-12 18:03:34 -05:00

@JG-Adams commented on GitHub (Mar 20, 2025):

Nice link. But I asked for clarification. And that is not an answer to my question. Look at the API Document dude. It showed that you embed this, "Why is the sky blue?" Does it make any sense to embed a question for retrieval? Like what the heck?!

https://github.com/ollama/ollama/blob/main/docs/api.md#generate-embeddings

Here's what it says:

Generate Embeddings
POST /api/embed
Generate embeddings from a model

Parameters
model: name of model to generate embeddings from
input: text or list of text to generate embeddings for
Advanced parameters:

truncate: truncates the end of each input to fit within context length. Returns error if false and context length is exceeded. Defaults to true
options: additional model parameters listed in the documentation for the Modelfile such as temperature
keep_alive: controls how long the model will stay loaded into memory following the request (default: 5m)
Examples
Request
curl http://localhost:11434/api/embed -d '{
"model": "all-minilm",
"input": "Why is the sky blue?"
}'
Response
{
"model": "all-minilm",
"embeddings": [[
0.010071029, -0.0017594862, 0.05007221, 0.04692972, 0.054916814,
0.008599704, 0.105441414, -0.025878139, 0.12958129, 0.031952348
]],
"total_duration": 14143917,
"load_duration": 1019500,
"prompt_eval_count": 8
}

So there's the response from this. A vector database. Now I ask again. How do you use? Like how do I get the AI to respond with this data?

@JG-Adams commented on GitHub (Mar 20, 2025): Nice link. But I asked for clarification. And that is not an answer to my question. Look at the API Document dude. It showed that you embed this, "Why is the sky blue?" Does it make any sense to embed a question for retrieval? Like what the heck?! [https://github.com/ollama/ollama/blob/main/docs/api.md#generate-embeddings](url) Here's what it says: Generate Embeddings POST /api/embed Generate embeddings from a model Parameters model: name of model to generate embeddings from input: text or list of text to generate embeddings for Advanced parameters: truncate: truncates the end of each input to fit within context length. Returns error if false and context length is exceeded. Defaults to true options: additional model parameters listed in the documentation for the [Modelfile](https://github.com/ollama/ollama/blob/main/docs/modelfile.md#valid-parameters-and-values) such as temperature keep_alive: controls how long the model will stay loaded into memory following the request (default: 5m) Examples Request curl http://localhost:11434/api/embed -d '{ "model": "all-minilm", "input": "Why is the sky blue?" }' Response { "model": "all-minilm", "embeddings": [[ 0.010071029, -0.0017594862, 0.05007221, 0.04692972, 0.054916814, 0.008599704, 0.105441414, -0.025878139, 0.12958129, 0.031952348 ]], "total_duration": 14143917, "load_duration": 1019500, "prompt_eval_count": 8 } So there's the response from this. A vector database. Now I ask again. How do you use? Like how do I get the AI to respond with this data?

GiteaMirror commented

2026-04-12 18:03:34 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

Does it make any sense to embed a question for retrieval?

Why not? The purpose of the RAG system might be to find questions that are similar. So you get the embedding for "Why is the sky blue?" and put it in the vector database. You add other questions like "Why is the grass green?","Why is the sunset orange?" and "Why do dogs have tails?". Then somebody has a query about questions pertaining to colours of natural phenomena. You can query the vector database for vectors that are similar to the vector for "Why is the sky blue?" and then rank the results on the cosine similarity of the returned vectors, and you will get blue sky, green grass, orange sunset but not dog tails.

So there's the response from this. A vector database. Now I ask again. How do you use? Like how do I get the AI to respond with this data?

The AI doesn't respond to this data. You put the vectors in a database, see "Indexing" in the provided link. Then a question is asked. The question is turned into a vector and used to query the vector database, see "Retrieval". The database query returns a list of vectors that match the query vector. Those vectors are ranked and the associated documents scored. Then the original question and the documents are passed to the model ("Augmentation") and the response from the model ("Generation") is returned to the client as a response to the question.

@rick-github commented on GitHub (Mar 20, 2025): > Does it make any sense to embed a question for retrieval? Why not? The purpose of the RAG system might be to find questions that are similar. So you get the embedding for "Why is the sky blue?" and put it in the vector database. You add other questions like "Why is the grass green?","Why is the sunset orange?" and "Why do dogs have tails?". Then somebody has a query about questions pertaining to colours of natural phenomena. You can query the vector database for vectors that are similar to the vector for "Why is the sky blue?" and then rank the results on the cosine similarity of the returned vectors, and you will get blue sky, green grass, orange sunset but not dog tails. > So there's the response from this. A vector database. Now I ask again. How do you use? Like how do I get the AI to respond with this data? The AI doesn't respond to this data. You put the vectors in a database, see "Indexing" in the provided link. Then a question is asked. The question is turned into a vector and used to query the vector database, see "Retrieval". The database query returns a list of vectors that match the query vector. Those vectors are ranked and the associated documents scored. Then the original question and the documents are passed to the model ("Augmentation") and the response from the model ("Generation") is returned to the client as a response to the question.

GiteaMirror commented

2026-04-12 18:03:35 -05:00

@JG-Adams commented on GitHub (Mar 20, 2025):

Does it make any sense to embed a question for retrieval?

Why not? The purpose of the RAG system might be to find questions that are similar. So you get the embedding for "Why is the sky blue?" and put it in the vector database. You add other questions like "Why is the grass green?","Why is the sunset orange?" and "Why do dogs have tails?". Then somebody has a query about questions pertaining to colours of natural phenomena. You can query the vector database for vectors that are similar to the vector for "Why is the sky blue?" and then rank the results on the cosine similarity of the returned vectors, and you will get blue sky, green grass, orange sunset but not dog tails.

So there's the response from this. A vector database. Now I ask again. How do you use? Like how do I get the AI to respond with this data?

The AI doesn't respond to this data. You put the vectors in a database, see "Indexing" in the provided link. Then a question is asked. The question is turned into a vector and used to query the vector database, see "Retrieval". The database query returns a list of vectors that match the query vector. Those vectors are ranked and the associated documents scored. Then the original question and the documents are passed to the model ("Augmentation") and the response from the model ("Generation") is returned to the client as a response to the question.

HOW NOT TO UNDERSTAND PEOPLE'S QUESTION.

You said, "The AI doesn't respond to this data." Holy cow dude. I said "with" the data. Not "to" it. What I'm looking for turned out to be query. How to query it. Now why not you say? Is it helpful to look for similarity to a question? The whole point of RAG is to retrieve the information that could be helpful to answer a user's question. Like for example we now know Saturn to have the most moon. But AI by itself may only know Jupiter to have the most moon. Which is an outdated piece of information. Why do I gotta spell everything out for you? I'm not here to talk about how RAG work. Learn to read.
Seriously now. What are you even doing???

@JG-Adams commented on GitHub (Mar 20, 2025): > > Does it make any sense to embed a question for retrieval? > > Why not? The purpose of the RAG system might be to find questions that are similar. So you get the embedding for "Why is the sky blue?" and put it in the vector database. You add other questions like "Why is the grass green?","Why is the sunset orange?" and "Why do dogs have tails?". Then somebody has a query about questions pertaining to colours of natural phenomena. You can query the vector database for vectors that are similar to the vector for "Why is the sky blue?" and then rank the results on the cosine similarity of the returned vectors, and you will get blue sky, green grass, orange sunset but not dog tails. > > > So there's the response from this. A vector database. Now I ask again. How do you use? Like how do I get the AI to respond with this data? > > The AI doesn't respond to this data. You put the vectors in a database, see "Indexing" in the provided link. Then a question is asked. The question is turned into a vector and used to query the vector database, see "Retrieval". The database query returns a list of vectors that match the query vector. Those vectors are ranked and the associated documents scored. Then the original question and the documents are passed to the model ("Augmentation") and the response from the model ("Generation") is returned to the client as a response to the question. HOW NOT TO UNDERSTAND PEOPLE'S QUESTION. You said, "The AI doesn't respond to this data." Holy cow dude. I said "with" the data. Not "to" it. What I'm looking for turned out to be query. How to query it. Now why not you say? Is it helpful to look for similarity to a question? The whole point of RAG is to retrieve the information that could be helpful to answer a user's question. Like for example we now know Saturn to have the most moon. But AI by itself may only know Jupiter to have the most moon. Which is an outdated piece of information. Why do I gotta spell everything out for you? I'm not here to talk about how RAG work. Learn to read. Seriously now. What are you even doing???

GiteaMirror commented

2026-04-12 18:03:35 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

My understanding is you want to use a RAG system to answer questions.

The whole point of RAG is to retrieve the information that could be helpful to answer a user's question.

So this is how to use RAG to answer a question about moons:

The information about the moons of Saturn ("Saturn has 274 moons") is processed into an embedding (/api/embed). The embedding is inserted in a vector database ("Indexing") with a pointer to the document from which embedding was generated. Then a user has a question about Saturnian moons ("How many moons does Saturn have?"). The question is converted to an embedding and used to query the vector database ("Retrieval"). The database returns a list of vectors and associated documents that are close matches to the query vector. One of those vectors corresponds to the document that contains "Saturn has 274 moons". Now the RAG system passes the original question ("How many moons does Saturn have?") and the retrieved documents ("Saturn has 274 moons" and others that had a close vector match but might not be as relevant as the first one) to the LLM ("Augmentation"). The response from the model ("Generation") is returned to the user as a response to the question.

If this doesn't help with your original question of How do you actually use RAG then please feel free to ask follow up questions.

@rick-github commented on GitHub (Mar 20, 2025): My understanding is you want to use a RAG system to answer questions. > The whole point of RAG is to retrieve the information that could be helpful to answer a user's question. So this is how to use RAG to answer a question about moons: The information about the moons of Saturn ("Saturn has 274 moons") is processed into an embedding (`/api/embed`). The embedding is inserted in a vector database ("Indexing") with a pointer to the document from which embedding was generated. Then a user has a question about Saturnian moons ("How many moons does Saturn have?"). The question is converted to an embedding and used to query the vector database ("Retrieval"). The database returns a list of vectors and associated documents that are close matches to the query vector. One of those vectors corresponds to the document that contains "Saturn has 274 moons". Now the RAG system passes the original question ("How many moons does Saturn have?") and the retrieved documents ("Saturn has 274 moons" and others that had a close vector match but might not be as relevant as the first one) to the LLM ("Augmentation"). The response from the model ("Generation") is returned to the user as a response to the question. If this doesn't help with your original question of `How do you actually use RAG` then please feel free to ask follow up questions.

GiteaMirror commented

2026-04-12 18:03:36 -05:00

@JG-Adams commented on GitHub (Mar 20, 2025):

I want to be clear that I didn't come to stackoverflow to be given a link. I'm here to talk about some missing info in our API document.
So forget about the wikipedia page. Look at the API document for embedding and tell me if that is all the steps you take to do what you just described.

You have explained how it work. Now I want to know how to use it. There's a difference. Like putting it into practical use in CODE.

As I try to understand, here's what I get from your last response:

Embed "Saturn has 274 moons" (It gets inserted into a vector database and automatically point to it?)
You ask a question. "How many moons does Saturn have?" (Assuming it's using the newly embedded info)
It goes through the vector database for similarity and answer with it.

Is that it? I gave it a go and it did not work. So clearly something is missing. Like how to use the embedded data for our user prompted question?

@JG-Adams commented on GitHub (Mar 20, 2025): I want to be clear that I didn't come to stackoverflow to be given a link. I'm here to talk about some missing info in our API document. So forget about the wikipedia page. Look at the API document for embedding and tell me if that is all the steps you take to do what you just described. You have explained how it work. Now I want to know how to use it. There's a difference. Like putting it into practical use in CODE. As I try to understand, here's what I get from your last response: 1. Embed "Saturn has 274 moons" (It gets inserted into a vector database and automatically point to it?) 2. You ask a question. "How many moons does Saturn have?" (Assuming it's using the newly embedded info) 3. It goes through the vector database for similarity and answer with it. Is that it? I gave it a go and it did not work. So clearly something is missing. Like how to use the embedded data for our user prompted question?

GiteaMirror commented

2026-04-12 18:03:36 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

I gave it a go and it did not work

If you show the code then perhaps we could debug it.

@rick-github commented on GitHub (Mar 20, 2025): > I gave it a go and it did not work If you show the code then perhaps we could debug it.

GiteaMirror commented

2026-04-12 18:03:38 -05:00

@JG-Adams commented on GitHub (Mar 20, 2025):

Thanks for your patience.
I'm using Ollama-hpp. for C++.
Here is the site: https://github.com/jmont-dev/ollama-hpp

I didn't expect this to work at all.

#include "ollama.hpp"
#include "json.hpp"
int main()
{
std::string Model = "llama3.2:latest";
ollama::show_requests(true);
ollama::show_replies(true);
std::cout << ollama::generate_embeddings(Model, "Saturn has 274 moons.") << std::endl;
std::cout << ollama::generate(Model, "How many moons does Saturn has?") << std::endl;
return 0;
}

@JG-Adams commented on GitHub (Mar 20, 2025): Thanks for your patience. I'm using Ollama-hpp. for C++. Here is the site: [https://github.com/jmont-dev/ollama-hpp](url) I didn't expect this to work at all. #include "ollama.hpp" #include "json.hpp" int main() { std::string Model = "llama3.2:latest"; ollama::show_requests(true); ollama::show_replies(true); std::cout << ollama::generate_embeddings(Model, "Saturn has 274 moons.") << std::endl; std::cout << ollama::generate(Model, "How many moons does Saturn has?") << std::endl; return 0; }

GiteaMirror commented

2026-04-12 18:03:39 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

OK, as I said at the start, ollama is not a RAG system, it is a component. You need other components to make a RAG system, one of which is a vector database. I know you don't want a link but I feel there's a knowledge gap here that could be helped by reading through an example: https://huggingface.co/blog/ngxson/make-your-own-rag. This is in python but the fundamentals apply: embeddings, storing vectors in a (very simple) database, lookups and generation.

@rick-github commented on GitHub (Mar 20, 2025): OK, as I said at the start, ollama is not a RAG system, it is a component. You need other components to make a RAG system, one of which is a vector database. I know you don't want a link but I feel there's a knowledge gap here that could be helped by reading through an example: https://huggingface.co/blog/ngxson/make-your-own-rag. This is in python but the fundamentals apply: embeddings, storing vectors in a (very simple) database, lookups and generation.

GiteaMirror commented

2026-04-12 18:03:40 -05:00

@JG-Adams commented on GitHub (Mar 20, 2025):

Thank you for your help. That is vital piece of information. I managed to convert it to C++ and it worked. Fantastic. They don't seem to have a C++ solution out there do they?

As a reward for your assistance. I think I will make a github site to share my codes after I polish it a bit.

As for all the confusion I got regarding the API document. I still think it could use some refinement. There is no indication that embedding is the first step to RAG and it needs an implementation for it. Honestly I'm not sure how it should be exactly.

@JG-Adams commented on GitHub (Mar 20, 2025): Thank you for your help. That is vital piece of information. I managed to convert it to C++ and it worked. Fantastic. They don't seem to have a C++ solution out there do they? As a reward for your assistance. I think I will make a github site to share my codes after I polish it a bit. As for all the confusion I got regarding the API document. I still think it could use some refinement. There is no indication that embedding is the first step to RAG and it needs an implementation for it. Honestly I'm not sure how it should be exactly.

GiteaMirror commented

2026-04-12 18:03:42 -05:00

@rick-github commented on GitHub (Mar 20, 2025):

They don't seem to have a C++ solution out there do they?

There likely is but I haven't touched C++ in about 10 years so I don't have any recommendations.

There is no indication that embedding is the first step to RAG

It's not really the province of ollama to create tutorials on how to implement external systems, whether it's RAG or chatbots or vision analysis systems. That's where examples like the huggingface link or information resources like Wikipedia come in.

@rick-github commented on GitHub (Mar 20, 2025): > They don't seem to have a C++ solution out there do they? There likely is but I haven't touched C++ in about 10 years so I don't have any recommendations. > There is no indication that embedding is the first step to RAG It's not really the province of ollama to create tutorials on how to implement external systems, whether it's RAG or chatbots or vision analysis systems. That's where examples like the huggingface link or information resources like Wikipedia come in.

GiteaMirror commented

2026-04-12 18:03:43 -05:00

@JG-Adams commented on GitHub (Mar 20, 2025):

I agree. But what I'm really saying is. The fact that it is only a piece of the puzzle to having RAG is actually good to know. Cause it's not saying anything at all about what it's good for. The word "RAG" isn't even mentioned at all in the doc.

Looking it up I couldn't find any such implementation. Not even perplexity is aware of it. I'm sure people will appreciate this.
Since the code was free I assume the converted one should also be free. What license should I use? MIT?

@JG-Adams commented on GitHub (Mar 20, 2025): I agree. But what I'm really saying is. The fact that it is only a piece of the puzzle to having RAG is actually good to know. Cause it's not saying anything at all about what it's good for. The word "RAG" isn't even mentioned at all in the doc. Looking it up I couldn't find any such implementation. Not even perplexity is aware of it. I'm sure people will appreciate this. Since the code was free I assume the converted one should also be free. What license should I use? MIT?

GiteaMirror commented

2026-04-12 18:03:44 -05:00

@JG-Adams commented on GitHub (Mar 21, 2025):

Ok I did it.
https://github.com/JG-Adams/RAGcpp
Hope this is good.

Also thank you very much for your help!

@JG-Adams commented on GitHub (Mar 21, 2025): Ok I did it. https://github.com/JG-Adams/RAGcpp Hope this is good. Also thank you very much for your help!

GiteaMirror referenced this issue

2026-04-12 23:50:09 -05:00

[PR #6484] [MERGED] Only enable numa on CPUs #12125

GiteaMirror referenced this issue

2026-04-16 06:01:33 -05:00

[PR #6484] [MERGED] Only enable numa on CPUs #17396

GiteaMirror referenced this issue

2026-04-19 16:28:14 -05:00

[PR #6484] [MERGED] Only enable numa on CPUs #22665

GiteaMirror referenced this issue

2026-04-22 09:03:12 -05:00

[GH-ISSUE #6425] optimize numa behavior for large models with GPU and CPU inference - numa_balancing on GPU causes excessively slow load times #29800

GiteaMirror referenced this issue

2026-04-22 22:40:16 -05:00

[PR #6484] [MERGED] Only enable numa on CPUs #37998

GiteaMirror referenced this issue

2026-04-24 23:00:45 -05:00

[PR #6484] [MERGED] Only enable numa on CPUs #43373

GiteaMirror referenced this issue

2026-04-28 16:22:45 -05:00

[GH-ISSUE #6425] optimize numa behavior for large models with GPU and CPU inference - numa_balancing on GPU causes excessively slow load times #50551

GiteaMirror referenced this issue

2026-04-29 13:43:27 -05:00

[PR #6484] [MERGED] Only enable numa on CPUs #58822

GiteaMirror referenced this issue

2026-05-03 23:52:28 -05:00

[GH-ISSUE #6425] optimize numa behavior for large models with GPU and CPU inference - numa_balancing on GPU causes excessively slow load times #66077

GiteaMirror referenced this issue

2026-05-05 06:29:32 -05:00

[PR #6484] [MERGED] Only enable numa on CPUs #74419

GiteaMirror referenced this issue

2026-05-09 12:06:54 -05:00

[GH-ISSUE #6425] optimize numa behavior for large models with GPU and CPU inference - numa_balancing on GPU causes excessively slow load times #81720

Sign in to join this conversation.

Branches Tags

main

hoyyeva/fix-claude-channels-env

parth-update-hermes-launch

hoyyeva/vscode-extension-docs-update

parth-gemma4-chat-template-renderer

parth-api-status-context-length

hoyyeva/wire-up-context-length

hoyyeva/claude-code-context-doc

jmorganca/investigate-issue-17046

hoyyeva/hermes-docs

jmorganca/agent-loop-style

hoyyeva/openclaw

parth-agent-loop

hoyyeva/ollama-vscode-extension

brucemacd/cache-metrics

brucemacd/hermes-desktop

hoyyeva/docs-vscode

parth-input-style-experiment

brucemacd/docs-glm52

hoyyeva/poc-docs

Parth/mlx-launch-recommendations

parth-first-time-app-cli-experience

test/darwin-xcode-pin

improve-cloud-model-recommendations

hoyyeva/goose-docs

jmorganca/context-limit-fixes

hoyyeva/qwen-doc

hoyyeva/vscode-docs

jmorganca/remove-mlx-imagegen-code

parth-copilot-token-length-defaults

hoyyeva/poolside-windows

laguna-support

jmorganca/harden-markdown-rendering

laguna-renderer-parser

laguna-llamacpp

codex/make-integration-hidden-and-lunchable

brucemacd/omp-docs

pdevine/gguf-mtp-oldstyle

hoyyeva/migrate-pi

hoyyeva/anthropic-local-image-path

parth-launch-codex-app

hoyyeva/anthropic-reference-images-path

parth-anthropic-reference-images-path

brucemacd/download-before-remove

hoyyeva/editor-config-repair

parth-mlx-decode-checkpoints

parth/hide-claude-desktop-till-release

parth-add-claude-code-autoinstall

release_v0.22.0

pdevine/manifest-list

codex/fix-codex-model-metadata-warning

pdevine/addressable-manifest

brucemacd/launch-fetch-reccomended

jmorganca/llama-compat

launch-copilot-cli

release_v0.20.7

parth-auto-save-backup

parth-test

jmorganca/gemma4-audio-replacements

fix-manifest-digest-on-pull

hoyyeva/vscode-improve

brucemacd/install-server-wait

parth/update-claude-docs

brucemac/start-ap-install

pdevine/mlx-update

pdevine/qwen35_vision

drifkin/api-show-fallback

mintlify/image-generation-1773352582

hoyyeva/server-context-length-local-config

jmorganca/faster-reptition-penalties

jmorganca/convert-nemotron

parth-pi-thinking

pdevine/sampling-penalties

jmorganca/fix-create-quantization-memory

dongchen/resumable_transfer_fix

pdevine/sampling-cache-error

jessegross/mlx-usage

hoyyeva/openclaw-config

hoyyeva/app-html

pdevine/qwen3next

brucemacd/sign-sh-install

brucemacd/tui-update

brucemacd/usage-api

jmorganca/launch-empty

fix-app-dist-embed

mxyng/mlx-compile

mxyng/mlx-quant

mxyng/mlx-glm4.7

mxyng/mlx

brucemacd/simplify-model-picker

jmorganca/qwen3-concurrent

fix-glm-4.7-flash-mla-config

drifkin/qwen3-coder-opening-tag

brucemacd/usage-cli

fix-cuda12-fattn-shmem

ollama-imagegen-docs

parth/fix-multiline-inputs

brucemacd/config-docs

mxyng/model-files

mxyng/simple-execute

fix-imagegen-ollama-models

mxyng/async-upload

jmorganca/lazy-no-dtype-changes

imagegen-auto-detect-create

parth/decrease-concurrent-download-hf

fix-mlx-quantize-init

jmorganca/x-cleanup

usage

imagegen-readme

jmorganca/glm-image

mlx-gpu-cd

jmorganca/imagegen-modelfile

parth/agent-skills

parth/agent-allowlist

parth/signed-in-offline

parth/agents

parth/fix-context-chopping

improve-cloud-flow

parth/add-models-websearch

parth/prompt-renderer-mcp

jmorganca/native-settings

jmorganca/download-stream-hash

jmorganca/client2-rebased

brucemacd/oai-chat-req-multipart

jessegross/multi_chunk_reserve

grace/additional-omit-empty

grace/mistral-3-large

mxyng/tokenizer2

mxyng/tokenizer

jessegross/flash

hoyyeva/windows-nacked-app

mxyng/cleanup-attention

grace/deepseek-parser

hoyyeva/remember-unsent-prompt

parth/add-lfs-pointer-error-conversion

parth/olmo2-test2

hoyyeva/ollama-launchagent-plist

nicole/olmo-model

parth/olmo-test

mxyng/remove-embedded

parth/render-template

jmorganca/intellect-3

parth/remove-prealloc-linter

jmorganca/cmd-eval

nicole/nomic-embed-text-fix

mxyng/lint-2

hoyyeva/add-gemini-3-pro-preview

hoyyeva/load-model-list

mxyng/expand-path

mxyng/environ-2

hoyyeva/deeplink-json-encoding

parth/improve-tool-calling-tests

hoyyeva/conversation

hoyyeva/assistant-edit-response

hoyyeva/thinking

origin/brucemacd/invalid-char-i-err

parth/improve-tool-calling

jmorganca/required-omitempty

grace/qwen3-vl-tests

mxyng/iter-client

parth/docs-readme

nicole/embed-test

pdevine/integration-benchstat

parth/remove-generate-cmd

parth/add-toolcall-id

mxyng/server-tests

jmorganca/glm-4.6

jmorganca/gin-h-compat

drifkin/stable-tool-args

pdevine/qwen3-more-thinking

parth/add-websearch-client

nicole/websearch_local

jmorganca/qwen3-coder-updates

grace/deepseek-v3-migration-tests

mxyng/fix-create

jmorganca/cloud-errors

pdevine/parser-tidy

revert-12233-parth/simplify-entrypoints-runner

parth/enable-so-gpt-oss

brucemacd/qwen3vl

jmorganca/readme-simplify

parth/gpt-oss-structured-outputs

revert-12039-jmorganca/tools-braces

mxyng/embeddings

mxyng/gguf

mxyng/benchmark

mxyng/types-null

parth/move-parsing

mxyng/gemma2

jmorganca/docs

mxyng/16-bit

mxyng/create-stdin

pdevine/authorizedkeys

mxyng/quant

parth/opt-in-error-context-window

brucemacd/cache-models

brucemacd/runner-completion

jmorganca/llama-update-6

brucemacd/benchmark-list

brucemacd/partial-read-caps

parth/deepseek-r1-tools

mxyng/omit-array

parth/tool-prefix-temp

brucemacd/runner-test

jmorganca/qwen25vl

brucemacd/model-forward-test-ext

parth/python-function-parsing

jmorganca/cuda-compression-none

drifkin/num-parallel

drifkin/chat-truncation-fix

jmorganca/sync

parth/python-tools-calling

drifkin/array-head-count

brucemacd/create-no-loop

parth/server-enable-content-stream-with-tools

qwen25omni

mxyng/v3

brucemacd/ropeconfig

jmorganca/silence-tokenizer

parth/sample-so-test

parth/sampling-structured-outputs

brucemacd/doc-go-engine

parth/constrained-sampling-json

jmorganca/mistral-wip

brucemacd/mistral-small-convert

parth/sample-unmarshal-json-for-params

brucemacd/jomorganca/mistral

pdevine/bfloat16

jmorganca/mistral

brucemacd/mistral

pdevine/logging

parth/sample-correctness-fix

parth/sample-fix-sorting

jmorgan/sample-fix-sorting-extras

jmorganca/temp-0-images

brucemacd/parallel-embed-models

brucemacd/shim-grammar

jmorganca/fix-gguf-error

bmizerany/nameswork

jmorganca/faster-releases

bmizerany/validatenames

brucemacd/err-no-vocab

brucemacd/rope-config

brucemacd/err-hint

brucemacd/qwen2_5

brucemacd/logprobs

brucemacd/new_runner_graph_bench

progress-flicker

brucemacd/forward-test

brucemacd/go_qwen2

pdevine/gemma2

jmorganca/add-missing-symlink-eval

mxyng/next-debug

parth/set-context-size-openai

brucemacd/next-bpe-bench

brucemacd/next-bpe-test

brucemacd/new_runner_e2e

brucemacd/new_runner_qwen2

pdevine/convert-cohere2

brucemacd/convert-cli

parth/log-probs

mxyng/next-mlx

mxyng/cmd-history

parth/templating

parth/tokenize-detokenize

brucemacd/check-key-register

bmizerany/grammar

jmorganca/vendor-081b29bd

mxyng/func-checks

jmorganca/fix-null-format

parth/fix-default-to-warn-json

jmorganca/qwen2vl

jmorganca/no-concat

parth/cmd-cleanup-SO

brucemacd/check-key-register-structured-err

parth/openai-stream-usage

parth/fix-referencing-so

stream-tools-stop

jmorganca/degin-1

brucemacd/install-path-clean

brucemacd/push-name-validation

brucemacd/browser-key-register

jmorganca/openai-fix-first-message

jmorganca/fix-proxy

jessegross/sample

parth/disallow-streaming-tools

dhiltgen/remove_submodule

jmorganca/ga

jmorganca/mllama

pdevine/newlines

pdevine/geems-2b

jmorganca/llama-bump

mxyng/modelname-7

mxyng/gin-slog

mxyng/modelname-6

jyan/convert-prog

jyan/quant5

paligemma-support

pdevine/import-docs

jmorganca/openai-context

jyan/paligemma

jyan/p2

jyan/palitest

bmizerany/embedspeedup

jmorganca/llama-vit

brucemacd/allow-ollama

royh/ep-methods

royh/whisper

mxyng/api-models

mxyng/fix-memory

jyan/q4_4/8

jyan/ollama-v

royh/stream-tools

roy-embed-parallel

bmizerany/hrm

revert-5963-revert-5924-mxyng/llama3.1-rope

royh/embed-viz

jyan/local2

jyan/auth

jyan/local

jyan/parse-temp

jmorganca/template-mistral

jyan/reord-g

royh-openai-suffixdocs

royh-imgembed

royh-embed-parallel

jyan/quant4

royh-precision

jyan/progress

pdevine/fix-template

jyan/quant3

pdevine/ggla

mxyng/update-registry-domain

jmorganca/ggml-static

mxyng/create-context

jyan/v0.146

mxyng/layers-from-files

build_dist

bmizerany/noseek

royh-ls

royh-name

timeout

mxyng/server-timestamp

bmizerany/nosillyggufslurps

royh-params

jmorganca/llama-cpp-7c26775

royh-openai-delete

royh-show-rigid

jmorganca/enable-fa

jmorganca/no-error-template

jyan/format

royh-testdelete

bmizerany/fastverify

language_support

pdevine/ps-glitches

brucemacd/tokenize

bruce/iq-quants

bmizerany/filepathwithcoloninhost

mxyng/split-bin

bmizerany/client-registry

jmorganca/if-none-match

native

jmorganca/native

jmorganca/batch-embeddings

jmorganca/initcmake

jmorganca/mm

pdevine/showggmlinfo

modenameenforcealphanum

bmizerany/modenameenforcealphanum

jmorganca/done-reason

jmorganca/llama-cpp-8960fe8

ollama.com

bmizerany/filepathnobuild

bmizerany/types/model/defaultfix

rmdisplaylong

nogogen

bmizerany/x

modelfile-readme

bmizerany/replacecolon

jmorganca/limit

jmorganca/execstack

jmorganca/replace-assets

mxyng/tune-concurrency

jmorganca/testing

whitespace-detection

jmorganca/options

upgrade-all

scratch

cuda-search

mattw/airenamer

mattw/allmodelsonhuggingface

mattw/quantcontext

mattw/whatneedstorun

brucemacd/llama-mem-calc

mattw/faq-context

mattw/communitylinks

mattw/noprune

mattw/python-functioncalling

rename

mxyng/install

pulse

remove-first

editor

mattw/selfqueryingretrieval

cgo

mattw/howtoquant

api

matt/streamingapi

format-config

mxyng/extra-args

shell

update-nous-hermes

cp-model

upload-progress

fix-unknown-model

fix-model-names

delete-fix

insecure-registry

ls

deletemodels

progressbar

readme-updates

license-layers

skip-list

list-models

modelpath

matt/examplemodelfiles

distribution

go-opts

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/ollama#6484