VocaMac does not expose anything to Shortcuts or App Intents, so dictation cannot be part of an automation the way other Mac apps can.
VoiceInk ships App Intents, and that is how it ends up inside Shortcuts, Raycast flows and hardware-key setups that do not go through a global hotkey.
The interesting part is that the pieces look like they are already here. --transcribe-file and --list-models landed with the headless CLI in #200, so there is a command surface already, and App Intents would mostly be a wrapper over decisions that have been made.
I do not have a Mac, so this comes from reading the repo rather than from using the app. Same thought filed for VocaLinux, where the mechanism would be D-Bus, and for VocaWin.
VocaMac does not expose anything to Shortcuts or App Intents, so dictation cannot be part of an automation the way other Mac apps can.
VoiceInk ships App Intents, and that is how it ends up inside Shortcuts, Raycast flows and hardware-key setups that do not go through a global hotkey.
The interesting part is that the pieces look like they are already here.
--transcribe-fileand--list-modelslanded with the headless CLI in #200, so there is a command surface already, and App Intents would mostly be a wrapper over decisions that have been made.I do not have a Mac, so this comes from reading the repo rather than from using the app. Same thought filed for VocaLinux, where the mechanism would be D-Bus, and for VocaWin.