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 #11476] Add Auto-Update Settings (with Metered Connection Awareness) #7576

New Issue
Closed
opened 2026-04-12 19:40:11 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-12 19:40:11 -05:00
Owner
Copy Link

Originally created by @nakanakaii on GitHub (Jul 20, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11476

Currently, Ollama updates seem to happen automatically in the background. While this is convenient for many, it can be problematic for users on metered internet connections (like mobile hotspots or data roaming plans). An unexpected large update could consume a significant portion of their data allowance, or lead to unexpected costs or throttled service. There's also no clear way for users to know when an update is happening or to defer it.

I propose adding a dedicated section in Ollama's settings for "Update Preferences." This section would offer users more control over how and when updates occur. Specifically, I'd like to see the following options:

  1. Auto-update (Recommended): This would be the default behavior, similar to how it works now, ensuring users always have the latest features and security patches.
  2. Notify and Ask Before Downloading: When an update is available, Ollama would notify the user (e.g., via pop-up or system tray notification) and ask for permission before downloading it.
  3. Manual Updates Only: This option would disable automatic updates entirely. Users would then need to manually check for and initiate updates from within the Ollama application.

Crucially, regardless of the chosen auto-update setting, It'd be better if the update is never happening on metered connection.

Thanks for considering this!

Originally created by @nakanakaii on GitHub (Jul 20, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11476 Currently, Ollama updates seem to happen automatically in the background. While this is convenient for many, it can be problematic for users on metered internet connections (like mobile hotspots or data roaming plans). An unexpected large update could consume a significant portion of their data allowance, or lead to unexpected costs or throttled service. There's also no clear way for users to know when an update is happening or to defer it. I propose adding a dedicated section in Ollama's settings for "Update Preferences." This section would offer users more control over how and when updates occur. Specifically, I'd like to see the following options: 1. **Auto-update (Recommended):** This would be the default behavior, similar to how it works now, ensuring users always have the latest features and security patches. 2. **Notify and Ask Before Downloading:** When an update is available, Ollama would notify the user (e.g., via pop-up or system tray notification) and ask for permission before downloading it. 3. **Manual Updates Only:** This option would disable automatic updates entirely. Users would then need to manually check for and initiate updates from within the Ollama application. Crucially, regardless of the chosen auto-update setting, It'd be better if the update is never happening on metered connection. Thanks for considering this!
GiteaMirror added the feature request label 2026-04-12 19:40:11 -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 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#7576
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?