Thaw: A GPL-3.0 Menu Bar Manager for macOS 26 and 27

What Thaw Solves and Who It's For

The README lists a core set of features: hiding menu bar items, an 'always-hidden' section, revealing hidden items via hover, click, scroll, or hotkey, and a search function to jump to any item. It also includes profiles for different contexts (work, focus, presenting) and extensive appearance customization: tint, gradient, shadow, border, and custom shapes, with separate settings for light and dark mode. The feature list expands to over 20 items, including drag-and-drop arrangement, item spacing, and hotkeys for toggling sections and the Thaw Bar. This is not just a simple icon hider; it is a full menu bar management suite. The design philosophy is clear from the README: no tracking, no account, no telemetry, and everything stays on your Mac. That is a strong stance for privacy-focused users.

How Thaw Works Under the Hood

The README does not provide detailed architecture diagrams, but the feature set implies the mechanism. Thaw uses the macOS accessibility APIs to enumerate and control menu bar items. The key design choice is that Screen Recording permission is optional. The README states: 'Hiding, revealing, and rearranging items all work without it. Grant it only if you want menu bar item previews and appearance tinting.' This is a significant trade-off. Without Screen Recording, Thaw cannot see the actual pixel content of menu bar items, so it cannot render previews or apply visual effects like tinting. It relies on the accessibility API to identify items and their positions. When you grant Screen Recording, Thaw gains the ability to capture the screen region for previews and to apply its custom styling, which likely involves overlaying a transparent window or using Core Graphics to redraw the bar. The 'Thaw Bar' feature, which shows hidden items in a separate bar below the menu bar, suggests a separate window or view that replicates the menu bar's contents. The project's use of Swift and the macOS SDK is standard for such tools. The fact that it can hide application menus when they overlap with shown items indicates a deep integration with the menu bar's layout system, likely using private or undocumented APIs, which is common for this type of utility but carries risk with OS updates.

Getting Started: Installation and Configuration

The README provides a 'Download' link to the GitHub releases page and an 'Install' section, but the cleaned README does not include explicit commands. However, the repository is a Swift project, so building from source is possible. You would clone the repository, open the Xcode project, and build it. The README mentions 'verifiable releases' with a link to docs/VERIFYING_RELEASES.md, indicating that releases are signed and notarized by Apple, and you can verify their integrity. The project uses GitHub Actions for CI, as shown by the CI badge, so the build process is automated. For configuration, the README describes features but not specific config keys. The app likely has a preferences window where you can set hotkeys, profiles, and appearance options. The README mentions hotkeys for toggling sections, showing the search panel, and enabling the Thaw Bar. You would assign these in the app's settings. The absence of a command-line interface or config file suggests that all configuration is done through the GUI. For a technical user, the main task is to download the latest release, verify its checksum, and grant the necessary permissions when prompted.

The GPL-3.0 License and Its Implications

Thaw is licensed under GPL-3.0, which is a strong copyleft license. The README emphasizes this: 'Open source, GPL-3.0. Read the code, build it yourself, fork it.' For end users, this means you can use it freely, modify it, and redistribute it, but if you distribute a modified version, you must make your source code available under the same license. For a typical user who just wants to hide menu bar icons, this has no practical impact. For developers who want to integrate Thaw into a commercial product, the GPL-3.0 license is a barrier. You cannot link to Thaw's code in a proprietary application without open-sourcing your entire product. This is a deliberate choice by the project, aligning with its privacy and open-source ethos. The README also mentions that the project is 'signed and notarized by Apple,' which is a separate issue from licensing. The license implications are clear: if you fork Thaw, your fork must also be GPL-3.0. This is a key consideration for any organization evaluating it.

Limitations and Potential Failure Modes

The most obvious limitation is that Thaw is still in release candidate stage. The latest release is 2.0.0-rc.5, not a stable 1.0. This means you may encounter bugs. The README includes a link to a 'macOS 27 status' issue, indicating that there are known compatibility concerns with the newest macOS version. The project's reliance on accessibility and screen recording APIs means that any change in macOS's security model could break functionality. For example, if Apple changes how menu bar items are exposed to accessibility APIs, Thaw would need to be updated. The README states that 'Screen Recording is optional,' but without it, you lose previews and tinting, which are major selling points. Another limitation is that Thaw only supports macOS 26 and 27. If you are on an older version, you cannot use it. The tool also has a feature to 'hide application menus when they overlap with shown menu bar items,' which could be disruptive if you rely on those menus. There is no mention of a trial or evaluation period, so you must commit to the release candidate or build from source. The project's focus on privacy means it does not collect usage data, which is good for privacy but means the developers may not know about bugs unless users report them manually.

Alternatives: How Thaw Compares to Other Menu Bar Managers

The most well-known commercial alternative is Bartender, a paid menu bar manager that has been around for years. Bartender offers similar features: hiding items, revealing them, and arranging them. The key difference is that Bartender is closed-source and requires a paid license, often with an upgrade fee for new macOS versions. Thaw's README explicitly contrasts with this: 'No purchase, no subscription, and no upgrade fee when macOS ships a new version.' Another alternative is Hidden Bar, a free and open-source menu bar hider that is simpler and less feature-rich. Hidden Bar focuses on a single always-hidden section and does not offer search, profiles, or appearance customization. Thaw's advantage is its comprehensive feature set and modern macOS support. However, Hidden Bar is stable and has been around longer, so it may be more reliable. There is also the option of using macOS's built-in ability to hide menu bar items by Command-dragging them off the bar, but that is limited and does not provide a search or profiles. For users who want a free, open-source solution with advanced features, Thaw is a strong candidate, but for those who need a battle-tested tool, a commercial option might be safer.

Maintenance and Upgrade Cost

The project is actively maintained, with the latest push on 2026-08-25, and releases are frequent: rc.3, rc.4, and rc.5 within ten days. This indicates a fast development cycle, which is good for bug fixes but also means you may need to update often. The README mentions that the project is tracked against OpenSSF Best Practices and has an OpenSSF Scorecard, which suggests a commitment to supply-chain security. Upgrades are free, as stated in the README, but you will need to download and install new releases manually. The project uses Crowdin for translations, with 20 languages, which adds to the maintenance burden but also makes it accessible to a wider audience. For a user, the upgrade cost is low: you download the latest release, verify it, and replace the app. For a developer who forks the project, the maintenance cost is higher because you must keep up with upstream changes and adapt to macOS updates. The README's note about 'verifiable releases' means you should check the verification document each time you update. Overall, the project appears well-maintained, but the rapid release cadence could be a sign of instability as they approach a stable release.

Editorial conclusion

Adopt Thaw if you need a free, open-source menu bar manager that respects your privacy and works on macOS 26 and 27. Avoid it if you require a stable 1.0 release or cannot accept the GPL-3.0 license for your use case. Before adopting, verify the latest release's checksums via docs/VERIFYING_RELEASES.md and check the project's issue tracker for macOS 27-specific bugs, as the README explicitly links to a macOS 27 status issue. If you need a menu bar manager today and cannot wait for a stable release, consider a commercial alternative or a simpler tool with a smaller feature set.

Official sources

1. Official README
2. Project repository
3. Release notes