ollama - 💡(How to fix) Fix More transparent permission flow for CLI installation on macOS using desktop app [1 participants]

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