Add Tahoe "Allow in Menu Bar" detection + user guidance dialog#945
Merged
steipete merged 2 commits intoMay 14, 2026
Merged
Conversation
4c3cfad to
3b1cd70
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #890.
Summary
NSStatusItembuttons actually materialize in a menu bar window/screen.x-apple.systempreferences:com.apple.MenuBarSettingsbutton.hasShownTahoeAllowListGuidance, while allowing it to reappear after 24h if the condition persists.Dialog copy
Title:
CodexBar can't show its menu bar iconBody:
macOS Tahoe can block menu bar apps in System Settings → Menu Bar → Allow in the Menu Bar. CodexBar is running, but macOS may be hiding its icon. Open Menu Bar settings and turn CodexBar on.Buttons:
Open Menu Bar Settings/DismissNotes
Apple does not expose a public API for the Tahoe allow-list state, so this is intentionally a best-effort heuristic. It only runs immediately after startup to avoid confusing later manual hiding tools such as Bartender with the system-level block.
Root-cause context came from the community diagnosis in #890: #890 (comment)
Testing
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift test --filter MenuBarVisibilityWatcherTestsDEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift buildDEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer make checkgit diff --checkOne local note: the default Command Line Tools developer dir failed on
KeyboardShortcuts#Previewmacros, so the successful build/test/lint runs above use the full Xcode developer dir.