BrewUI is Homebrew's official native macOS app for finding, installing, updating and managing Homebrew packages through a graphical interface rather than the Terminal. It is written in SwiftUI and published by the Homebrew project itself, and it is aimed at Mac users who want what Homebrew offers but do not want to memorize command-line syntax to get it. People who already live in a shell are not the target audience, although the app is deliberately transparent enough that they can watch exactly which commands it issues on their behalf.
What it does
The app puts the everyday Homebrew workflow behind a window. You search for packages, install them, update what you already have, and manage the result, all with clicks instead of typed commands. The project describes its goal as enabling users who avoid the CLI to safely discover, install, update and manage Homebrew packages.
The part that separates it from a generic front end is its stance on transparency. BrewUI does not hide what Homebrew is doing: a console surfaces the actual brew commands as they run, so a click is never a black box. Every action in the interface corresponds to a real Homebrew operation you can read, learn from, and reproduce in a Terminal later if you want to.
Information in the app comes from two places: the brew command-line tool itself, and the public Homebrew JSON API that also powers the formulae website. There is no separate package index to trust and no parallel implementation of Homebrew's logic to drift out of sync.
How it works
BrewUI is a Swift 6.0 codebase with strict concurrency enabled, built with SwiftUI and Swift Package Manager, and it targets macOS Tahoe 26 and newer. It is a native app rather than a web view in a window.
The interesting engineering decision is how it invokes Homebrew. BrewUI always launches brew through /bin/zsh, including when it upgrades itself, and it does so with --no-rcs --no-global-rcs so that optional user and system shell startup files are skipped. It then supplies a clean environment in which PATH contains only the directory of the located brew executable followed by /usr/bin:/bin.
The practical consequence is worth understanding before you install it: your login shell, your aliases, your exported variables and your custom PATH do not configure Homebrew when it runs under BrewUI. That is a feature — it makes runs reproducible and independent of whatever accumulated in a dotfile over the years — but it will surprise anyone who has tuned Homebrew through .zshrc.
Configuration instead goes in brew.env files, which Homebrew reads on its own. There are three scopes: a user file at ~/.homebrew/brew.env, an installation file at <Homebrew prefix>/etc/homebrew/brew.env, and a system file at /etc/homebrew/brew.env. Lines are literal NAME=value pairs with no export, no shell expansion and no command substitution. User settings normally override installation settings, which override system settings; setting HOMEBREW_SYSTEM_ENV_TAKES_PRIORITY=1 in the system file flips that so the system file wins.
Getting started
Installation is a single cask:
brew install --cask homebrew-app
After that, the migration step for existing Homebrew users is moving environment variables out of shell startup files. If you relied on something like HOMEBREW_NO_ENV_HINTS=1 being exported from your shell profile, put that same line in ~/.homebrew/brew.env instead and it will apply both in the app and on the command line. Homebrew's own environment documentation lists the variables available.
When to use it / when not
Use BrewUI if you are on a recent Mac, you want Homebrew's catalog and update handling, and a graphical window is simply a more comfortable place to browse and click than a prompt. It is also a reasonable teaching tool: the live command console means a newcomer can see the CLI equivalent of every action, which is a gentler path into brew than a blank terminal.
It is the wrong tool if you need automation — scripts, CI jobs, provisioning and remote machines all still want the CLI. It also will not help you on a Mac older than macOS Tahoe 26, and there is nothing here for Linux users of Homebrew. And if your Homebrew setup depends on shell-side configuration you would rather not restructure, expect to do that cleanup first.
Anyone who maintains Macs for other people should look at this closely: it is a first-party app, so it will track Homebrew's behavior rather than guess at it, and it lets a non-technical colleague keep their own tools current without you writing out commands for them to paste. The project has drawn more than a thousand stars since it appeared, which says something about demand for a supported graphical option. Note the AGPL-3.0 license if you were thinking of building on the code rather than just running the app.