A thin bar on the edge of your screen shows how each deployment, check, payment and usage limit is doing. Point at a tool for the details.
// Kitbar keeps watch while you work. struct FunnelBreakdown: View { let source: String var body: some View { Chart(steps) { step in BarMark(x: .value("Step", step.name), y: .value("Users", step.count)) } } }
Eight tools, one bar, no tabs to keep open.
Paste a read-only key per tool. Claude Code and Codex connect with one click.
Green when all is well, turning while it builds, red when something failed.
Point at a tool and its card opens. Redeploy, re-run checks, or open the page.
Faint while there is nothing new, bright when there is news you haven't seen.
Switch on the ones you use. More are on the way.
More connectors arrive regularly. Missing one? Tell us.
Right or left edge, any display. Tuck it away to a thin line and bring it back with a shortcut.
Kitbar asks your tools directly, the way their own dashboards do.
No subscription. Your license key arrives by email right after checkout.
All of yours. One key activates any number of them, and Settings lets you free one you no longer use.
Write to us within 7 days of buying and we will refund you in full.
Into your system keychain, and from there only to the service each key belongs to: your Vercel token goes to Vercel, your Stripe key to Stripe. The privacy policy lists every request the app makes.
No. Claude Code and Codex report your limits themselves: Kitbar runs them on your computer and reads their answer. It never touches the sign-in they keep. Claude Code reports limits for Pro and Max plans; API usage is read with an admin key you make yourself.
A key that can read, and nothing more: the Settings page of each tool says exactly which permissions, with a link to where the key is made. Redeploy and re-run need a key that may write; the card tells you when yours cannot.
macOS 15 Sequoia and later, on Apple silicon and Intel Macs, and Windows 10 and 11.
Selling it ourselves lets us ship updates the day they are ready. Every build is signed and checked by your system when you open it; the Mac build is notarized by Apple.
