A little better.
With every release.

What's new

• A meeting can be kept in your own Google Drive. Connect the Google account you want it in, pick a recording, and Clario copies the playable file there — into a folder of its own, under a permission that reaches nothing else in your Drive. Settings shows what is up there and how much room is left, playback streams straight back out of it, and taking one down moves it to your own trash. The file is yours in your account; Clario keeps no copy of it anywhere else.
• You can edit the minutes by changing the words themselves. Select a phrase in the minutes and say what it should be instead; Clario changes that phrase and leaves everything around it alone. It tells you what it changed before you keep it, the same selection works whether you dragged upwards or downwards, and a mark you replaced keeps its colour and follows the words that took its place. Editing twice in a row now works — the second change used to be refused.
• Summarise again asks what the meeting was for. One line, one field, before it runs: what Clario should know about this meeting. Given a purpose, the minutes come back about that rather than about whatever was loudest. It stays what you said, never turned into an outcome nobody reached.
• Two walkthroughs open where they apply. One on the dashboard for keeping a meeting in your own Google Drive, one the first time you open a meeting's minutes, for editing them. Each waits for the screen it is about instead of arriving at launch, each comes once, and neither closes by a stray click beside it — only Explore or Skip.
• Playback starts on half a megabyte instead of eight. A meeting kept in Drive begins playing almost at once rather than after the first eight megabytes have arrived, seeking answers the place you last dragged to rather than every place on the way, and a window that is taking too long says so instead of looking like nothing is happening.

Bug fixes

• The pinned tabs on a meeting stay where you can press them. They reached neither the top of the pane nor the page's own background, so the row floated in the middle of the page and one thing at the foot of the screen sat over the controls.
• A moved mark no longer locks the minutes. Moving one used to refuse every later edit in that meeting until it was reopened.
• The minutes are not ringed while you type into them. The focus outline drawn around the whole pane made an edit look like a form to fill in.

First look

This release ships two — Drive on the dashboard, and editing the minutes. Both wait on their own screen and appear once, for people updating from an earlier version.

What's new

• A recording carries on when your Mac sleeps. Closing the lid or putting the Mac to sleep pauses the recording, because nothing can be heard while it sleeps. When the Mac wakes, Clario reconnects the microphone, the screen and the other side of the call, and goes on recording by itself — however long it slept. A recording you paused yourself stays paused, and a locked screen keeps recording, since the call may still be going on with the screen dark.
• Minutes say what happened, not what was talked about. The instructions the summariser works from were rewritten from scratch. Minutes now report what was asked for, decided, put on hold or left open, one point to a bullet with the thing it is about in bold — so a walkthrough comes back as what was said about each screen, not a list of the screens. A plain statement stays plain even where the speech recognition mangled its words, and decisions made in Hindi are no longer the ones that go missing.
• Your bot's name always says it is a Clario bot. Settings edits your part of the name and shows the whole of what the room will see. Two Clario bots in the same meeting can now tell each other apart from the people in it, instead of each holding the room open for the other.

Bug fixes

• Reconnecting system audio brings the screen back with it. It used to reconnect the sound while the recorded video and the text read off the screen stayed frozen for the rest of the meeting.
• Clario says what went wrong in words. A failure used to be able to reach the screen as the inside of the app — one person signing in was shown a page of code where a sentence belonged. Every refusal now arrives as something a person can read and act on, and a password that is too short says exactly that.
• A recording survives its bot stopping unexpectedly. What the bot captured before it stopped is recovered and reaches your Mac, and the meeting says the recording ends early instead of saying nothing was recorded.
• One calendar can no longer send two bots to one meeting. Connecting a Google Calendar that another Clario account already holds moves it to the newest connection, rather than leaving both accounts sending a bot.

What's new

• Clario can tell you things. A notice arrives in the app when there is something worth saying — a release, a change to how something works, a fault we know about. It can carry a picture and a way out, and closing one closes it for good.
• What's new is a list you can go back to. Closing a notice used to be a decision nobody could undo. A Settings row now opens everything still available to you, closed or not, and opening one shows it again without bringing it back.
• You can report a bug from inside Clario, and get an answer. Describe what went wrong, attach a screenshot if you have one, and send it. The report carries a bounded excerpt of this machine's own log — no transcript, no summary, no meeting — so there is something to read besides the description. The reply comes back as a notice addressed to you, which is the first time a fixed bug has ever been news to whoever found it.
• The telemetry switch now names everything it does not cover. It said a bug report always goes, and stopped there — while the app was also reporting whether a notice had been shown and whether it had been closed, whatever the switch said. A switch that understates its own reach is the one thing it must never do, so it says both now.

Bug fixes

• A run that is ending stops asking. It went on counting refusals it could do nothing about; it now counts them, gives up, and says so.
• Two writers, one nameless file. A second user's writes were going to a file with no name. Both are named now.
• Clario's logs are Clario's. Server logs went into a system file four other products are read from, and "48 hours" of history was really a size limit wearing a time's clothing. They have their own destination now, rotated hourly, and 48 hours means 48 hours.

Known, on Windows

• Windows warns before it installs. The build is not signed yet, so SmartScreen asks. Choose More info → Run anyway.
• Clario does not watch for meetings quite as closely as on a Mac — it can name the application holding the microphone, but cannot show its icon.

Bug fixes

• Opening a meeting on a Mac no longer shows a blank window. 0.2.8's Mac build was packaged with a new interface and an old bridge between it and the rest of the app, so the screen asked for something that half could not answer and stopped drawing. Every meeting was affected and nothing else was: the recordings, transcripts and summaries were all still there, and this release shows them again. The Windows build of 0.2.8 was not affected.
• A build that cannot carry its own bridge now fails while it is being made. The fault above was invisible until somebody clicked a meeting, because nothing checked that the two halves of a package came from the same source. Packaging now counts them and stops if any are missing.
• A blank window is no longer silent. An interface error wrote nothing to the log, which is why the cause of the above took a day to find rather than a minute. It is written down now.

Known, on Windows

• Windows warns before it installs. The build is not signed yet, so SmartScreen asks. Choose More info → Run anyway.
• Clario does not watch for meetings quite as closely as on a Mac — it can name the application holding the microphone, but cannot show its icon.

What's new

• A Server Bot meeting says what is happening to it, all the way through. The bot left a meeting four minutes into a recording and the meeting appeared nowhere for another fifty-four seconds — the recording was crossing the network and being decoded the whole time, and the sequence had ended where the bot's knowledge ends rather than where the waiting ends. Two steps were missing and are there now: Downloading the recording, which counts the bytes on disk against the size the transfer declared and says it is safe to close the window, because the transfer runs outside it and picks up where it left off; and Reading the recording, which asks that the window stay open, because that work happens in it.
• Send Clario shows the meeting and the bot instead of describing them. The dialog was five stacked blocks of prose. It is Meet's mark, the bot's mark, and a rule between them that is dashed until a link parses and solid once one does — the same language the calendar screen already speaks, so anyone who has seen that screen has read this one. The code sits under the marks as the headline, and a link Clario cannot read is refused within the keystroke rather than in a sentence underneath.
• The three things that are different about sending Clario are three marks and a tick. The fine print is gone. What it carried has not gone with it: the middle mark now says Clario's servers capture the meeting, because naming a boundary without naming who receives the recording is not consent. That the recording comes back is said by the run itself, where it is true, rather than in advance.
• The empty library wears Clario's mark and stops listing its own buttons. The sentence named Record, Upload and Send Clario — the three buttons directly beneath it — so the screen said its three ways twice. What is left is the half no button says: everything lands in one place, and the transcript is made on this Mac.

Bug fixes

• A summary that comes back in a shape Clario cannot read is asked for again, and says so. It failed the whole job on the first unexpected response. It retries once now, and the row reads Unexpected response. Retrying… while it does, rather than sitting on Summarising through a wait nobody could account for.
• Mac updates work again. 0.2.7 shipped without the file that tells Clario where its updates come from, so every check failed with a message about the connection when nothing was wrong with it. A Mac already running 0.2.7 cannot fix this by checking — it has no way to look. Download 0.2.8 from the site once and updating works from then on. Windows was never affected.

Known, on Windows

• Windows warns before it installs. The build is not signed yet, so SmartScreen asks. Choose More info → Run anyway.
• Clario does not watch for meetings quite as closely as on a Mac — it can name the application holding the microphone, but cannot show its icon.

What's new

• Clario runs on Windows. Recording, local transcription, screen reading and summarising all work there, from the same code that runs on a Mac. The engine is built for Windows and runs on the CPU: an hour of meeting transcribes in about two minutes, against roughly one on a Mac's GPU, for a job nobody sits and waits for.
• Windows notices a meeting too. When something has held the microphone for a while, Clario asks whether to record it — the same question, read from what Windows already writes down rather than from a helper of ours. It names the application and, unlike the Mac, shows no icon beside it: there is no picture in the place Windows keeps that answer.
• Windows updates itself. New versions arrive the way they do on a Mac.
• The installer is drawn. It wears the same artwork as the Mac disk image, installs for you alone, and never asks for an administrator.
• What Clario is working on is a list you can open. The 2 working count in the top bar was a label with no way to reach what it counted. It names each meeting now, with the stage it has got to and the one figure that stage actually knows, and a row opens that meeting. A file being uploaded is counted alongside them.
• An upload is the same upload wherever you are. It used to belong to the screen that started it, so leaving the library lost the percentage and the dashboard never knew a file was coming in. There is one upload now, reported the same on every screen and counted in the bar.
• A summary being written in another shape survives a reload. Asking for a Client call or a Standup write-up spends a provider call, and reloading the window lost track of it — so the menu offered to write the same one again, and pressing it paid for it twice. The write is held where it actually runs, and a window that comes back finds it and waits on it.

Bug fixes

• A recording interrupted by a crash is given back. A meeting only entered the library when it stopped, and the audio file only stated its true length when it closed — so a force quit or a flat battery left an hour of audio on disk, inside a file claiming to be empty, belonging to no meeting. Both halves were always recoverable and neither was being recovered. Clario now finds them when it opens.
• A meeting recorded without the screen plays back whole. Turning the picture off left playback falling through to the room's track alone, so you heard everybody except yourself. The two tracks are added together now.
• One damaged row no longer hides the whole library. Every meeting is re-read on the way out of the database, and the first row that would not parse took the entire list with it — two hundred good meetings showing as none. A row that cannot be read now costs that row.
• Deleting a meeting retries when Windows has the file locked. Windows will not delete a file something still has open, where a Mac simply does.
• The two voices in a transcript are Speaker 1 and Speaker 2. They were You and Others, which is a name-shaped label for something that only knows which microphone a line arrived on — and Others was drawn with an initial as though it were one person. Every transcript already recorded is relabelled.
• A long link in a transcript no longer drags the page sideways. A word with no space in it ran past the measure and took the whole pane with it.
• A transcript turn offers Copy, and only Copy. React, comment, highlight and clip sat beside it on every line of every transcript, and none of them could be pressed.
• Sending Clario to a meeting reads as a choice rather than an alarm. The three things that are different about it were set in a yellow box behind an exclamation mark, on a screen where nothing has gone wrong. They are said plainly now, one line each.

Known, on Windows

• Windows warns before it installs. The build is not signed yet, so SmartScreen asks. Choose More info → Run anyway.
• Clario does not watch for meetings quite as closely as on a Mac — it can name the application holding the microphone, but cannot show its icon.

What's new

• Summarising no longer has a consent switch of its own. Setting up a provider is the agreement. The switch had already stopped governing whether a summary could run, but three paths still enforced it — so the same question was answered differently depending on a toggle most people never found, and a pinned meeting quietly lost its transcript tools without it. The Settings row is gone with it.
• Sending a bot to somebody else's meeting still asks, and always will. That is a different question from whether this Mac may summarise its own transcripts, and it is untouched.

Bug fixes

• The app says what the server actually refused. Nine of the twelve refusals the server can send were reaching people as "Clario could not reach its server. Check your connection" — every expired session, every wrong password, every link belonging to another account. The server had answered each in under a millisecond. Two bugs reported the same day, one connecting a calendar and one in the share menu, were both this.
• The ask field stays open on a library with nothing summarised. It used to close itself there, on the reasoning that there were no summaries to search — but @ reaches a meeting's transcript, so the field was shut against questions the app can answer, on the newest library, which is the worst moment to hand somebody a control that does nothing.

Requires macOS on Apple silicon. Update from 0.2.4 happens in the app.

This release has no installable build. Its only published file is a block map — there is no disk image and no update payload — so nothing can install it and no installed copy can update to it. What it carried reached people in 0.2.6 instead.

What's new

• The app points at the server that answers. The server address had been held at loopback while the host still served the retired stack — correct at the time, and the reason a build from that period could not sign anyone in. The box has since caught up and the address now names it.

The entry is kept rather than deleted because a version that exists and cannot be had is worth being able to look up.

What's new

• Screen text is used more and explained less. It informs what was said without ever being reported as something that was said.

Bug fixes

• Summaries read as summaries. No [Moments: …] or Assignee: null left in the prose, the participants section is back, and quoted lines are the summary's own sentences rather than raw transcript.

Requires macOS on Apple silicon. Update from 0.2.3 happens in the app.

What's new

• A summary can be read at a glance, rather than waded through. Measured on a real one: 12 numbered sections, 42 bullets, and no bold, sub-headings or tables anywhere — the model was not underperforming, nothing had asked it for any of that. It now asks for bold on the few terms a reader scans for, sub-headings where a section runs long, and a table where the content is genuinely tabular.
• A line of the minutes can be heard, not only a quote. Play controls used to sit only beside action items and decisions, because those carry a verbatim quote that can be found in the transcript. Most of a summary is prose, and prose could not be played. The summariser reports the moment each bullet came from instead.
• The summariser records figures and named tools, and the prose marks them. The minutes marked only who an action item was given to and a date that was actually spoken, so a summary full of quantities and systems read as flat grey text. A highlight still means _this is something it recorded_, never _this looked important_.
• A new version says so in the bar. Updating already downloaded by itself and installed on quit, but the only place that said so was a row in Settings — so it worked and nobody knew. It refuses while a recording is running, and says why.

Bug fixes

• First run keeps its place across the restart the screen step needs. Screen recording is the one step that cannot be completed without relaunching, so the single flow that must restart was the flow that lost its position — a grant landed you back at the beginning.
• The dashboard and the library redraw when a meeting finishes. Both read once and kept the answer, so a recording that finished while you were looking at the dashboard did not appear until the screen was opened again. The work happening was visible; its result was not.
• Pressing a play control no longer sends the reader to the top. Playing changes state above the summary, and the whole tree was being rebuilt on every render — which throws away the scroll position of the panel you are reading.
• A table and a sub-heading render everywhere, not only on screen. They were reaching people as a wall of pipes and a literal ### Current Portfolio. Summaries already stored come good at render time.

Requires macOS on Apple silicon.

This repository does not record what went into this release.

It was built and uploaded by hand, before the release workflow could run. There is no v0.2.2 tag here or on the remote, and the commit that set the version to 0.2.2 was made sixteen minutes _after_ this release was published — the shape of a build cut from a working tree rather than from a tag. Every commit between the 0.2.0 and 0.2.3 tags came after it too, so none of them is what it carried.

The disk image is still here and still installs. What changed in it is the thing that was not written down.

This repository does not record what went into this release.

It was built and uploaded by hand, before the release workflow could run. The evidence that it cannot be reconstructed is in the history rather than missing from it: there is no v0.2.1 tag here or on the remote, package.json went from 0.2.0 straight to 0.2.2 — so 0.2.1 was never a version in this repository at all — and every commit between the 0.2.0 and 0.2.3 tags was made _after_ this release was already published, so none of them is what it carried.

The disk image is still here and still installs. What changed in it is the thing that was not written down.

Accounts, and a summary can be published to a link.

What's new

• This release requires an account. Signing in happens once at first run and then works offline indefinitely, but a fresh install cannot record until somebody has signed in. Existing installs will ask on next launch — meetings already on disk are untouched and stay local.
• A summary can now go to a link. It is encrypted before it leaves and the key travels in the URL fragment, which browsers do not send — so the server stores what it cannot read. Only the summary: never audio, never the video, never the transcript. Publishing again keeps the same URL, and taking a link down deletes it rather than forgetting it locally.
• Export and Share are menus. Export hands over the recording or the summary as a PDF; Share copies a public link or the text. Both say what they are doing on the row you pressed.

Requires macOS on Apple silicon.

The first release that can actually transcribe.

What's new

• The engine and models ship with the app. whisper.cpp, built from source at a pinned version, and the speech and voice-activity models, each verified by checksum. Nothing is downloaded on first run and nothing has to be installed by hand. The download is about twice the size; the app works the moment it opens.
• First run explains what it needs before macOS asks. The microphone, and screen recording for the other side of a call — and it says plainly what happens if you skip either. It also notices when a screen-recording permission has been granted but has not reached the running app, and offers to restart rather than leaving you guessing.
• Bring your own key, from whichever service you use. OpenAI, Anthropic, Gemini, OpenRouter, DeepSeek, Groq, Mistral, Together, xAI, or any OpenAI-compatible address — including a model running on your own machine. Each keeps its own key, and Clario lists the models your key can actually reach rather than asking you to remember one.
• Summaries send when you press Summarise. Settings says what leaves: the transcript and the text read off recorded screens. Audio never leaves this Mac.

Bug fixes

• 0.1.0 and 0.1.1 shipped without a speech engine or a model. They recorded, read the screen, and then failed — honestly, with a real error, and completely. This one carries both.

Requires macOS on Apple silicon. Signed with EMIAC Technologies' Developer ID and notarised by Apple.

A patch release whose only change is its version number.

It exists to prove the updater against a real, notarised, published release rather than against a fixture: an installed 0.1.0 finding this, fetching it, verifying it, and saying so. Nothing else in the application changed between 0.1.0 and 0.1.1.

The first release of Clario — a local-first meeting summary app for macOS.

What's new

• Your audio never leaves your machine. Recording and transcription both happen here, on this computer, and no audio file is ever uploaded anywhere. Summarising is the one exception: it sends the transcript text to the provider you choose, with a key you supply, and only after you have said yes. You can withdraw that at any time in Settings.
• It records both sides of a call at once. Your microphone and the other side, so it can tell who said what without any cloud service knowing either.
• It transcribes on this machine, and summarises with action items and decisions. Each one quotes the transcript it came from.
• Every meeting is kept in a searchable library. Clario answers questions about them.
• It updates itself. Clario checks for a new version shortly after it starts and every six hours, downloads it in the background, and then tells you — it never restarts itself while you might be in a meeting. Turning it off in Settings → Updating means it does not contact anything at all, rather than checking quietly.

Requires macOS on Apple silicon. Signed with EMIAC Technologies' Developer ID and notarised by Apple. Download the .dmg, open it, and drag Clario to Applications; on first run it will ask for microphone access, and for Screen & System Audio Recording if you want it to hear the other side of a call.