Griasa

Griasa

A promise with a date turns up when the date passes. One without a date never turns up at all.

Griasa records your meetings on your own Mac, works out who promised what, and puts the second kind in front of you before your next call with the person you owe. A menu-bar app, not a service.

Download for macOS · The project page · What changed

Five minutes before a call, without taking keyboard focus. Everybody in these screenshots is invented — the app is pointed at a made-up team to photograph it, with Support/shoot-docs.sh .

What it does

Before the call. Minutes before a calendar event, a panel appears with who is on it and what you last discussed. Open promises are grouped by *why* you are being shown them — overdue, promised in an earlier call with exactly these people, from a one-to-one with somebody in the room, or with these people from somewhere else. A promise involving nobody in the room is not shown at all. One button opens the Zoom or Meet link and starts recording.

During. Your microphone and everything the Mac plays are captured as two tracks, which is what lets the transcript say who was speaking. Make a reminder from anything on screen (⌃⌥⌘R) and it remembers the app, window and browser tab it came from. Hold a key and talk, and the words land in whatever app has focus.

After. Promises are pulled out of the transcript — who took what on and by when — split into what you owe and what you are owed. A later conversation can *propose* closing one, and has to quote the sentence that says it was finished; nothing closes itself. Anything old and undated gets asked about, because that is the kind that never surfaces on its own. Every colleague gets a page built from the meeting roster, with no setup step.

And your own assistant can read it. Claude Code, Codex, Cursor — anything speaking MCP — over a local, token-protected, read-only endpoint, and Claude Desktop installs it in one click.

Your day on one screen. Today shows the meetings ahead and what you and each table owe each other, your overdue promises, what your team is late on and the decisions due for another look. A morning brief brings it up at 8:00, and a desktop widget keeps it in view. Each meeting also yields its decisions: what was settled, why, by whom, and when to look at it again.

From the iPhone, hands-free. No iPhone app is needed. Say "Hey Siri, Griasa note" in the car, or save a voice memo or a recorded call to iCloud Drive, and it is waiting on the Mac as a meeting with its promises. Your dated promises sit in a "Griasa" list in Apple Reminders, and ticking one on the phone closes it here.

Everything runs at once: you can dictate while a conversation is being recorded. Most of the pieces are small, and Apple could ship several of them tomorrow. What is hard to copy is that they are one thing — the reminder made during a call, the promises extracted from that same call, the page for the person who made them and the brief before the next meeting with them all point at the same people and the same history. Separate apps would need separate integrations and would still lose the joins, because a join is not a feature any one of them owns.

Every feature, by the name used for it in the app, is in [docs/FEATURES.md](docs/FEATURES.md). [The project page](https://stari-am.github.io/griasa/) has the rest: more screenshots, what leaves your Mac and what doesn't, the engineering that turned out harder than it looked, and the questions people actually ask.

Privacy Policy

The short version is below; the full policy is at stari-am.github.io/griasa/privacy.html.

• Audio never leaves your Mac. Transcription is local — Apple's recognizer or whisper.cpp. There is no Griasa server and no account.
• Text stays on the Mac by default. A new install uses a local model that Griasa sets up after one question; Anthropic, OpenAI or Gemini are used only if you choose one.
• The calendar is read, never written. Reminders are created, but only when you ask for one.
• API keys are kept in the macOS keychain, encrypted, not in a plain preferences file.
• Every permission is optional, and the app says what stops working if you decline it.
• An optional reminder to tell people they're recorded. The other side of a call gets no recording indicator from macOS. Turn on *Settings → Meetings → Remind me to tell everyone*, and starting a recording offers a sentence to paste into the call's chat.
• Notes from other tools come in too. *Import Meeting Notes…* turns a ChatGPT Record, Zoom or Meet summary into a Griasa meeting — promises, people pages, the brief — dated by when the meeting happened.
• Old audio can delete itself. Transcripts and notes are kept; the audio of transcribed recordings can be removed after a chosen period (*Settings → Meetings → Recordings on disk*). It is nearly all of the space recordings take.
• Chats you bring in stay on the Mac. Conversations (a Telegram export you choose, only the chats you tick) are stored in a local database that only your account can read, summarized by the same model as everything else, and deleted with *Delete chat*. Assistants can offer chats only if you switch on *Let assistants add to Griasa* (off by default), and what they offer waits for your review.
• Companies can lock it down with MDM — on-device AI only, a company model server, MCP off. See Support/mdm.

Download

[Download the latest release — signed, notarized, universal](https://github.com/Stari-am/griasa/releases/latest), or ./build.sh to compile it yourself.

With Homebrew, one command installs the app and both engines it uses (whisper.cpp for speech, llama.cpp for the on-device AI):

brew trust --cask stari-am/tap/griasa

brew install --cask stari-am/tap/griasa

Homebrew 7 loads casks from taps outside its own only after you trust them; the first line does that for this one cask.

Free, and nothing is held back: there is no license check, and under GPL-3.0 there could not be a meaningful one. If it saves you time, $29 on Ko-fi would make my day — any amount does, and none is fine too.

Think of it the way you think of WinRAR: the trial never ends and it keeps working whether or not you pay. WinRAR apparently makes real money like that, which leaves the mystery nobody has solved in thirty years — *somebody* pays. Feel free to be one of the somebodies.

The two things that make the list shrink: evidence that something was finished, and a question about what has carried no date for a month.

---

Documentation

Everything below is for running, building and changing it.

How dictation behaves

Build & run

./build.sh        # produces "Griasa Dev.app"

open "Griasa Dev.app" ./test.sh # the invariant checks; release.sh runs these first

A local build announces itself: amber DEV icon, its own file name, "Griasa Dev" in Privacy settings and Activity Monitor, and a squared-off menu-bar glyph. It also uses its own bundle identifier, am.stari.griasa.dev. That last part is not cosmetic — macOS stores a privacy grant against the identifier *and* the signature it saw, so two differently-signed builds sharing one identifier overwrite each other's grants and both end up asking every launch. Separate identifiers cost one round of permission prompts, once. release.sh does none of this; the signed build carries the real identifier, icon and name.

test.sh checks the rules live typing must never break — emitted text only ever grows, a hypothesis that re-words the start of an utterance may not extend its end, the language leg locks once. The first two were regressions that actually shipped; they now fail a command instead of a text field. There is no test framework involved: swiftc compiles PartialStabilizer.swift with the checks and the binary exits non-zero, so this works on a machine with only the Command Line Tools. Each failure message states the rule and why it matters, because "expected true, got false" tells whoever reads it nothing.

Benchmark. How well Griasa finds promises is measured on six invented meetings in benchmark/ — Russian, English, Ukrainian and mixed, from a 12,000-character sync to a 90,000-character roadmap session — each with the promises a person marked by hand. "Griasa Dev.app/Contents/MacOS/Griasa" --benchmark benchmark/meetings runs today's single pass, the long-meeting path and (with --cloud ) a cloud reference on them and prints recall, precision and mine/theirs accuracy. Nobody in them is real, so anyone can rerun it and compare.

Distribute it yourself

./release.sh      # signed + notarized dist/Griasa-<version>.dmg — the one on Releases

./dist.sh # ad-hoc signed dmg, no Apple account needed

release.sh is the path used for the published build: Developer ID signature, Hardened Runtime, Apple's notarization ticket stapled to both the app and the disk image, then verified the way a stranger's Mac will — spctl, stapler, and lipo -archs on the finished file rather than on the build settings. It needs a Developer ID Application certificate and a stored notarytool credential; run it without them and its preflight explains exactly what to create, including the two traps that cost the most time (importing the certificate with security import because a double-click reports -25294, and installing the G2 intermediate separately or codesign dies with "unable to build chain to self-signed root").

dist.sh is for handing a build to a colleague with no Apple Developer account: a universal dmg with an app icon, an /Applications shortcut, and INSTALL.txt.