It was 2 AM during a production incident. A payment service was returning 503s. I had PagerDuty open in one tab, the relevant GitHub PR in another, a Datadog dashboard in a third, Linear for the incident ticket, and Slack somewhere underneath all of it. I spent four minutes — four actual minutes — just trying to find the deployment that caused the regression.
The code fix took thirty seconds. Finding it took four minutes.
That’s the problem DevBar solves.
The 20-tab problem
Every developer I know runs their browser in a state of permanent tab debt. GitHub for PRs. Jira or Linear for tickets. PagerDuty or OpsGenie for alerts. Datadog or Grafana for metrics. GitLab CI for pipelines. Slack for everything else.
The tools are all good individually. The problem is the switching. Every context switch costs attention. You lose your train of thought, you miss the notification that arrived while you were in the wrong tab, and you spend a non-trivial fraction of your workday just navigating between windows that should be talking to each other.
The deeper issue: browser tabs are invisible. You can’t see your open PagerDuty incident while you’re writing code in VS Code. You close the browser to focus, and now you’re flying blind.
The insight: the menu bar is always there
macOS engineers have one piece of screen real estate that’s always visible regardless of what application is open: the menu bar. It sits at the top, persistent, above everything else.
The idea for DevBar started there. What if the most important signal from your entire developer stack — pending PR reviews, active incidents, failing pipelines, unacknowledged alerts — was always one click away, regardless of what you were doing?
Not another browser tab. Not another Electron app eating 400MB of RAM. A native menu bar app that connects to your tools and surfaces only what needs your attention.
What DevBar actually does
DevBar aggregates 18+ integrations — GitHub, GitLab, Jira, Linear, PagerDuty, OpsGenie, Datadog, Grafana, Prometheus, Sentry, Slack, Notion, Confluence, Bitbucket, Jenkins, CircleCI, ArgoCD, and more — into a single macOS menu bar icon.
Open the popover and you see a unified feed: open PRs waiting on your review, incidents that fired in the last hour, tickets assigned to you, recent deploys. All of it filtered to what’s actually relevant to you, not a firehose of everything happening across the org.
A few things engineers have told us they couldn’t go back from after trying DevBar:
The command palette. Hit your configured shortcut from anywhere in macOS and you get a spotlight-style interface into all your tools. Jump to a PR by number, open an incident, search tickets — without switching applications.
Real-time push. DevBar uses WebSocket connections to the backend, which receives webhooks from your integrations. When PagerDuty fires, you see it in the menu bar within a second. No polling. No 60-second delay while you’re heads-down in an editor.
The manager panel. For engineering leads, DevBar surfaces DORA metrics — deployment frequency, lead time, change failure rate, mean time to recovery — aggregated from your actual CI/CD and incident data. Not a survey. Real numbers from your pipeline.
Why not just use the native apps?
PagerDuty has a macOS app. GitHub has notifications. So do most of the others. The issue isn’t that individual apps don’t have desktop clients — it’s that running 12 separate menu bar apps creates its own kind of noise. DevBar replaces that with a single, unified, configurable view.
You decide which integrations are active. You set thresholds (only show incidents with severity P1/P2). You configure which repos and teams are relevant to you. The result is signal, not noise.
Where we are and where we’re going
DevBar is in active development. The integrations list is growing, and we’re working on team-level features: shared dashboards, escalation routing, and org-wide DORA rollups.
If you’re an engineer or engineering manager who’s tired of tab-switching during incidents, download DevBar and tell us what you think. We read every piece of feedback, and the roadmap is heavily influenced by what teams actually ask for.
The GitHub repo for the issue tracker is at github.com/devbar-app. If something’s broken or missing, open an issue. If something’s working well, we want to know that too.
We built this because we needed it. Turns out, so did a lot of other people.