macOS 27 beta: status item never appears in the menu bar
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
Research direction
The report needs a macOS 27 beta machine to reproduce, and the payload names no source file. Start by finding where the app creates its menu-bar status item, then read the linked issues #2306 and #3377 for earlier menu-bar failures. Done means the status item appears on macOS 27 beta, or the app logs a clear hosting failure distinct from provider errors.
Written by the indexing model from the issue text.
Description
Summary
On macOS 27 beta, CodexBar launches and the CLI usage path works, but the status item never appears in the menu bar. This looks like a macOS MenuBarAgent/Control Center compatibility issue rather than a provider-authentication problem.
Environment
- macOS 27 beta
- CodexBar 0.74.1 installed via Homebrew
- “Allow in the Menu Bar” enabled for CodexBar
Reproduction
- Install CodexBar.
- Enable it under System Settings → Menu Bar → Allow in the Menu Bar.
- Launch CodexBar.
- The application runs, but no CodexBar icon appears in the menu bar.
The same result occurred after toggling the permission, restarting the menu-bar system components, rebooting, and performing a clean uninstall/reinstall.
The independent CLI path succeeds:
codexbar usage --status --provider codex
Request
Please investigate and update CodexBar for macOS 27 beta compatibility, especially the status-item hosting/Control Center registration path. A clearer diagnostic or fallback would also help users distinguish a menu-bar hosting failure from a provider/authentication failure.
Related reports: #2306 and #3377.
- Dominant language
- Swift
- Stars
- 23.3k
- Forks
- 2.2k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 231
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from steipete/CodexBar
-
clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:other issue-rating: 🦪 silver shellfish P2
Difficulty 1/5 Under an hour Newbie friendliness 72/100
steipete/CodexBar#5147 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
googledeveloper: unclaimed Ultra credit (null remaining amount) fails with "unrecognized response" instead of "Not applied"Possibly taken @djbclark claimed this today. Openclawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 28/100
steipete/CodexBar#5145 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:other issue-rating: 🦪 silver shellfish P2
Difficulty 3/5 1-2 days Newbie friendliness 50/100
steipete/CodexBar#5144 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Claude CLI source drops "Current week (all models)" when /usage redraws over earlier screen contentOpenclawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 4/5 3-5 days Newbie friendliness 30/100
steipete/CodexBar#5143 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-info clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🦐 gold shrimp P2
Difficulty 4/5 3-5 days Newbie friendliness 42/100
steipete/CodexBar#5132 · 5 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in steipete/CodexBar
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nwverse/persona#12800 · 1 comment ·
Maintainers usually reply within 1 day
-
bug documentation
Difficulty 1/5 Under an hour Newbie friendliness 86/100
ajithrnayak/xpunge#7 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DuarteSantos8/openGym#1469 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day