Introduction
Remove one or more Homebrew packages from a macOS device as part of an automation. Use this action to clean up tools that are no longer needed, enforce software policies, or pair with a Tag Removed trigger to automatically uninstall packages when a device leaves a group or loses a tag.
Uninstall Homebrew Package
From the automation pipeline in edit mode, click + Add action and select Uninstall Homebrew package from the App management category. The action panel opens with two sections: Action type (pre-set to Uninstall Homebrew package) and Step configuration.
Package(s)
Enter the Homebrew formula or cask name for each package you want to remove. Press Tab or type a comma after each name to add the next.
The field is required — you can't save the action without at least one package name.
For package name reference, visit https://formulae.brew.sh/.
💡 TIP: Pair this with the Tag Removed trigger to automatically uninstall packages when a device loses a tag. Tag a device with dev-tools, use Tag Applied to install a set of packages, and use Tag Removed to uninstall them when the tag comes off.
Conditions
The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action. Expand the section to add conditions.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for additional execution settings including action name, failure behavior, output variables, and retries.
See Actions Overview for the full reference on additional options available on every action.
FAQ
What if the package I specify isn't installed? Homebrew reports it as not found and skips the uninstall. Configure failure behavior in Additional options if you need the action to fail explicitly in this case.
Does this remove package dependencies too? No. Only the named packages are removed. Run
brew autoremovein a subsequent script action to clean up orphaned dependencies.I see a banner when running brew commands in the terminal. Is that normal? Yes. Level's wrapper script at
/usr/local/bin/brewprints an informational note confirming Homebrew is Level-managed. It's not an error. See Install Homebrew Action for more detail.Does this work on Windows or Linux? No. Homebrew is macOS only. This action is not available for Windows or Linux devices.
Who can add or modify this action in an automation? Technicians with permission to edit automations in the relevant group. See Workspace → Permissions for access control configuration.
What happens if the device is offline when this action runs? The action queues and resumes once the device comes back online.
Can I use this to uninstall Homebrew itself? No. This action removes Homebrew packages, not Homebrew itself.