Dashboard
The day in one screen: what is waiting, what is late, and what moved since you last looked.
A desktop app that pulls your code reviews, mail, messages, calendar, money and notes into a single frame — kept on your machine, encrypted with a key that never leaves it.
macOS · Linux · Windows — built on Tauri 2
onibi-app#51 is the only thing actually blocked — CI red since 14:02, waiting on you.▍
Modules
Every module reads the same way — scope, list, reading pane — so nothing has to be learned twice. Turn on only what you use.
The day in one screen: what is waiting, what is late, and what moved since you last looked.
Pull requests across every git account you own, with what is actually blocking each one — reviewer, CI, or you.
Unified inbox over IMAP and Microsoft Graph. Remote images are proxied, never fetched by the message itself.
Telegram and WhatsApp threads sitting next to the work they belong to, instead of in another window.
Your own calendar first. Invites that arrive by mail become events without asking a third party for permission.
Long-form notes and documents, written in the app and kept in the same encrypted store as everything else.
Hours reconstructed from the traces work already leaves behind — commits, reviews, cards — instead of from memory.
Accounts, spending and runway, in the currencies you actually hold, with the numbers staying on your disk.
Cloud accounts, health and cost per client and per project, read through keys that can only look.
A local knowledge graph, so the assistant can recall context instead of re-reading everything you own.
Architecture
The app is complete before it ever talks to a server. Sync is something you switch on, not something you inherit by installing.
Data lives in a local SQLite database under your home folder. No account and no connection are needed to open the app and work.
The master key is generated on your device and stored in the operating system keychain. It is never uploaded, and no copy exists on our side.
If you turn on Pulse Cloud, anything that leaves the device is already AES-256-GCM ciphertext. The server stores blobs it cannot read.
Because the server never holds your key, we cannot recover your data if you lose every trusted device together with your recovery code. That is a trade this design makes on purpose.
Privacy
Privacy here is not a policy page bolted onto a product — it is the reason the product is shaped the way it is.
Content is encrypted with AES-256-GCM using a key that lives in your OS keychain. Holding the key is what proves the data is yours.
Optional sync uploads encrypted blobs. There is no debug view, no support tool and no query that turns them back into your content.
Nothing you connect is mined to build a profile, and no third party buys access to it. The app has no advertising business to feed.
Export your data in open formats, disconnect any integration from Settings, or delete the local database and be genuinely gone.
AES-256-GCM
Everything that leaves your device is sealed before it goes — and only your device can open it again.
sealed on deviceConnections
Every connection is added by you, one at a time, with the narrowest access that makes the feature work — and can be revoked from Settings at any moment.
Two-way sync of your events, so a meeting created in the app shows up in Google Calendar and the other way around.
OAuth 2.0 · calendar scope
Reads your inbox over IMAP or Microsoft Graph, using an app password or a token you generate yourself.
IMAP · Graph · app password
Pull requests, reviews and CI status for the accounts you link — one token per account, each kept in the keychain.
Personal token · per account
Your own bot bridges to the app, so you can drive it from your phone without a middleman holding the conversation.
Bot token · self-hosted
Digests and drafts run through Claude only when you ask for them. Without it the app still works — just without the assistant.
Opt-in · no shell access
Read-only keys used to show the health and cost of infrastructure you already pay for. Nothing is provisioned on your behalf.
Read-only keys
About Google user data: Mussi Pulse's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data powers the calendar module inside your own app, is stored encrypted on your device, and is never sold, used for advertising, or read by a human — read the full disclosure.
Platforms
Tauri 2 with the native webview: a real desktop app with a real tray icon, not a browser tab wearing a costume.
Apple silicon and Intel, with a menu bar tray that keeps the app alive when the window closes.
private betaAppImage and .deb out of the same build pipeline, with the secret service for keys.
private betaWindows 10 and 11, with keys held by the Windows credential manager.
private betaMussi Pulse is built in the open by one person, for real daily use before anyone else's. If you want in when the beta widens, write and say what you would use it for.
No public download yet · no account needed to run the app