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 #283] Do not prompt to install CLI if already on $PATH #25886

New Issue
Closed
opened 2026-04-22 01:43:53 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-22 01:43:53 -05:00
Owner
Copy Link

Originally created by @justinmayer on GitHub (Aug 4, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/283

Originally assigned to: @jmorganca on GitHub.

When launching the Ollama application, a dialog window will appear and prompt you for administrative access in order to “install” the command line executable, which in practice means symlinking /Applications/Ollama.app/Contents/Resources/ollama to /usr/local/bin/ollama.

Observed Behavior

This dialog window appears even when ollama is already available elsewhere on $PATH. Presumably the check naively looks for /usr/local/bin/ollama, and if it is not found at that specific location, the aforementioned dialog window appears on each and every launch of the application.

Expected Behavior

If ollama is already available on $PATH, regardless of its specific location, the aforementioned dialog window should not appear.

Rationale

When installing new applications, I prefer not to grant such administrative permissions, particularly when the only purpose is to create a symlink into a protected directory. I therefore prefer to manage my $PATH myself and manually create such symlinks into places such as ~/.local/bin/ that do not require admin permissions. Others might even prefer to invoke the full path to /Applications/Ollama.app/Contents/Resources/ollama instead.

But as the situation currently stands, there is no way to stop this dialog from appearing, even when its intended purpose is entirely unnecessary.

Proposed Remediation

I suggest all three of the following be implemented posthaste:

  1. Do not show this dialog window if ollama is already available on $PATH.
  2. Put a button on the dialog window to skip the CLI symlink step.
  3. Put a checkbox on this dialog that says "Do not ask again" and record the result, so future application launches will not spawn the CLI symlink prompt.
Originally created by @justinmayer on GitHub (Aug 4, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/283 Originally assigned to: @jmorganca on GitHub. When launching the Ollama application, a dialog window will appear and prompt you for administrative access in order to “install” the command line executable, which in practice means symlinking `/Applications/Ollama.app/Contents/Resources/ollama` to `/usr/local/bin/ollama`. ## Observed Behavior This dialog window appears even when `ollama` is already available elsewhere on `$PATH`. Presumably the check naively looks for `/usr/local/bin/ollama`, and if it is not found at that specific location, the aforementioned dialog window appears on each and every launch of the application. ## Expected Behavior If `ollama` is already available on `$PATH`, regardless of its specific location, the aforementioned dialog window should _not_ appear. ## Rationale When installing new applications, I prefer not to grant such administrative permissions, particularly when the only purpose is to create a symlink into a protected directory. I therefore prefer to manage my `$PATH` myself and manually create such symlinks into places such as `~/.local/bin/` that do not require admin permissions. Others might even prefer to invoke the full path to `/Applications/Ollama.app/Contents/Resources/ollama` instead. But as the situation currently stands, there is no way to stop this dialog from appearing, even when its intended purpose is entirely unnecessary. ## Proposed Remediation I suggest all three of the following be implemented posthaste: 1. Do not show this dialog window if `ollama` is already available on `$PATH`. 2. Put a button on the dialog window to skip the CLI symlink step. 3. Put a checkbox on this dialog that says "Do not ask again" and record the result, so future application launches will not spawn the CLI symlink prompt.
GiteaMirror added the buggood first issuemacos labels 2026-04-22 01:43:54 -05:00
GiteaMirror commented 2026-04-22 01:43:55 -05:00
Author
Owner
Copy Link

@wrinkledeth commented on GitHub (Aug 14, 2023):

I am interested in this feature as well.

Devs, please, let us use ollama without needing to grant administrative access.

<!-- gh-comment-id:1678123828 --> @wrinkledeth commented on GitHub (Aug 14, 2023): I am interested in this feature as well. Devs, please, let us use ollama without needing to grant administrative access.
GiteaMirror commented 2026-04-22 01:43:56 -05:00
Author
Owner
Copy Link

@geensr commented on GitHub (Nov 6, 2023):

I would also prefer not to have to give admin rights only to get something on the Path. In fact an install in the per user Applications directory is much preferred.

<!-- gh-comment-id:1795195087 --> @geensr commented on GitHub (Nov 6, 2023): I would also prefer not to have to give admin rights only to get something on the Path. In fact an install in the per user Applications directory is much preferred.
GiteaMirror commented 2026-04-22 01:43:57 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (Feb 20, 2024):

Working on this. Ollama on Windows doesn't require administrative access at all – and we're hoping to do the same on macOS

<!-- gh-comment-id:1953324602 --> @jmorganca commented on GitHub (Feb 20, 2024): Working on this. Ollama on Windows doesn't require administrative access at all – and we're hoping to do the same on macOS
GiteaMirror commented 2026-04-22 01:43:57 -05:00
Author
Owner
Copy Link

@kjanko commented on GitHub (Feb 20, 2024):

Working on this. Ollama on Windows doesn't require administrative access at all – and we're hoping to do the same on macOS

If we manually create the symlink everything works fine - the issue is just getting prompted for the admin access. On managed company devices this is a huge issue.

<!-- gh-comment-id:1954112778 --> @kjanko commented on GitHub (Feb 20, 2024): > Working on this. Ollama on Windows doesn't require administrative access at all – and we're hoping to do the same on macOS If we manually create the symlink everything works fine - the issue is just getting prompted for the admin access. On managed company devices this is a huge issue.
GiteaMirror commented 2026-04-22 01:43:58 -05:00
Author
Owner
Copy Link

@arekdist commented on GitHub (Jun 7, 2024):

It's riddiculous to ask end user for admin permissions when opening app for the first time. Why not to implement all the required stuff (proper linking) during app installation? Because of this "feature" we had to block this app in our organization...

<!-- gh-comment-id:2154288862 --> @arekdist commented on GitHub (Jun 7, 2024): It's riddiculous to ask end user for admin permissions when opening app for the first time. Why not to implement all the required stuff (proper linking) during app installation? Because of this "feature" we had to block this app in our organization...
GiteaMirror commented 2026-04-22 01:43:58 -05:00
Author
Owner
Copy Link

@igorschlum commented on GitHub (Jun 7, 2024):

@arekdist I"m in charge of a international school facilities and we will face the same issue if we want to deploy Ollama.

<!-- gh-comment-id:2154393100 --> @igorschlum commented on GitHub (Jun 7, 2024): @arekdist I"m in charge of a international school facilities and we will face the same issue if we want to deploy Ollama.
GiteaMirror commented 2026-04-22 01:43:59 -05:00
Author
Owner
Copy Link

@arekdist commented on GitHub (Jun 14, 2024):

Are there any chances to fix this?
My devs are groaning with impatience...

<!-- gh-comment-id:2167922962 --> @arekdist commented on GitHub (Jun 14, 2024): Are there any chances to fix this? My devs are groaning with impatience...
GiteaMirror commented 2026-04-22 01:44:00 -05:00
Author
Owner
Copy Link

@4513ECHO commented on GitHub (Feb 28, 2025):

Is there any progress of this? I hope to use Ollama without the admin permission...

<!-- gh-comment-id:2690363912 --> @4513ECHO commented on GitHub (Feb 28, 2025): Is there any progress of this? I hope to use Ollama without the admin permission...
GiteaMirror commented 2026-04-22 01:44:00 -05:00
Author
Owner
Copy Link

@arekdist commented on GitHub (Mar 1, 2025):

I'm afraid not. In today's world I can see only "features" but stability and security is at the end of the list. Not only in Ollama world.

<!-- gh-comment-id:2692126843 --> @arekdist commented on GitHub (Mar 1, 2025): I'm afraid not. In today's world I can see only "features" but stability and security is at the end of the list. Not only in Ollama world.
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 bug good first issue macos
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#25886
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?