Version 0.3.0 · updated 2026-09-22
Known issues.
Everything we know doesn't work yet, with the workaround where there is one. If you hit something that isn't here, tell us and it goes on this list.
- Workaround since 0.1.0
macOS warns that the app is from an unidentified developer
Early builds are not yet signed with an Apple Developer ID or notarised, so macOS shows a warning on first launch. Permission grants (microphone, system audio) can also be lost when an unsigned build updates.
What to do: Right-click Recordist in Applications, choose Open, then Open again. Re-grant permissions in System Settings → Privacy & Security if a recording comes out silent after an update. Signed builds are the first item on the go-live list.
- Open since 0.1.0
Windows and Linux versions are in early access
Both versions are built from the same code as the Mac app and compile in our test pipeline, but we have not yet verified a full recording on that hardware ourselves. Recording may fail or capture only one side of a call.
What to do: If you try one and it works, or does not, tell us: a confirmed call on each platform is what moves them out of early access. Diagnostics (Settings → General → Export diagnostics) contain no audio or transcripts.
- Workaround since 0.1.0
Local notes take a few minutes on 8 GB Macs
Measured 2026-09-23 with Qwen2.5 1.5B, the model the built-in engine picks on 8 GB: a 5-minute clip took about 35 seconds, so a 40-minute meeting takes about five minutes on an 8 GB Apple-silicon Mac. Measured 2026-09-20 with the larger Qwen3 4B model: a 39-minute meeting takes about 12 minutes; an 18-minute meeting takes about 4 minutes. 16 GB machines get a larger context window and are roughly three times faster. The earlier out-of-memory crashes are fixed; the machine stays responsive during generation.
What to do: Use your own Anthropic or OpenAI-compatible key (about 20 seconds per meeting; the transcript text is the only thing sent), or keep the 1.5B model the engine picks on 8 GB machines (Settings → AI notes → Model) rather than switching to Qwen3 4B.
- Fix planned since 0.1.0
Multiple remote speakers share one label
Your own voice is attributed correctly because it is recorded on its own channel. Everyone else arrives on the system-audio channel and is labelled as one remote speaker, which you can rename per meeting. Splitting that channel into Speaker 1, Speaker 2 and remembering names is planned; no date is promised.
- Open since 0.1.0
Checkout opens plan by plan
Stripe checkout, the license-key emailer and the recovery endpoint are written and tested but not yet deployed for every plan. Where a plan's checkout is not live, its button on the pricing page collects your email and the plan you want instead.
What to do: Recording, transcription, search and Prep Briefs need no purchase. Leave your email and we write once when the plan opens.
- Workaround since 0.1.0
Google Meet in Chrome needs the extension for titles
Browser meetings are detected through the microphone like any other call, but the meeting title and attendees are only available if the Chrome extension is installed and paired, or if the meeting is in your calendar. The extension is being prepared for the Chrome Web Store.
What to do: Add the meeting to your calendar so the title comes from there, or rename the meeting afterwards. Ask us for the extension early at [email protected].
Still stuck? Ask Wren (bottom right) or email [email protected].