AnyBar is a free, open-source Mac utility that places a small, coloured dot in your menu bar and lets any script, terminal command, or application change its colour on demand to communicate status at a glance.
What is AnyBar?
AnyBar is a programmable menu-bar dot for macOS — a tiny circle that sits in your system tray and changes colour in response to UDP messages you send it from the command line or any program. It has no built-in meaning; you assign the meaning. That radical simplicity is the whole point.
Think of it as a single pixel of awareness you can wire to anything: a long-running build, a server health check, a background sync job, a custom shell alias. When the dot is green, things are good. When it goes red, something needs your attention — without you ever switching windows or reading a log.
What does AnyBar do best?
AnyBar excels at bridging the gap between headless background processes and your human attention span. Where most monitoring tools demand you open a dashboard or parse console output, AnyBar reduces the whole status surface to one coloured dot you can register in your peripheral vision.
- Instant scriptability: a single echo -n "red" | nc -4u -w0 localhost 1738 is all it takes to flip the indicator — no SDK, no API key, no framework.
- Multiple independent instances: launch AnyBar on different UDP ports and you can track several parallel jobs simultaneously, each with its own dot.
- Custom images: drop a yourname.png into ~/.AnyBar/ and send its name over UDP to display a completely custom icon, not just the built-in colour palette.
- Zero resource footprint: the app is genuinely tiny. It sits idle, using negligible CPU and RAM, until it receives a message.
I've used it to signal when a pytest suite finishes, when a local Docker build completes, and when a cron job that scrapes external data runs into an error. In every case the feedback loop is immediate and requires zero context-switching.
Is AnyBar free?
Yes — AnyBar is completely free and open-source under the MIT licence. The source lives on GitHub at github.com/tonsky/AnyBar and the project accepts no payment. You can install it via Homebrew Cask in one line, or download the release directly from the GitHub releases page.
Who should use AnyBar?
AnyBar is squarely aimed at developers, sysadmins, and power-users who live in the terminal and want ambient feedback from their toolchain without opening another window. If you routinely kick off long builds, run scheduled scripts, monitor server health, or chain shell commands together, this is the kind of glanceable signal that pays off dozens of times a day.
It is emphatically not for someone who wants a self-contained monitoring app with a UI, prebuilt integrations, and sensible defaults. AnyBar is a primitive, not a product — you bring the meaning. Non-technical users will find nothing here; developers will find an underrated gem.
It pairs naturally with tools like Alfred (trigger colour changes from workflows), Hammerspoon (bind status changes to Lua scripts), or any CI system that can run a shell command on job completion.
How does AnyBar compare to alternatives?
There are a handful of menu-bar status tools, but most solve a different problem. Bitbar / SwiftBar let you put arbitrary script output — text, icons, submenus — into the menu bar; they are far more powerful but also far more complex to set up. If you want rich dropdowns with clickable actions, reach for SwiftBar. If you want a single, scriptable signal dot with no configuration overhead whatsoever, AnyBar wins on simplicity.
xbar (the spiritual successor to Bitbar) is similarly full-featured and plugin-driven. Again, more capable, more ceremony. One Switch and similar utilities occupy a different lane entirely — they toggle system settings, not expose a programmable signal.
AnyBar's closest spiritual relative is a Unix named pipe with a visual renderer bolted on. If that sentence appeals to you, you already know whether to install it.
What are AnyBar's limitations?
Honesty first: AnyBar is a single-file, community-maintained project and it shows. There is no automatic update mechanism, no macOS Settings pane, and Retina rendering of custom images requires you to supply correctly named @2x variants yourself. The UDP protocol is unencrypted and unauthenticated — fine for localhost automation, a non-starter for networked use without a wrapper. The app has also gone through stretches of slow maintenance as macOS APIs evolve, so always confirm it is notarised and runs cleanly on your current macOS version before wiring it into anything critical.
