Who BrewUI is for#
Mac users managing Homebrew without Terminal
BrewUI presents a searchable view of installed formulae and casks, upgrade status, and package details in a point-and-click interface. Install, remove, or update any package by clicking buttons that show the underlying `brew` command as it runs. No shell knowledge required for routine package management.
Skip if:
You already use the `brew` CLI daily and know what you want to install. The GUI adds navigational overhead for experienced terminal users who can type commands faster than clicking through a UI.
Developers onboarding teammates to a new Mac
Sharing `brew install --cask homebrew-app` gives a new team member a visual way to find and install development dependencies. They can browse what is available, read formula descriptions, and monitor update status across their tools without learning `brew` syntax first.
Skip if:
Your team uses a centralized MDM tool (Jamf, Mosyle) to push packages to managed Macs. BrewUI is designed for individual users managing their own Homebrew, not fleet-wide package deployment.
macOS users exploring the Homebrew catalog
Homebrew indexes thousands of formulae and casks not available on the Mac App Store. BrewUI lets users browse that catalog, read package descriptions, and install tools visually. The Homebrew JSON API integration keeps the formula list current with upstream without requiring app updates.
Skip if:
You are looking for Mac App Store apps or commercial software. BrewUI only surfaces packages distributed through Homebrew and has no visibility into App Store or direct-download software.
The problem it solves#
Package management on macOS has always been a Terminal-first discipline. Homebrew is the standard package manager for the Mac ecosystem, but it has no official graphical interface, which means every install, update, and removal requires typing shell commands. For developers who live in the terminal this is no obstacle, but for designers, students, and non-engineering teammates who need Homebrew packages, the barrier is real: learning enough shell to manage a package manager safely is overhead that has nothing to do with their actual work.
The workarounds have always been imperfect. Third-party GUI wrappers emerged to fill the gap, but they are maintained outside the Homebrew project and can lag behind Homebrew's own API and behavior changes. Users relying on these unofficial interfaces sometimes find they do not surface the latest formulae or reflect what Homebrew is actually doing under the hood.
How it solves it#
Native SwiftUI interface on macOS
Built in Swift 6.0 with SwiftUI and targeting macOS Tahoe 26 or later, BrewUI renders as a first-class macOS app rather than an Electron wrapper or web view. Every UI element follows macOS conventions, and strict Swift 6.0 concurrency governs all async operations.
Full Homebrew CLI transparency
Every action BrewUI takes calls the `brew` CLI directly and streams its output to an in-app console. When you install, remove, or upgrade a package, the exact Homebrew command and its full output are visible. Nothing is hidden or abstracted away from the underlying package manager.
Homebrew JSON API integration
BrewUI pulls package metadata from the official Homebrew JSON API at formulae.brew.sh for browsing and search. This covers formulae and casks, giving you current descriptions and availability without bundling a local database that could go stale between app updates.
Isolated environment for Homebrew operations
BrewUI launches Homebrew through `/bin/zsh` with shell startup files disabled (`--no-rcs --no-global-rcs`) and a PATH containing only the `brew` executable directory and `/usr/bin:/bin`. Your shell aliases, exported variables, and custom PATH do not affect how Homebrew runs inside the app.
brew.env configuration file support
Custom Homebrew settings go in `~/.homebrew/brew.env` (user scope), `<Homebrew prefix>/etc/homebrew/brew.env` (installation scope), or `/etc/homebrew/brew.env` (system scope) using plain `NAME=value` lines. BrewUI's Configuration tab reports the active environment and surfaces any issues found by `brew doctor`.
Strengths and trade-offs#
Strengths
- Official Homebrew organization backingBrewUI is maintained under the Homebrew GitHub organization, not by an independent developer. API changes, new formula categories, and Homebrew behavior changes reach BrewUI without waiting for a third party to notice and release an update. The repo description calls it Homebrew's official macOS GUI.
- Free installation via brew caskInstalling BrewUI requires no App Store account and no purchase. `brew install --cask homebrew-app` is the entire install path. Paid third-party Homebrew GUI apps on the Mac App Store charge for the same core functionality; BrewUI provides official, maintained capability at zero cost.
- Active development with a low issue backlogThe repository was created in March 2026 and last pushed September 15, 2026, with only 8 open issues against 1,367 stars. The README describes the project as stable and under active development. A low open-issue count relative to stars indicates responsive maintenance.
Trade-offs
- -macOS Tahoe 26 or later requiredBrewUI targets macOS Tahoe 26 and above exclusively. Users on Ventura, Sonoma, or Sequoia cannot run it; an OS upgrade is a prerequisite. For managed Mac fleets where an OS upgrade requires IT approval or testing cycles, this is a real deployment blocker.
- -macOS only, no cross-platform supportBrewUI is a native SwiftUI app built for Apple's platform. It has no Linux or Windows equivalent and no web interface. If you manage packages on non-macOS machines, BrewUI is not relevant to that workflow.
- -AGPL-3.0 applies to forks distributed as servicesFor ordinary use (installing and managing packages), AGPL-3.0 has no effect on end users. If you fork BrewUI's source and run a modified version as a networked service, the license requires making your modified source publicly available. This constraint only matters to developers building on top of the codebase.
BrewUI vs alternatives#
BrewUI vs Cork
Both BrewUI and Cork provide graphical interfaces for Homebrew on macOS, letting users browse formulae, install and remove packages, and track updates without the Terminal. BrewUI comes from the Homebrew organization itself; Cork is an independently developed third-party app sold on the Mac App Store.
| Feature | BrewUI | Cork |
|---|---|---|
| License | AGPL-3.0 | Proprietary |
| Price | Free | Paid (Mac App Store) |
| Project origin | Official Homebrew organization | Independent developer |
| macOS requirement | macOS Tahoe 26+ | Earlier macOS supported |
| Install path | brew install --cask homebrew-app | Mac App Store purchase |
BrewUI is the stronger choice for users on macOS Tahoe 26 or later who want a GUI maintained by the Homebrew project. The official origin means BrewUI tracks Homebrew's API and behavior changes directly, rather than waiting for a third-party developer to ship an update after each Homebrew release. For users not tied to the App Store, the brew cask install path keeps all package management in one tool.
Cork is worth considering if you are on an earlier macOS version that BrewUI does not support, or if you prefer the App Store purchase and update model. BrewUI's first commit was March 2026, making it newer than Cork; users who need a more battle-tested GUI with a longer track record may find Cork's maturity an advantage for edge cases BrewUI has not yet encountered.
Quick start#
Install BrewUI as a macOS cask after Homebrew is set up on your Mac.
```bash
brew install --cask homebrew-app
```What it's built on#
- Languages
- Swift
FAQ#
Does BrewUI require Homebrew to already be installed?
Yes. BrewUI is a GUI layer on top of the brew CLI; it does not bundle or replace Homebrew. Install Homebrew first via the official script at brew.sh, then add BrewUI with brew install --cask homebrew-app. BrewUI locates the brew executable automatically and uses it for all package operations.
What macOS version does BrewUI require?
BrewUI requires macOS Tahoe 26 or later. It is built with Swift 6.0 and SwiftUI and targets Apple's platform exclusively. macOS Ventura, Sonoma, and Sequoia are not supported. Users on earlier releases who want a Homebrew GUI should look at third-party options such as Cork or Cakebrew.
Why doesn't my shell configuration affect Homebrew inside BrewUI?
BrewUI intentionally isolates Homebrew from your shell. It launches Homebrew through /bin/zsh with startup scripts disabled (--no-rcs --no-global-rcs) and a stripped PATH containing only the brew directory and /usr/bin:/bin. Your .zshrc settings, shell aliases, and exported variables are not visible to Homebrew inside the app. To pass Homebrew-specific settings, use ~/.homebrew/brew.env with plain NAME=value lines.
Is BrewUI affiliated with the official Homebrew project?
Yes. BrewUI is maintained by the Homebrew organization at github.com/Homebrew. The repository describes it as Homebrew's official macOS GUI. It is not a third-party app; it lives under the same GitHub organization as Homebrew itself.
What does the AGPL-3.0 license mean for BrewUI users?
For end users installing and managing packages, AGPL-3.0 has no practical effect. You can use it freely on any Mac you own. The license becomes relevant only if you fork the source and distribute a modified version as a networked service; in that case, AGPL requires making your modified source publicly available. You cannot build a competing managed service from the source without releasing your changes.
Similar open-source tools#
iloader
Free open-source iOS sideloader for Windows, Mac, and Linux
escrcpy
Graphical Android device mirroring and control with scrcpy
vphone-cli
Virtual iPhone on Apple Silicon, self-hosted and MIT licensed
hysteria
Fast and censorship-resistant proxy solution
OpenFlux
TCP tunneling via Yandex Docs or WebRTC transports
Sonarr
Smart PVR for Usenet and BitTorrent TV fans