Voice input: cannot configure Russian/Cyrillic submit keywords despite Russian language support

Support Bug Reports
1

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
Screenshot From 2026-09-12 19-09-14.png420×115 6 KB
Screenshot From 2026-09-12 19-09-10.png
Screenshot From 2026-09-12 19-09-10.png792×269 10.9 KB

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

5

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.

8

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.