Two ways to install
Both routes deliver the same artifact. The Homebrew cask installs the very same published DMG as the GitHub release, so pick whichever fits your setup.
Homebrew
brew install --cask Johannes-Berggren/tap/limit-lifeboat
The cask is published from a personal tap and is marked auto_updates true,
because the app manages its own updates through a signed feed.
Signed DMG
Download Limit-Lifeboat-1.1.10-arm64.dmg from the
latest GitHub release, open it, and drag
Limit Lifeboat to Applications. GitHub Releases is the only direct-download
source for release artifacts; there are no mirrors.
Requirements
- An Apple Silicon Mac running macOS 14 Sonoma or newer. Intel Macs are not supported.
- Claude Code, the Codex CLI, or both — whichever providers you want to monitor and switch.
- Nothing else. There are no API keys to paste and no new account system to create.
The app is signed with a Developer ID certificate, notarized by Apple, stapled, and built with the hardened runtime. It deliberately does not use the App Sandbox, because switching has to read and update provider-owned CLI files; the release entitlement is limited to optional Terminal automation.
First run: register the accounts you already have
Limit Lifeboat does not create accounts and cannot log in on your behalf. Each account is authenticated once through the provider’s own flow, and then registers itself.
- Sign in with
/logininside Claude Code, orcodex loginin Terminal. - Open Limit Lifeboat from the menu bar and refresh.
- The active account is detected, linked to a local profile, and an encrypted credential snapshot is saved to the macOS Keychain.
- Repeat for each account you want to be able to return to.
After that, switching restores a saved snapshot and verifies the resulting identity. The first switch may ask for macOS Terminal Automation permission. Full walkthroughs live in the Claude Code guide and the Codex CLI guide.
Verify the download
Every release publishes a .sha256 file next to the DMG. Compare it against
the file you downloaded:
shasum -a 256 ~/Downloads/Limit-Lifeboat-1.1.10-arm64.dmgPublished tags, versions, DMGs, checksums, and appcasts are immutable. A fix always ships as a new patch release rather than a replaced artifact, so a checksum that once matched will always match.
How updates work
The app checks a signed GitHub release feed once a day by default. You can disable automatic checks in Settings. Nothing installs silently: every update waits for you to choose Install and Relaunch. Overwriting the app in Applications keeps its Application Support data and Keychain entries.
The changelog lists what changed in each version.
Questions
Is Limit Lifeboat free?
Yes. It is free and open source under the MIT License. There is no paid tier, no account to create, and no telemetry.
Does it work on an Intel Mac?
No. Limit Lifeboat 1.1.10 is built for Apple Silicon only and requires macOS 14 Sonoma or newer. Intel Macs are not supported.
How do I verify the download?
Each GitHub release publishes the DMG alongside a .sha256 checksum file. Run shasum -a 256 on the downloaded DMG and compare the result with the published checksum. The app is also signed with a Developer ID certificate and notarized by Apple, so macOS verifies it on first launch.
How does the app update itself?
It checks a signed release feed once a day by default, and automatic checks can be turned off in Settings. Updates are never installed silently: every one waits for you to choose Install and Relaunch. Replacing the app in Applications preserves its Application Support and Keychain data.
What permissions does it ask for?
None on install. Notifications are optional. Launch at login is off until you enable it. macOS Terminal Automation is requested the first time you switch an account, and Keychain access is requested only for explicit actions that need it.