Known issues

Last updated 3 min read

Current tracked bugs with user-facing impact. Updated at each release. Closed issues are removed when their fix ships in a tagged release. For general troubleshooting steps, see Troubleshooting common issues.

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.

Was this helpful?