Remote desktop sessions require a manual Cmd-V#
Symptom. When dictating into a remote-desktop window (Apple Screen Sharing, iPhone Mirroring, Microsoft Remote Desktop, Jump Desktop, AnyDesk, TeamViewer, RustDesk, or Parsec), the text does not appear on the remote machine by itself. Evoglyph shows a "Press Cmd-V to paste your dictation" notification instead.
Why. Remote-desktop clients rebuild your keystrokes for the other machine from real hardware keyboard state and discard keystrokes that software generates. An automatic paste never survives the trip: a synthetic Cmd-V arrives on the remote side as a plain "v", and typing the text out key by key drops capitals and punctuation. The clipboard is the only channel that carries your words across exactly, and the final Cmd-V has to be a real keypress from you.
What to do. Dictate as normal. Evoglyph copies the finished transcription to your clipboard and notifies you. Click where you want the text in the remote window, then press Cmd-V. In Apple Screen Sharing, keep Edit → Use Shared Clipboard enabled so your clipboard follows you into the session. Evoglyph also shows a one-time reminder the first time you bring a remote-desktop app to the front; you can dismiss it permanently from the reminder itself.
Status. By design (Evoglyph#3411). Fully automatic delivery would require a virtual keyboard driver and is not currently planned.
Last updated. July 31, 2026.
No automatic leading space between consecutive transcriptions#
Symptom. When you dictate twice in a row into the same text field (for
example in Obsidian or a terminal multiplexer), the second transcription is appended
directly to the first without a separating space. You get
hello worldgoodbye instead of hello world goodbye.
Status. Fix planned (Evoglyph#1713).
Workaround. Speak a leading word like "space" or manually add a space between dictations. Alternatively, pause briefly between dictations and click into the text field to re-establish cursor position before the second dictation.
Last updated. June 6, 2026.
Occasional text injection to wrong element in mixed-framework apps#
Symptom. In apps that mix native Cocoa views with embedded web content or Electron frames, injected text sometimes lands in the wrong element, for example, in a search bar instead of the focused message field.
Status. Investigating (Evoglyph#1465). Root cause is the bundle-ID injection routing table not covering capability-first fallback for AX-settable elements.
Workaround. Click directly inside the target text field immediately before pressing the hotkey. If the wrong-app pattern repeats in a specific app, email [email protected] with the app name and version.
Last updated. June 6, 2026.
Corrections table not populating#
Symptom. The corrections table in the app dashboard remains empty even after you manually correct transcription output. The inline AX edit observation is not firing.
Status. Investigating (Evoglyph#1439).
Workaround. None currently. Corrections intended for vocabulary improvement can be added manually via Evoglyph → Settings → Vocabulary.
Last updated. June 6, 2026.
Compound name digit merging incomplete#
Symptom. Numbers in compound names (for example "GPT-4o", "Llama 3.1", "M4 Pro") may not merge correctly when spoken, producing broken output like "G P T 4 o" or "M four Pro".
Status. Fix planned (Evoglyph#1331). The LCP compound-name licensing fix currently covers single digits; teens, tens, hundreds, and thousands are a follow-on.
Workaround. Add the specific compound name to your custom vocabulary at Evoglyph → Settings → Vocabulary. Vocabulary entries are boosted via CTC rescoring and typically resolve these cases.
Last updated. June 6, 2026.
Issue not listed here?#
Email [email protected] with a description of
the symptom, your Evoglyph version (Evoglyph menu bar icon → About),
your macOS version, and the contents of ~/Library/Logs/evoglyph/ if you can
attach them. The log does not contain audio or transcripts.