Your Base over every app
One click in the menu bar — no window to hunt for, no app to switch to, Obsidian open or closed.
Point BaseBar at a .base file and it shows that view as a board — your filters, your grouping, your property names. Drag a card and it writes one line back into the note. Obsidian can stay closed.
macOS 13+ · One-time purchase · 30-day refund
Works with Bases, a plain folder of notes, or an old Kanban-plugin board.
# How it works
No sync engine, no account, nothing to configure twice. The board you already built in Obsidian, shown where your eyes already are — watch it happen.
BaseBar reads that file: its filters, the view you picked, what it groups by, the column order, and your own property names. It never writes to the .base.
One click and the board is there, over whatever app you're in. Several bases? Each one is a tab — and one base with two views can be two tabs.
BaseBar rewrites only the property the view groups by, inside that one note. Everything else in the file is untouched, and Obsidian picks it up whenever you open it.
# the whole idea
BaseBar doesn't ask you to rebuild a board. It reads the Base you already made in Obsidian and renders that exact view in the menu bar — including the names you gave your properties.
filters:and:- file.inFolder("tasks")1- file.hasTag("task")properties:due:displayName: Deadline4views:- type: kanban-viewname: Pipeline2groupBy: status3order: [due, owner]4- type: tablename: Everything
which notes are on the board
The filters are yours: inFolder, hasTag, and the != rules a view uses to hide finished work. BaseBar matches the same notes Obsidian does.
which view you meant
A base usually holds several views — by status, by weekday, a flat table. You pick one, and that one is the board. Add the same file twice and you get two tabs.
what makes the columns
Whatever the view groups by — status, stage, day — becomes the columns, in the order the view fixes. That one property is also the only thing BaseBar ever writes back.
what goes on a card
The properties the view lists, labelled the way you labelled them. Your board about films has a “Runtime”, not a “priority” you never set.
.base file. The one thing it writes is the grouping line inside a note — nothing else in the vault is touched.# What it looks like
Same app, three different vaults. Nothing here is a mockup — these came out of the version you'd download today.



The popover is as wide as your columns need and scrolls when there are more — these are cropped to the first few so they fit on the page.
# What it can read
Bases is the main road, but you don't have to be on it. Whatever your vault already looks like, there's a way in.
A .base file you already built. BaseBar takes its filters, the view you choose, what that view groups by, the column order and your property labels.
filters:
and:
- file.inFolder("tasks")
views:
- type: kanban-view
name: Pipeline
groupBy: statusPoint it at a folder instead and every note in it becomes a card, grouped by whichever frontmatter property you name.
---
status: in progress
due: 2026-09-22
---
Ship notes and the DMG.The abandoned Kanban plugin kept boards as one note. BaseBar reads that format directly — ## headings are columns, - [ ] lines are cards — and moving a card moves its line.
## Backlog
- [ ] Write the changelog
- [ ] Call the bank #high
## In progress
- [ ] Record the demo# What you can do
No roadmap promises — just what ships today. Every tile is a live loop of the real behaviour.
One click in the menu bar — no window to hunt for, no app to switch to, Obsidian open or closed.
Drop a card in another column and BaseBar rewrites only the property the view groups by.
Fields come from the base, and each one offers the values you already use. Pick, don't retype.
Cards are labelled the way you labelled them in Obsidian — not with a status/priority guess.
One base, several views. Choose one per tab — by status here, by weekday next to it.
Tasks, a media plan, a reading list — each a tab in the same popover.
Click a card's title to jump straight to the full note in Obsidian.
There the moment your Mac starts. No account, no sync, no server.
↔Nothing here needs a plugin: Bases ships with Obsidian, and BaseBar reads your file without changing a byte of it.
# What it doesn't do
Fewer surprises means fewer refunds. BaseBar only ever reads and writes plain Markdown — so here's exactly what it won't do, before you pay for it.
30 daysmoney-back, no questions asked
Early access is $9.99 — locked in before it goes to $19.99.
See pricing & reserve your price# Installation
BaseBar is made by a solo developer and isn't notarized yet, so macOS shows a warning on first launch — the two highlighted steps below. Here's exactly what you'll see and what to click.
Use the link in your email to download BaseBar.dmg.
Thanks for your order — grab the app below and follow the steps.
Download BaseBar.dmgOpen the DMG and drop the BaseBar icon onto the Applications folder.
macOS can't verify the developer. Open System Settings → Privacy & Security, scroll down, click Open Anyway.
That's the quarantine flag, not real damage. Run the one-line command in Terminal — copy it from the window.
A short wizard asks where your tasks live — a .base, a folder, or a board note — and that's the whole setup.
No Base yet? The wizard writes a small working board into your vault so you can see it move.
?Why the “unverified” and “damaged” warnings?
BaseBar isn't notarized by Apple, so macOS can't confirm who built it and shows those warnings. Notarizing requires a paid Apple Developer Program membership — $99/year, and as a solo developer on a tight budget I haven't bought in yet. The app only touches your Markdown files; its one network request is a daily check for a newer version, which you can turn off. Once BaseBar earns enough to cover it, I'll notarize and these steps disappear.
# Pricing
One-time. Price goes up after launch.
macOS 13+ · Secure checkout when it opens
# what you get
The native menu-bar app itself — a universal .app for Apple Silicon and Intel that you drag into Applications. Works whether Obsidian is open or closed.
No Base yet? The setup wizard writes a small working board into your vault — no plugins to enable, nothing to configure.
Every 1.x release is included — you buy once, updates keep coming at no extra charge.
How you get it
No account to create, no activation server. It's just a file you own.
# FAQ
Obsidian helps, Bases is optional. A .base file is the best way in — BaseBar reads its filters, its view and your property names. But you can also point it at a plain folder of Markdown notes, or at a board note in the old Kanban-plugin format. It reads files, not a database.
Your .base file is never written to at all. In a note, BaseBar rewrites exactly one line: the property your view groups by, and only when you move a card. Adding a note creates a new file. Nothing else in the vault is touched.
No. There is no account, no sync and no analytics in the app — your notes never leave your Mac. BaseBar makes exactly one network request: once a day it downloads basebar.app/version.json to see whether a newer version exists. That request carries nothing about you or your vault, and you can switch it off in Settings.
macOS 13 (Ventura) or newer, on both Apple Silicon and Intel Macs.
Yes — 30 days, no questions asked. If BaseBar isn't for you, email us and we'll refund it.
The one you pick. BaseBar lists every view in the file and you choose per tab — so the same base can appear twice, grouped by status in one tab and by weekday in the next.
They still show up. A note with no value for the grouping property gets its own lane at the end instead of disappearing, and a view with no grouping at all is simply shown as a list.
Not right now. BaseBar is a native macOS menu-bar app, and there's no mobile or Windows build planned.
BaseBar is made by a solo developer and isn't notarized yet, so macOS asks you to confirm on first launch. It's standard for independent Mac apps — the Installation section shows each step.