A lightweight, native macOS menu bar application for managing your local Ollama server.
  • Swift 87.7%
  • Shell 12.3%
Find a file
2026-11-21 22:14:09 +01:00
Resources Initial commit 2026-11-21 22:14:09 +01:00
Sources Initial commit 2026-11-21 22:14:09 +01:00
.gitignore Initial commit 2026-11-21 22:14:09 +01:00
build.sh Initial commit 2026-11-21 22:14:09 +01:00
ICON_CREDITS.md Initial commit 2026-11-21 22:14:09 +01:00
LICENSE Initial commit 2026-11-21 22:14:09 +01:00
README.md Initial commit 2026-11-21 22:14:09 +01:00
RELEASE_NOTES.md Initial commit 2026-11-21 22:14:09 +01:00

Ollama Control

A native macOS menu bar app built with SwiftUI. It uses a purple, Liquid Glass-inspired app icon.

Requirements

  • macOS 14 or later
  • Xcode Command Line Tools (xcode-select --install)
  • Local Ollama installation; supported executable paths include /opt/homebrew/bin/ollama, /usr/local/bin/ollama, /usr/bin/ollama, and ~/.local/bin/ollama

Build and launch

chmod +x build.sh
./build.sh
open "dist/Ollama Control.app"

No external Swift packages are required. build.sh must be run on macOS because it uses SwiftUI, AppKit, sips, and iconutil. The local build is ad-hoc signed. The free release build is also ad-hoc signed and is not notarized; macOS Gatekeeper may block it on other Macs.

For reliable Launch at login behavior, move the built app to /Applications/Ollama Control.app before enabling the checkbox. Rebuilding or moving a registered app may require toggling the setting off and on again. macOS may also request approval in System Settings → General → Login Items & Extensions. Login item registration may not work reliably for ad-hoc signed apps on all macOS versions; Developer ID signing is recommended for distribution.

Features

  • Start Ollama using the local ollama serve CLI command.
  • Stop a server launched by this app. For externally launched servers, only terminate a process when an ollama serve listener on port 11434 can be unambiguously identified.
  • Display server availability and Ollama version via GET /api/version.
  • List currently loaded models via GET /api/ps (not all installed models).
  • Unload individual models via POST /api/generate with keep_alive: 0.
  • Automatically poll status every 30 seconds. There is no manual refresh button.
  • Show a menu bar icon and an accessible, resizable settings window (default 820 × 720 points).
  • Enable or disable Launch Ollama Control at login using macOS ServiceManagement (SMAppService).

Network Access & Privacy

Ollama Control itself communicates only with the local Ollama API at http://127.0.0.1:11434. It uses this connection to check server availability and version, list currently loaded models, and request that a model be unloaded. Status checks run automatically every 30 seconds.

Ollama Control does not include telemetry, analytics, or external reporting. Monitoring and managing an already-running local Ollama server does not require an internet connection.

Firewall applications (Little Snitch / LuLu)

When Ollama Control starts ollama serve, Ollama runs as a child process of the app. Firewalls such as Little Snitch or LuLu may therefore attribute network connections made by Ollama to Ollama Control.

Depending on how Ollama is used, these may include:

  • ollama.com and Ollama registry endpoints — for downloading or pulling models and related registry requests.
  • Other network endpoints — if explicitly configured or contacted by Ollama or its integrations.

These connections are not part of Ollama Control's status monitoring. Blocking external access generally does not prevent inference with models already available locally, but downloads and other network-dependent Ollama operations may fail.

If Ollama is started independently (for example, by Ollama Desktop or a service manager), firewall applications may instead show its connections under the separate Ollama process.

Local API security

By default, Ollama Control targets the loopback address 127.0.0.1:11434; it does not expose an additional network service. If you separately configure Ollama to listen on a network-accessible interface, protect that API with appropriate network and firewall restrictions.

Notes

The app connects only to http://127.0.0.1:11434. Servers managed by Ollama Desktop, launchd, or another service manager may restart automatically or may not be safely stoppable from this app. A failed HTTP request indicates that the local API is unreachable, not necessarily that no Ollama process exists.

The settings window opens on first launch and can be reopened from the menu bar. The project is built directly using swiftc and does not require an Xcode project file.

License and credits

Copyright (c) 2026 Ulrich Habel rhaen@pkgbox.de.

This project, including the supplied icon assets, is distributed under the MIT License. See LICENSE.

AI disclosure: The purple Ollama Control app icon was created with AI assistance. The included artwork is distributed under the project's MIT License to the extent that the author can grant rights to it. AI-generated artwork may not qualify for copyright protection in every jurisdiction, and this notice does not grant rights to third-party trademarks or other protected material.

Free GitHub release (without Apple Developer ID)

Run on a Mac with Xcode Command Line Tools and a macOS SDK that supports both Apple Silicon and Intel:

./build.sh --release

This builds an optimized universal arm64 + x86_64 app (minimum macOS 14), applies ad-hoc code signing, verifies the signature, and creates:

  • dist/OllamaControl-v1.2.0-macOS-universal.zip — upload to GitHub Releases
  • dist/OllamaControl-v1.2.0-macOS-universal.zip.sha256 — checksum

The script does not publish anything to GitHub and does not notarize the app. No Apple Developer Program membership is needed for this build. The compiled application must be built on macOS; the source ZIP is not a compiled binary.

Installing an unnotarized release

  1. Download the release ZIP from the project's GitHub Releases page and extract it.
  2. Move Ollama Control.app to /Applications.
  3. Try opening the app normally. If macOS blocks it, go to System Settings → Privacy & Security, locate the blocked-app notice, and choose Open Anyway after verifying that the download came from the expected project. Follow macOS confirmation prompts. The option may only appear after a blocked launch attempt.

Security notice: The app is not Developer ID signed or notarized. Ad-hoc signing does not authenticate the publisher. Do not disable Gatekeeper globally, and do not blindly remove quarantine attributes. Review the source and checksum before trusting a release. Login-item registration through SMAppService may behave differently across macOS versions for ad-hoc signed apps.