# Voice input: cannot configure Russian/Cyrillic submit keywords despite Russian language support **URL:** \ **Category:** Bug Reports\ **Tags:** voice\ **Created:** [September 12, 2026, 4:09pm UTC](https://forum.cursor.com/t/voice-input-cannot-configure-russian-cyrillic-submit-keywords-despite-russian-language-support/171443 "2026-09-12T16:09:34Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![DanteTemplar](https://avatars.discourse-cdn.com/v4/letter/d/919ad9/32.png) [@DanteTemplar](https://forum.cursor.com/u/DanteTemplar)\ **Post date:** [September 12, 2026, 4:09pm UTC](https://forum.cursor.com/t/voice-input-cannot-configure-russian-cyrillic-submit-keywords-despite-russian-language-support/171443/1 "2026-09-12T16:09:34Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug Voice input works for Russian, and Russian is available in the voice language selector. However, the Submit Keywords field does not let me enter a Russian word as a custom submission trigger. For example, I cannot configure отправить (“send”) as a submit keyword. The field appears to accept only English/Latin characters. This is a problem with entering/configuring the keyword, not with ordinary Russian speech transcription or an already-configured keyword failing to trigger. Russian dictation works, but a Russian submit keyword cannot be configured. This prevents a fully Russian hands-free workflow. ### Steps to Reproduce 1. Open Cursor’s voice settings. 2. Select Russian as the voice input language. 3. Find Submit Keywords. 4. Try to enter a Russian keyword such as отправить. 5. Observe that it cannot be entered/configured, while an English keyword can. ### Expected Behavior Allow custom submit keywords in supported voice input languages, including Cyrillic text, and recognize those keywords when spoken. ### Screenshots / Screen Recordings ![Screenshot From 2026-09-12 19-09-14.png](https://us1.discourse-cdn.com/cursor1/original/3X/c/8/c883788619cfba79c73a1c8b6eaa90c8b483452e.png) ![Screenshot From 2026-09-12 19-09-10.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/8/085a579af7c739a3c7fba7023c575e74c7b64b55.png) ### Operating System Linux ### Version Information Version: 3.18.9 VS Code Extension API: 1.128.0 Commit: 2ba48ff3f7514cc4643c52ca9f7b3173d9b66130 Date: 2026-08-27T01:42:22.092Z Layout: IDE Build Type: Stable Release Track: Default Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.291 OS: Linux x64 7.1.3-200.nobara.fc44.x86\_64 ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [September 12, 2026, 5:22pm UTC](https://forum.cursor.com/t/voice-input-cannot-configure-russian-cyrillic-submit-keywords-despite-russian-language-support/171443/5 "2026-09-12T17:22:03Z")
Hey, thanks for the report and the screenshots. I can see both the error toast and that only Latin words stay in the field. Confirmed: right now the Submit Keywords field only saves Latin letters and numbers, so a non-Latin keyword gets trimmed to empty and dropped with that warning. The same happens with any non-Latin alphabet. This isn’t anything in your setup. I’ve shared this with the team so custom keywords can be saved and recognized in voice input across all supported languages. There’s no workaround for a non-Latin keyword yet. Until this is fixed, the field will only accept a Latin keyword like `submit`, and you can always end dictation with the stop button. I’ll reply in the thread when there’s an update. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 16, 2026, 12:35pm UTC](https://forum.cursor.com/t/voice-input-cannot-configure-russian-cyrillic-submit-keywords-despite-russian-language-support/171443/8 "2026-09-16T12:35:31Z")
Hey @DanteTemplar, Quick update on this one. A fix for the Submit Keywords field dropping Cyrillic (and other non-Latin) keywords has landed and will be included in an upcoming version of Cursor (3.22). Once you’re on that version, a keyword like отправить should save normally and trigger submission when you say it. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [October 6, 2026, 9:11pm UTC](https://forum.cursor.com/t/voice-input-cannot-configure-russian-cyrillic-submit-keywords-despite-russian-language-support/171443/9 "2026-10-06T21:11:14Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.