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

[GH-ISSUE #12436] Option to disable all Cloud and remote Search features #8260

New Issue
Closed
opened 2026-04-12 20:47:40 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-12 20:47:40 -05:00
Owner
Copy Link

Originally created by @dragetd on GitHub (Sep 28, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12436

I understand why Ollama added remote model loading, cloud hosting, and search support. It helps finance development and provides convenience for many users.

However, a core reason for using Ollama is strong privacy and the guarantee of running models locally without any unwanted remote connections (except explicitly configured tool calls). For users with this priority, it would be very valuable to have a configuration option that completely disables all remote/cloud features.

I’m aware that without a login or token these features do not activate. Still, an explicit “local-only” mode would act as a safeguard.

Example:
A second admin, a misconfiguration, or buggy software might introduce a token or cloud model without my knowledge.

Even if unintentional and non-malicious, this could break the privacy expectation.

An explicit toggle/setting to enforce local-only operation would provide additional peace of mind for privacy-conscious users.

Originally created by @dragetd on GitHub (Sep 28, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12436 I understand why Ollama added remote model loading, cloud hosting, and search support. It helps finance development and provides convenience for many users. However, a core reason for using Ollama is strong privacy and the guarantee of running models locally without any unwanted remote connections (except explicitly configured tool calls). For users with this priority, it would be very valuable to have a configuration option that completely disables all remote/cloud features. I’m aware that without a login or token these features do not activate. Still, an explicit “local-only” mode would act as a safeguard. Example: A second admin, a misconfiguration, or buggy software might introduce a token or cloud model without my knowledge. Even if unintentional and non-malicious, this could break the privacy expectation. An explicit toggle/setting to enforce local-only operation would provide additional peace of mind for privacy-conscious users.
GiteaMirror added the feature request label 2026-04-12 20:47:40 -05:00
GiteaMirror commented 2026-04-12 20:47:42 -05:00
Author
Owner
Copy Link

@TungstenWolframite commented on GitHub (Sep 28, 2025):

Is airplane mode in settings what you are looking for?
It says it keeps data local, disabling cloud models and web search.

<!-- gh-comment-id:3343298805 --> @TungstenWolframite commented on GitHub (Sep 28, 2025): Is airplane mode in settings what you are looking for? It says it keeps data local, disabling cloud models and web search.
GiteaMirror commented 2026-04-12 20:47:42 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Sep 28, 2025):

Even with an explicit toggle/setting to enforce local-only operation, a second admin, a misconfiguration, or buggy software could break the privacy expectation. Better to firewall off or airgap the machine.

<!-- gh-comment-id:3343303050 --> @rick-github commented on GitHub (Sep 28, 2025): Even with an explicit toggle/setting to enforce local-only operation, a second admin, a misconfiguration, or buggy software could break the privacy expectation. Better to firewall off or airgap the machine.
GiteaMirror commented 2026-04-12 20:47:43 -05:00
Author
Owner
Copy Link

@dragetd commented on GitHub (Sep 28, 2025):

True, a malicious actor could just change the option. But being forgetful, an accident etc., I think the 'no phoning home' and 'no code to leak your prompts' value proposition is an important part of ollama.

And a simple firewall does not help, if you still want to download models or use it with other software. You'd need a WAF/filter proxy, which is beyond what most people would set up.

I understand that it might be a niche request and if you want to close the issue, please feel free. I still love hte project. :)

<!-- gh-comment-id:3344257334 --> @dragetd commented on GitHub (Sep 28, 2025): True, a malicious actor could just change the option. But being forgetful, an accident etc., I think the 'no phoning home' and 'no code to leak your prompts' value proposition is an important part of ollama. And a simple firewall does not help, if you still want to download models or use it with other software. You'd need a WAF/filter proxy, which is beyond what most people would set up. I understand that it might be a niche request and if you want to close the issue, please feel free. I still love hte project. :)
GiteaMirror commented 2026-04-12 20:47:44 -05:00
Author
Owner
Copy Link

@laniakea64 commented on GitHub (Sep 30, 2025):

See also https://github.com/ollama/ollama/issues/12404

While waiting for a definitive answer, maybe try setting the environment variable OLLAMA_REMOTES to a value that cannot be a valid hostname (e.g. ! )? -

c47154c08d/envconfig/config.go (L284)

c47154c08d/server/routes.go (L1802-L1806)

c47154c08d/envconfig/config.go (L137-L146)

<!-- gh-comment-id:3349762224 --> @laniakea64 commented on GitHub (Sep 30, 2025): See also https://github.com/ollama/ollama/issues/12404 While waiting for a definitive answer, maybe try setting the environment variable `OLLAMA_REMOTES` to a value that cannot be a valid hostname (e.g. `!` )? - https://github.com/ollama/ollama/blob/c47154c08d59c93a653a2a798885a4a29bff71ee/envconfig/config.go#L284 https://github.com/ollama/ollama/blob/c47154c08d59c93a653a2a798885a4a29bff71ee/server/routes.go#L1802-L1806 https://github.com/ollama/ollama/blob/c47154c08d59c93a653a2a798885a4a29bff71ee/envconfig/config.go#L137-L146
GiteaMirror commented 2026-04-12 20:47:45 -05:00
Author
Owner
Copy Link

@dragetd commented on GitHub (Oct 11, 2025):

Thanks for the discussion so far. I guess there is not much to add. Feel free to close this issue!

<!-- gh-comment-id:3393034626 --> @dragetd commented on GitHub (Oct 11, 2025): Thanks for the discussion so far. I guess there is not much to add. Feel free to close this issue!
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#8260
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?