Desktop overlay behavior is per platform
The Windows and Linux clients use their platform's own windowing and audio stacks.
Window managers, accessibility settings and compositors can affect overlays.
What we verified.
Engineering notes: what we checked, when we checked it, and what we found — including the limits. Dated, so you can hold us to them.
Observed implementation behavior and the environments that can change it.
Facts intended to remain checkable across releases.
The download is checkable
Current public binaries publish their exact version, byte size and SHA-256 in the products.json registry.
Checksum sidecars and the public products.json registry give a stable comparison point.
The reviewed range and what remains outside it.
Available platforms are separated from planned work.
Available platforms are separated from planned platforms
Lven Instant ships for Windows, Linux, and Android.
The product registry records an exact version, byte size, download URL and SHA-256 for every build.
Implementation paths and the cases where they can fail.
Text delivery has an explicit fallback
Where an application accepts direct insertion the transcript lands at the cursor; where it does not, it is placed on the clipboard, so nothing is lost.
Protected fields and applications that block automation take the clipboard path.
Recovery and network boundaries stated explicitly.
Account traffic is separate from dictated audio
Sign-in, access checks and the one-time model download use the network. None of those requests carry audio or transcript text.
Transcription itself runs with no connection.
Architecture and variables, without a universal benchmark claim.
On-device removes the upload
Lven Instant performs speech recognition on the device, so its transcription path never uploads microphone audio.
Measured on consumer-grade hardware: real-time factor 0.166, 3.76% word error rate, 0.93 s median per clip.
Documented architectural limits, not aspirational targets.