Flags
Flags are runtime-only overrides. They do not modify your saved settings. The
next launch without the flag returns to whatever is configured in Settings.
How remote-control flags reach the running instance
SpeakoFlow enforces a single instance. The--toggle-transcription, --toggle-post-process, --toggle-assistant, and --cancel flags work by launching a second process. That process hands its arguments to the already-running instance through Tauri’s single-instance plugin, then exits immediately. No second window or tray icon appears, and the command returns right away.
If SpeakoFlow is not already running, the new process becomes the primary instance and starts normally. The toggle/cancel flags have nothing to act on in that case.
Launching a second instance with no recognized flag brings the existing window to the front.
Environment variables
Examples
Windows: toggle dictation from a script
macOS: toggle dictation from a script
Linux: Sway or Hyprland shortcut
In your Sway config:hyprland.conf:
Linux: GNOME or KDE custom shortcut
In GNOME Settings → Keyboard → Custom Shortcuts, add a shortcut with the command:What --list-devices shows
What --list-devices shows
It brings the native speech engine up, lists every compute device it found
with its index and memory, and reports whether the Vulkan, Metal, and CPU
backends loaded. Useful for verifying your GPU is visible to SpeakoFlow before
filing a bug. There is also a hidden
--probe-devices flag used internally on
Linux for crash-isolated device probing.GDK_BACKEND on GNOME Wayland
GDK_BACKEND on GNOME Wayland
On GNOME under Wayland, SpeakoFlow sets
GDK_BACKEND=x11 for itself so the
overlay can float above other windows. If you have already set
GDK_BACKEND yourself, your choice is respected.