v0.12.253+12253-macos

BasedHardware/omiv0.12.253+12253-macosSep 1, 2026by mdmohsin7

AI Summary

This candidate release introduces model identification in response popovers and fixes a bug where meeting notes incorrectly labeled native messaging app calls.

Key Highlights

Response Context popovers now reveal the actual model name served, distinct from the requested alias.
Model identification is now available for voice answers and the latest message.
Meeting notes no longer incorrectly label the first speaker as 'Speaker 1' for native messaging apps when the contact name is visible.

New Features

Model identification in response context popover
Improved meeting notes speaker labeling for native apps

Full Release Notes

## OMI Desktop v0.12.253

### What's New
- Every answer now shows which model actually produced it: the Response Context (i) popover — including on the latest message and on voice answers — gains a Model row reporting the served model observed on the response itself (e.g. the managed chat lane's real model), never the requested alias.
- Stop meeting notes from labeling Telegram (and other native messaging-app) calls as Speaker 1 when the other party's name is on the call window.

### Downloads
- **DMG Installer**: For fresh installs, download the DMG below
- **Auto-Update**: Existing users will receive this update automatically via Sparkle

<!-- KEY_VALUE_START
isLive: false
channel: candidate
edSignature: DvCuteDlh2Q8cA/AZl+cFQjD9XEdq9xFelDiy2N3VdLpU/T9tS1EKbjf5OyMOS7sfMx4zlwuqFILgl1UU4MfAA==
betaEdSignature: UAiK2avaa6vDlRiNZmz4CjkAAWUWN/uftGK4TCzOF8k93nbzEpUrIFJ9sMGYOV3t6FVClgAAS9+/pFptweUkDg==
changelog: Every answer now shows which model actually produced it: the Response Context (i) popover — including on the latest message and on voice answers — gains a Model row reporting the served model observed on the response itself (e.g. the managed chat lane's real model), never the requested alias.|Stop meeting notes from labeling Telegram (and other native messaging-app) calls as Speaker 1 when the other party's name is on the call window.
KEY_VALUE_END -->