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

[GH-ISSUE #14375] [Feature Proposal] Settings toggle to disable app auto-start #55856

New Issue
Open
opened 2026-04-29 09:48:50 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-29 09:48:50 -05:00
Owner
Copy Link

Originally created by @brpeterman on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14375

Summary

Today, the Windows and Mac Ollama apps automatically register themselves as startup items on the first run, but don't expose any way to undo that action. As discussed in #8783 and #14237, this is a user-unfriendly experience.

I propose to add a toggle to the app settings that controls this behavior.

UI

Image

Implementation

app/ui

  • Add endpoints to get and modify the state of the user's auto-start settings.

cmd/app

  • Remove automatic registration as a startup item from the windows and darwin platform-specific code, leaving the decision up to the user.

app/startup

  • New package that contains platform-specific logic for registering the app as a startup item.
  • This mostly just copies the existing startup code from cmd/app and adds new interfaces to get the current state and allow for deregistration.

Compatibility

  • For existing users, there is no automatic change to behavior. There's just a new toggle in the settings.
  • For new users, the app will not automatically start on login. Users will have the option to opt in using the toggle in the settings.

Documentation

  • Update the FAQ to point to the new setting instead of documenting platform-specific instructions.

Rollout

I can build everything listed here except for the backend Mac implementation, as I don't have a Mac. I can set up the infrastructure to make it simple for someone to come in and finish the job.

We can hide the new setting from any platforms that don't have a backend implementation yet, allowing for a seamless phased rollout.

Originally created by @brpeterman on GitHub (Feb 23, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14375 ### Summary Today, the Windows and Mac Ollama apps automatically register themselves as startup items on the first run, but don't expose any way to undo that action. As discussed in #8783 and #14237, this is a user-unfriendly experience. I propose to add a toggle to the app settings that controls this behavior. ### UI <img width="986" height="741" alt="Image" src="https://github.com/user-attachments/assets/761c2e6d-2138-4313-b3a6-3b22bf7da54b" /> ### Implementation #### app/ui - Add endpoints to get and modify the state of the user's auto-start settings. #### cmd/app - Remove automatic registration as a startup item from the windows and darwin platform-specific code, leaving the decision up to the user. #### app/startup - New package that contains platform-specific logic for registering the app as a startup item. - This mostly just copies the existing startup code from cmd/app and adds new interfaces to get the current state and allow for deregistration. ### Compatibility - For existing users, there is no automatic change to behavior. There's just a new toggle in the settings. - For new users, the app will not automatically start on login. Users will have the option to opt in using the toggle in the settings. ### Documentation - Update the [FAQ](https://github.com/ollama/ollama/blob/main/docs/faq.mdx#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer) to point to the new setting instead of documenting platform-specific instructions. ### Rollout I can build everything listed here except for the backend Mac implementation, as I don't have a Mac. I can set up the infrastructure to make it simple for someone to come in and finish the job. We can hide the new setting from any platforms that don't have a backend implementation yet, allowing for a seamless phased rollout.
GiteaMirror added the feature request label 2026-04-29 09:48:50 -05:00
GiteaMirror commented 2026-04-29 09:48:51 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Feb 23, 2026):

https://github.com/ollama/ollama/blob/main/docs/faq.mdx#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer

<!-- gh-comment-id:3945901222 --> @rick-github commented on GitHub (Feb 23, 2026): https://github.com/ollama/ollama/blob/main/docs/faq.mdx#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer
GiteaMirror commented 2026-04-29 09:48:52 -05:00
Author
Owner
Copy Link

@brpeterman commented on GitHub (Feb 26, 2026):

Any maintainers have any feedback? I can submit a PR if I get the green light.

<!-- gh-comment-id:3963636417 --> @brpeterman commented on GitHub (Feb 26, 2026): Any maintainers have any feedback? I can submit a PR if I get the green light.
GiteaMirror commented 2026-04-29 09:48:52 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Feb 26, 2026):

Submit the PR, it's easier to discuss implementation details with concrete code.

<!-- gh-comment-id:3964844562 --> @rick-github commented on GitHub (Feb 26, 2026): Submit the PR, it's easier to discuss implementation details with concrete code.
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#55856
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?