CCMenu is a free, open-source Mac menu-bar app that shows the live build status of your continuous integration pipelines at a glance, placing colour-coded pass/fail indicators a single click away from whatever you're working on.
What is CCMenu?
CCMenu is a lightweight macOS utility that sits in your menu bar and polls CI servers — Jenkins, GitHub Actions, CircleCI, Travis CI, Buildkite, and any server that speaks the CCtray XML feed format — then surfaces the current build health of every monitored pipeline without you ever switching to a browser tab. Think of it as a silent sentry: green means ship it, red means someone's commit just broke the build.
I've had it running in the menu bar since long before I could remember to keep a browser tab open to Jenkins. The value is zero-friction awareness — I don't have to think about CI; CCMenu thinks about it for me and taps me on the shoulder when something needs attention.
What does CCMenu do best?
CCMenu excels at keeping CI signal in your peripheral vision without the overhead of a full dashboard app or a noisy notification flood. Its core loop is beautifully simple: you paste in a CCtray feed URL, give the project a name, and a coloured status icon appears in your menu bar within seconds.
- Menu-bar icon changes colour — grey (unknown), green (passed), yellow (building), red (failed) — no need to open anything.
- Drop-down per-project list shows every monitored pipeline's last build label, who triggered it, and how long ago it ran.
- macOS notifications fire on state changes only, so you aren't drowning in alerts when builds are consistently passing.
- Multiple servers, one app — mix GitHub Actions feeds alongside a self-hosted Jenkins instance without spinning up a second tool.
Where it does not shine is in deep analytics or build log access. CCMenu is a status indicator, not a build debugger. For that you still open the CI web UI — but CCMenu tells you when to bother.
Is CCMenu free?
Yes — CCMenu is completely free and open source under a BSD-style licence. You can install it via Homebrew Cask (brew install --cask ccmenu) or grab the universal binary directly from ccmenu.org. There is no paid tier, no subscription, and no telemetry that requires your acceptance of a privacy policy.
Who should use CCMenu?
Any developer or DevOps engineer who works with CI pipelines daily and wants a native, always-visible build-health signal belongs in CCMenu's target audience. It is especially valuable on teams that share a multi-project monorepo: you can monitor the builds for every sub-project and catch a broken dependency pipeline before it blocks your own PR.
If you rely entirely on email or Slack notifications for CI failures, you've probably experienced the lag where a colleague merges a red commit and you don't find out until your own build is blocked fifteen minutes later. CCMenu shrinks that gap to the next polling interval.
Less useful if you work on a solo project with a single pipeline that rarely breaks, or if your CI vendor's own Mac app (e.g. Buildkite's native notifications) already covers your needs — though CCMenu's multi-server coverage is hard to beat.
How does CCMenu compare to alternatives?
The closest competitor in the menu-bar space is BuildWatch, which offers a similar concept but with a narrower list of supported CI services and less active maintenance. Navi for GitHub Actions is polished if you're GitHub-only, but the moment you add a Jenkins server to the mix, you're reaching for CCMenu. Browser extensions like Octocat Helper or the GitHub Actions dashboard handle GitHub well but live in the browser context, not the system menu bar.
For full-blown build monitoring at team scale you'd look at something like Meercode or a hosted CI dashboard — but those require browser tabs, logins, and often a paid plan. CCMenu's niche is the solo developer or small team that wants a zero-cost, always-there status light with no account required.
What are the best CCMenu alternatives?
If CCMenu doesn't fit, your best options are Navi (GitHub Actions-only, slicker UI), BuildWatch (menu-bar, fewer integrations), or simply pinning your CI provider's status page to a browser tab and relying on Slack webhooks. For teams with dedicated DevOps screens, a self-hosted Grafana dashboard fed by your CI API is more powerful — but vastly more work to set up for the benefit CCMenu gives you in two minutes.
