Why do apps like VS Code, Slack, or Chrome need a different setting?
On a Mac, apps built on Electron or Chromium only say which field is focused when asked. One setting asks them, and it is on by default. Windows needs nothing.
For almost every application, dictation works with no setup: click into a text field, dictate, and the words appear there. On a Mac, one family of applications needs a setting to behave the same way, and Dictate Safe turns it on for you.
#Electron and Chromium apps, on a Mac
VS Code, Cursor, Slack, Discord, Chrome, and other applications built on Electron or Chromium share a quirk: they only report which field is focused once something asks them to. Without that, Dictate Safe cannot tell whether you have a text field focused inside one of them.
#Detect text fields in Electron apps
This is the setting that asks them. It lives in Settings → Typing, and it is on by default.
With it on, dictating into one of these apps with nothing focused shows the no-target popup instead of typing into nowhere.
It costs a little memory in whichever of those apps you use, because it asks each one to build the accessibility information it would not otherwise build. If you would rather not spend it, turn the setting off: dictation still types into these apps normally, and you only lose the popup when nothing is focused.
Windows finds the focused field in these apps without being asked, so there is no setting to change, and the row does not appear.
This only decides whether to type or show the popup. It is not why dictation would fail to type at all. If dictation is not typing anywhere, in any application, see Why is nothing typed when I dictate?