OpenWhispr 1.9.1
π Highlights
- βΉ Meetings stop when the call stops β Auto-end drops the 60-second countdown, so recordings finish about a minute sooner. If it called it wrong, a 30-second card puts you back into the same note.
- π Gemini for transcription β
gemini-3.5-transcribejoins OpenAI, Groq, and Mistral as a bring-your-own-key provider. - π₯ Granola import β Bring your meeting notes across from Granola's CSV export with dates, transcripts, and speaker names intact.
- π Account deletion stays in its lane β Deleting one account no longer touches another account's notes, your workspace content, or your downloaded models.
β¨ Also new
- A dictation pill for Agent mode, on the opposite edge of your display
- Screen Context permission during setup
- Your assistant can find free calendar slots, now 31 days out instead of 7
- Buy Enterprise in-app, with one-click entry to the web console
π Dictation
- A cyan-to-indigo processing glow replaces the rainbow beam
- Assistant answers paste back into the field you were typing in, or fall back to your clipboard
- Recording starts 4β5 seconds sooner for local-mode and signed-out users
- No trailing space after Chinese or Japanese text
π Fixes
- Performance β 1.9.0's recording-time CPU spike is fixed, and GPU packs that 1.8.3 deleted are now repaired at launch.
- Meetings β On Windows, meetings that recorded you but nobody else: a browser opened from the meeting link landed inside the process tree that system-audio capture excludes.
- Calendar β Recurring meetings on shared Microsoft calendars have names again.
- AI models β Stray
<think>tags stop leaking whatever their capitalization, and an Anthropic reply that hits its token limit no longer crashes cleanup. - Elsewhere β Settings stays open when you dismiss a dropdown, debug logs record which release produced them, packaged builds block untrusted file navigation, and the CLI bridge handles UTF-8 correctly.
π Thanks
Thanks to @hsusul, @AdityaPainuli, @Chadpiha, @boseq and @greatcoat, for their work on this release, and to @lingfish, @Nagell, @RonanCJ and @xlurie for the reports behind several of these fixes β and a warm welcome to first-time contributor @zhongwater123! π