Snippets

What a snippet is

A snippet pairs a spoken trigger with an expansion. Say the trigger and nothing else, and the expansion is inserted verbatim.

Common uses: your email signature, your address, a standup preamble, a bug-report template, a legal disclaimer, a support reply you send daily.

Creating one

Dashboard ▸ Snippets has two fields — trigger and expansion. Keep triggers short and distinctive: my address, signature, standup intro. Triggers are stored lowercase and matched case-insensitively, so you do not need to worry about how you capitalize them.

Adding a trigger that already exists replaces its expansion, which makes editing a snippet as simple as re-adding it.

How matching works

After transcription, the app compares what you said against your triggers:

• An exact match of the whole transcript expands.
• A prefix match also expands, provided the trigger ends at a word boundary — so “signature” matches but “signatures” does not accidentally fire it.
• When several triggers could match, the longest one wins.

Say a trigger in the middle of a longer sentence and it will not expand — snippets are deliberately an all-or-nothing gesture, so ordinary dictation never mutates unexpectedly.

Where they are stored

~/Library/Application Support/OpenVoiceFlow/snippets.json. There is no cap on how many you can have, and they are never uploaded.

Choosing good triggers

• Two or three words beats one — single common words risk firing when you meant to dictate them.
• Avoid triggers that are also natural sentence openings.
• Say the trigger cleanly and stop. Trailing “um” can prevent a match.
• If a snippet is not firing, check History to see exactly what was transcribed — usually the transcript differs slightly from the trigger you registered.