Fix macOS 26 menu bar ownership and recovery - #9
bifrost-proxy wants to merge 2 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee9dd3ce3f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [[ "${LAUNCH_MODE}" == "auto" && "${macos_major}" -ge 26 ]]; then | ||
| launch_app=0 |
There was a problem hiding this comment.
Keep the macOS 26 release checklist runnable
On macOS 26, the default installer command in docs/RELEASING.md:79-83 now takes this branch after the script has quit the existing app at line 125, leaving no BLEUnlock process. The same release checklist later runs the performance gate using pgrep (docs/RELEASING.md:95-100), which consequently exits with “A running BLEUnlock process is required” unless the verifier independently knows to relaunch the app from Finder. Update the release guide to include that required Finder launch before the runtime checks. agents.mdL168-L176
Useful? React with 👍 / 👎.
Background
On macOS 26.5, BLEUnlock could keep running while its status item disappeared and the app was absent from System Settings > Menu Bar > Allow in the Menu Bar.
A read-only decode of Control Center's
trackedApplicationsreproduced the root cause:com.bifrost-proxy.BLEUnlockwas recorded in themenuItemLocationsowned by the disabledcom.openai.codexentry. Control Center therefore blocked BLEUnlock as if it belonged to its launcher.Changes
NSStatusItem;--launchopt-in while preserving--no-launch;Verification
bash -n install.shbash install.sh --helpscripts/build-local.sh --verifyin a non-FileProvider temporary checkout: compile, 5-second smoke test, ad-hoc signature verification, DMG, SHA-256, read-only mount, and nested executable verification all passed.bash install.sh --version v1.15.1 --install-dir <temporary-dir>on macOS 26.5: download, checksum, signature verification, copy, and post-install verification passed; the app did not auto-launch and the Finder instruction was printed.com.openai.codex.Manual recovery still requiring user approval
The affected Mac still needs System Settings > Menu Bar > Reset Control Center followed by a first launch from Finder. That reset changes the user's current menu bar arrangement, so it was not executed automatically. MB-01 and MB-02 remain explicitly pending for that reason.
Environment limits
Full
xcodebuildwas not run because this Mac has Command Line Tools only (/Library/Developer/CommandLineTools) and no full Xcode installation. The repository's CLT verification gate passed.