Evidence, not just summaries
Important claims link back to the moment they were said, and AI answers carry a verified badge you can check claim by claim.
One private workflow that runs fully offline on your computer: prepare, capture, compare what changed, and create approved deliverables.
LocalNote helps keep meetings, commitments, and decisions connected. Review source moments instead of trusting a summary without context.
After a meeting, it can prepare an updated brief and draft correspondence for your approval. No email is sent automatically.
Try the fictional sampleChoose a step. This fictional, prewritten example shows the workflow without uploading a recording or requiring a login.
Many capabilities, one clear outcome: leave meetings with less to do manually.
Important claims link back to the moment they were said, and AI answers carry a verified badge you can check claim by claim.
Set a goal and LocalNote prepares the brief, the follow-ups and the file updates - each waiting for your approval. Nothing is sent on its own.
Recording happens in the app on your computer. No meeting bot, no extra guest, and no copy of your audio on someone else's server.
Bot-free local recording, speaker separation, uncertainty review, dictation and voice notes.
Semantic search, source-linked AI answers, evidence timeline and people context.
My Day, reminders, scheduled briefs, weekly recaps and approved file creation.
A project lives in two places: the documents that were agreed, and the meetings where things actually get decided. Work Guardian is the part of LocalNote that keeps those two honest with each other.
Import the project's documents — the statement of work, the plan, the agreement — and mark which copy is the approved one. Every version is kept, and each new copy replaces the last without ever editing it. The approved copy is never changed in place, by you or by the app. And if a page has no readable text — a scan, a photo of a page — Guardian says so plainly instead of guessing.
Guardian reads what the documents promise and what your meetings decided — deliverables, dates, owners, amounts — and keeps the exact words behind every claim. A claim from a meeting is tied to that meeting; a claim from a document, to its place in the document. Nothing is blended together, and one project's records are never checked against another's.
Five kinds of drift get flagged: new scope that was never agreed, a date that conflicts, an owner that changed, work waiting on something late or unproven — and approval checks that end, in the app's own careful words, "Approval not found in selected records." It never claims an approval didn't happen; it tells you it isn't in the records you gave it. Flags land in My Day under Needs review — the top three up front, each quoting both sides word for word. You confirm, dismiss, or set each one aside; a decision stands until the facts change.
For a flag you confirm, Guardian drafts the fix: a clarification note, or a corrected file saved as a new file — never over the original. Your approval is tied to that exact file's contents; if the file changes after you approve, the write refuses and explains why. And every step is written into a completion ledger — Proposed, Prepared, Approved, Saved, Sent, Acknowledged — where a step the app verified itself (it read the file back) is labelled verified, and a step you marked yourself is labelled as yours. The two are never blurred.
Work Guardian is off until you switch it on in Settings. It works on the documents and meetings already in LocalNote, on your computer — nothing new leaves your machine.
A meeting can end with everyone nodding — and two different memories of what was decided. The Agreement Network turns the decisions into a small packet the other side answers, in writing, bound to the exact words.
LocalNote gathers one to five decisions from a meeting, each backed by the exact words that were said. Nothing inferred slips in quietly — a decision the record doesn't support has to be put right by you before the packet can be finished.
You hand the recipient a single packet file — by email, by chat, however you already reach them. There is no LocalNote server and nothing to log into. They answer with a response file: confirm, ask for a correction, dispute, or decline — decision by decision. They never install LocalNote and never create an account. A ready-made invitation draft is written for your own email app; LocalNote itself sends nothing.
Every answer is tied to that packet's version and its fingerprint. Edit the packet and it becomes a new version: earlier answers stay attached to the words they answered, as history — they are never silently carried onto new wording.
A packet proves the answer matches the exact words. It does not prove who answered — and it says so, on its face. Nothing here is called a legal signature, because it isn't one. What you get is a clean, checkable record of who was asked, what they were asked, and what came back.
The Agreement Network is off until you switch it on in Settings. And when a packet is confirmed, it can propose an update to the project's approved record through Work Guardian — the same approval-bound, hash-checked path as every other fix. Nothing updates itself.
Most writing doesn't happen in your notes. It happens in email, chat and documents — everywhere. The Writing Assistant meets you there: select, press a shortcut, rewrite, done.
Select text in any app on your Mac and press the shortcut (⌘⇧E — changeable in Settings). A small preview shows the original beside the rewrite: improve, shorten, expand, make it professional or friendly, translate it, or ask for anything in your own words — all with the model on your device.
Nothing changes until you press Replace — and Replace only fires if the selection is still exactly what it was. Afterwards, LocalNote reads the text back to check the change really landed; if it can't verify, it tells you plainly and offers Copy instead. Your clipboard is restored afterwards, too — a rewrite never eats what you copied earlier. Dictation got the same protection.
Password managers, banking apps and secure fields sit on a protected list — shown in Settings, where you can inspect it and add your own. In those places, the assistant refuses before a single character is read.
Writing sessions are remembered as counts — which app, which action, how much text — never the text itself. There is no history of your words to leak, because none is kept.
The Writing Assistant is Mac first, and off until you switch it on in Settings. It reads only the selection you point it at, only when you press the shortcut.
A promise without time in the day is just a hope. The Day Planner takes the commitments from your meetings and drafts focus blocks for them — fitted around the calendar you already keep, and never written anywhere until you approve them.
LocalNote looks at what you owe — the commitments with due dates from your meetings — and at the calendar already on your Mac, or a calendar file you import, and drafts blocks of protected time that fit around what is already there. The promise due soonest gets its time first; nothing is planned into time that isn't free.
The plan arrives as a proposal — in your morning queue, ready to review block by block. Your approval is tied to that exact set of blocks: change one, and it becomes a new proposal for you to approve. Nothing reaches your calendar before that, and a plan is never quietly applied in the background.
If no calendar can be read, the planner refuses and says why — it will not guess at your day. A calendar file that is days old is labelled stale on the plan itself, so you always know how much to trust what you are approving.
Approved blocks are written to your calendar on this computer — and read back, to confirm they landed as approved. Or export the plan as a standard calendar file (.ics) and use it wherever you like. There is no cloud calendar sync: LocalNote never reaches out to a remote calendar.
The Day Planner is off until you switch it on in Settings. Writing to a calendar is a Mac feature today; the plan itself only ever comes from a calendar LocalNote could actually read.
Decisions hide in email as much as in meetings. Bring an archive in — single messages or a whole mailbox file — and read, search and answer it with the same privacy as everything else in LocalNote: entirely offline.
Import single .eml messages or a full .mbox archive exported from any mail app. Threads are rebuilt from the replies themselves, not just matching subject lines, and a message you import twice is recognised and kept once.
Open a thread and read it plainly, or search the whole archive by what was actually written. Mail search is its own thing — words from your email never leak into your meeting results, or the other way round.
HTML mail is converted to plain text at the moment it is imported; scripts and markup are dropped, and links are shown as text. There are no remote images and no tracking pixels — nothing inside an imported email can run, load, or report back to anyone.
Write a reply inside LocalNote and export it as a standard email file, ready to send from your own mail app. LocalNote holds no mail account of yours, has nothing to sign in to, and sends nothing itself.
Email is off until you switch it on in Settings. This stage is import only — LocalNote does not connect to your mail account, and there is no account to connect.
“Prepared” is not “done”. When you approve a change, Verified Execution carries it into the destination file — then opens that file again and checks what actually landed.
Every action starts as a proposal: this content, into this file, for this reason. Your approval is bound to the exact content — change anything, and the approval no longer fits.
The write goes through the same guarded path as Guardian's fixes: the file's current state is checked first, the write is atomic, a backup is kept — and afterwards the destination is read again, independently, and compared with what was approved.
Verified: the read-back matches. Failed: it differs — and you're told. Uncertain: it couldn't be checked — and you're told that too, instead of a confident guess. The three are never blurred into one green tick, and every landing leaves a receipt.
If the destination file changed after you approved, the approval is invalidated and the action goes back for review. You can cancel any action, and an emergency stop halts everything — and a write that already landed is never pretended away; the record says what actually happened.
A project usually has a task file of its own — a CSV or JSON list the team keeps. Project Sync keeps it in step with the project's meetings: promises heard there are proposed into the file you choose, through the same approve-then-verify path as everything above.
A promise is proposed as an update only when it names a task exactly — a row LocalNote created earlier and marked as its own, or one single row that matches on title, owner and due date. “Similar” is never good enough: anything weaker becomes a short question — is this that task? — and only your answer links the two. A file whose rows carry no stable identity, or fields LocalNote doesn't manage, is left alone, with the reason stated.
LocalNote remembers which promise went to which row, so syncing again proposes nothing it already proposed. And every change still walks the same door: proposed, approved by you one by one, written, and read back — verified, failed, or uncertain, in plain words.
For consultants, the expensive sentence in a meeting is “while you're at it…”. From a project's approved statement of work, the Revenue Pack proposes the rate card and the timesheet, waits for you to confirm both, and turns work outside the agreed scope into a change-order candidate with the arithmetic shown.
Rates are proposed from the approved SOW — never from a copy nobody approved — and time is proposed from your meetings. Neither counts until you confirm it. If a rate is unconfirmed or the time isn't, the candidate carries no total at all, rather than an estimate dressed up as one.
Amounts are worked out in exact whole-number arithmetic — no rounding drift, and totals are never mixed across currencies. Every candidate is labelled, in the app and in the pack: Not billable until approved. Approving one sends it through the same verified path as any other change: proposed, approved, written, read back.
In this stage, destinations are your own local files and project files, on this computer. Verified Execution is off until you switch it on in Settings — and there is no approve-everything button, on purpose.
Everything in the app today, in one place — and all of it runs on your computer.
Join the waitlist - the first public release comes with a full 30-day free trial.