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

[GH-ISSUE #15604] More transparent permission flow for CLI installation on macOS using desktop app #72020

New Issue
Open
opened 2026-05-05 03:20:55 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-05 03:20:55 -05:00
Owner
Copy Link

Originally created by @jaywardell on GitHub (Apr 15, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15604

The issue
On first launch, the macOS app immediately triggers a system authentication prompt to install the ollama CLI. This happens without any prior explanation from the app itself.

From a user perspective (even a technical one), this feels abrupt:
• The system dialog appears with no context
• It’s not clear what is being installed
• It’s not clear where it’s being installed
• It’s not obvious that this is just creating a symlink

While this is explained in the documentation, not everyone reads the documentation.

Even though the behavior is safe and minimal, the lack of disclosure creates unnecessary friction and distrust.

Expected behavior (macOS conventions)
Apps that require elevated permissions—especially for system-level locations like /usr/local/bin—typically:
• Explain the action before triggering the system auth dialog
• Clearly state what will be installed and why
• Give the user a chance to opt in intentionally

Many developer tools also make this step explicit and user-driven, rather than automatic on first launch.

Suggested improvement
A simple pre-permission dialog on first launch would solve this cleanly.

Proposed dialog:
• Short explanation in plain, developer-friendly terms:
• That Ollama wants to create a symlink
• The source and destination paths
• Why this enables using ollama from Terminal
• Why admin permission is required (writing to /usr/local/bin)

Actions:
• Create Symlink (default)
• Not Now

Example dialog text and layout:

  Title:
  Install Command Line Tool
  
  Body:
  Ollama can install a command line tool so you can run `ollama` from Terminal.
  
  This will create a symlink:
    /usr/local/bin/ollama → /Applications/Ollama.app/Contents/Resources/ollama
  
  Administrator permission is required to write to /usr/local/bin.
  
  Buttons:
   [Not Now] [Create Symlink]

This preserves the current behavior while making it explicit and intentional.

Settings fallback
Additionally, it would be useful to expose this in a Settings pane:
• Show whether the CLI symlink is currently installed
• Provide a “Create CLI Symlink” button if it is missing

This helps in cases where:
• The user initially chose “Not Now”
• The symlink was manually removed later
• The user simply wants a clear, discoverable way to enable it

Originally created by @jaywardell on GitHub (Apr 15, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15604 The issue On first launch, the macOS app immediately triggers a system authentication prompt to install the ollama CLI. This happens without any prior explanation from the app itself. From a user perspective (even a technical one), this feels abrupt: • The system dialog appears with no context • It’s not clear what is being installed • It’s not clear where it’s being installed • It’s not obvious that this is just creating a symlink While this is explained in the documentation, not everyone reads the documentation. Even though the behavior is safe and minimal, the lack of disclosure creates unnecessary friction and distrust. Expected behavior (macOS conventions) Apps that require elevated permissions—especially for system-level locations like /usr/local/bin—typically: • Explain the action before triggering the system auth dialog • Clearly state what will be installed and why • Give the user a chance to opt in intentionally Many developer tools also make this step explicit and user-driven, rather than automatic on first launch. Suggested improvement A simple pre-permission dialog on first launch would solve this cleanly. Proposed dialog: • Short explanation in plain, developer-friendly terms: • That Ollama wants to create a symlink • The source and destination paths • Why this enables using ollama from Terminal • Why admin permission is required (writing to /usr/local/bin) Actions: • Create Symlink (default) • Not Now Example dialog text and layout: ``` Title: Install Command Line Tool Body: Ollama can install a command line tool so you can run `ollama` from Terminal. This will create a symlink: /usr/local/bin/ollama → /Applications/Ollama.app/Contents/Resources/ollama Administrator permission is required to write to /usr/local/bin. Buttons: [Not Now] [Create Symlink] ``` This preserves the current behavior while making it explicit and intentional. Settings fallback Additionally, it would be useful to expose this in a Settings pane: • Show whether the CLI symlink is currently installed • Provide a “Create CLI Symlink” button if it is missing This helps in cases where: • The user initially chose “Not Now” • The symlink was manually removed later • The user simply wants a clear, discoverable way to enable it
GiteaMirror added the feature request label 2026-05-05 03:20:56 -05:00
GiteaMirror commented 2026-05-05 03:21:03 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

🤖 Automated Triage & Analysis Report

Issue: #15604
Analyzed: 2026-04-18T18:19:46.680771

Analysis

  • Type: unknown
  • Severity: medium
  • Components: unknown

Implementation Plan

  • Effort: medium
  • Steps:

This issue has been triaged and marked for implementation.

<!-- gh-comment-id:4274305432 --> @PureBlissAK commented on GitHub (Apr 18, 2026): <!-- ollama-issue-orchestrator:v1 issue:15604 --> ## 🤖 Automated Triage & Analysis Report **Issue**: #15604 **Analyzed**: 2026-04-18T18:19:46.680771 ### Analysis - **Type**: unknown - **Severity**: medium - **Components**: unknown ### Implementation Plan - **Effort**: medium - **Steps**: *This issue has been triaged and marked for implementation.*
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#72020
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?